Every organisation says it values complaints. Very few behave as if they do. Complaints get counted, categorised, closed and reported, and then the next month the same complaints arrive again, from different customers, wearing slightly different clothes.
After more than twenty years handling the most complex end of customer resolution across telecommunications, financial services, insurance and government, I have come to believe the problem is not effort. Frontline teams work hard. The problem is a listening error. We treat each complaint as a case to be closed, when it is actually a signal to be read.
Every complaint carries three layers
When a customer escalates, they hand you three things at once, and most processes are only built to receive the first.
The issue. The bill that is wrong, the service that failed, the decision they do not understand. This is the layer complaint systems are designed for, and on a good day we resolve it well.
The feeling. Behind almost every escalation is a fear: that nobody is accountable, that they will have to fight, that they do not matter. The customers who seem the most difficult are usually not difficult at all. They are exhausted. If you answer the issue but not the fear, the complaint is closed and the customer is still lost.
The pattern. This is the layer organisations drop, and it is the most valuable one. One customer confused by a letter is a case. Forty customers confused by the same letter is not forty cases. It is one broken letter, and every case closed without reading the pattern is the cost of not fixing it.
The repeat signal is the loudest one
Early in my financial services career I noticed something in the call queue that nobody had flagged: the same customers were ringing back about the same issues. On paper, every one of those earlier calls had been resolved. In reality, if a person has to call twice, something in the service quietly failed the first time.
So I stopped guessing and went to the data. I analysed the callbacks and tagged the actual root cause behind each one, and a clear picture emerged: two product areas were generating most of the repeats, and customers were getting different answers depending on who picked up the phone. The fix was not heroic. A targeted knowledge refresh on exactly those two areas, and a simple discipline that every call ends with the customer knowing their one clear next step. Then the part most people skip: tracking the numbers for the following quarter to prove the fix held.
Repeat contacts fell measurably. But the number was never the point. The point is that the signal had been sitting in plain sight, in data every organisation already collects, waiting for someone to read it as a pattern instead of a pile of cases.
How to listen like a system
If you handle complaints, or you lead people who do, four disciplines turn complaint handling into complaint intelligence.
Tag the root cause, not the symptom. "Billing enquiry" tells you nothing. "Customer could not reconcile the pro rata charge on their first invoice" tells you exactly what to fix. The extra thirty seconds of precise tagging is where all the later insight comes from.
Treat repeats as system failures. A repeat contact is not a new case. It is evidence that the first resolution did not hold, and it deserves a different question: not "how do I close this" but "why did this come back".
Escalate patterns as risk, not as complaint. When you find a systemic issue, how you raise it decides whether it gets fixed. Data, business case, proposed fix. Never an accusation about the team upstream. A pattern presented as a risk gets a meeting. A pattern presented as a moan gets a nod.
Close the loop with the person. A decision is not finished until the customer actually understands it. Every case closed with a confused customer is a repeat contact you have simply scheduled for later.
What this means for the people in the queue
If you work in customer experience, this reframe changes your job description. You are not a case closer. You are the organisation's most sensitive instrument, the person positioned to hear the tremor before anyone else feels the earthquake. The complaint in front of you matters twice: once for the customer who deserves a resolution, and once for the thousand customers who will never complain, but are quietly hitting the same wall.
Resolve the case. Answer the fear. Read the signal. That is the whole craft, and after twenty years it still gets me out of bed.
— Leena Kumar, Sydney