Turning a resolved complaint into an advocate, which happens often
- 5 days ago
- 3 min read
Updated: 3 days ago
Introduction
A customer who has never had a problem has nothing to say about you beyond that everything was fine. A customer who had a problem and watched you deal with it properly has a story, and stories are what get repeated. This is why complaints, handled well, produce advocates more reliably than flawless delivery does.
It is counterintuitive and it holds up in practice. Anybody can appear competent when nothing goes wrong. How a business behaves when something does is genuinely informative, and customers know it, which is why the account of a recovery persuades in a way that praise for ordinary work does not.
The conditions under which this works are specific. Miss any of them and the complaint stays a complaint.
1. Turning a resolved complaint into an advocate depends on speed
The first condition.
Acknowledgement the same day converts most of the anxiety before it hardens into resentment. Delay makes recovery much harder. Nothing else matters as much. Acknowledge even before you know the answer.
2. Do not argue about fault first
The second condition.
Establishing responsibility before addressing the problem guarantees the customer remembers the argument rather than the fix. Deal with the situation. Attribution can wait. In many cases it never needs raising at all.
3. Fix more than the minimum
The generosity point.
Resolving exactly what was complained about is adequate; doing slightly more is what produces the story. It need not be expensive. Proportion matters more than value. A small gesture beyond the fix is what gets described.
4. Explain what happened
The transparency point.
A plain account of the cause, without excessive apology, reads as competence rather than weakness. People trust businesses that can explain their own failures. It also reassures that it will not recur. Keep it factual rather than defensive.
5. Say what you changed
The credibility step.
Telling the customer what will now be different demonstrates the complaint was taken seriously beyond their own case. This is the detail people repeat. It costs one sentence. It also makes the change real internally.
6. Follow up afterwards
The completion.
A message a week later confirming everything is settled finishes the recovery properly. Most businesses stop at the fix. This step is where the goodwill is consolidated. One message, a week later.
7. Do not ask for anything during the recovery
The restraint.
Requests for reviews or referrals while a complaint is live are badly received, however well the resolution went. Wait until it is properly closed. The willingness will still be there. A fortnight is a reasonable interval.
8. Record the complaint and the outcome
The organisational point.
Recovery only produces advocates if it is consistent, and consistency requires knowing what happened before. Two lines on the record. It also reveals repeating faults. The same complaint twice is a process problem, not bad luck.
9. Recognise that some complaints cannot be recovered
The realism.
A serious failure, or a second failure after a first, may end the relationship regardless of the response. The approach here works for ordinary problems handled well. It is not a substitute for reliability. Reliability comes first.
Be careful about drawing the wrong conclusion from all this. The finding is that recovery produces advocates, not that problems are desirable, and a business that generates difficulties in order to resolve them will simply be regarded as unreliable.
Conclusion
Treat a complaint as the best available opportunity to create an advocate.
Acknowledge it the same day, resolve the situation before discussing fault, do slightly more than the minimum required, explain plainly what went wrong, say what you have changed so it does not recur, follow up a week later to confirm it is settled, ask for nothing while the complaint is live, record what happened so recovery is consistent, and accept that some failures end relationships whatever you do.
.png)



Comments