In many teams escalation works because one particular person sorts things out. That is not a process, it is a dependency with an annual leave entitlement.
In many service teams escalation works reliably – as long as one particular person is in the building. That person knows the exceptions, the right contacts and the short route. It is valuable, but it is not a process. It is a dependency, and it becomes visible the moment they take leave.
When to escalate has to be settled in advance
Without defined triggers, the decision comes down to how someone feels that day: those who feel confident try it themselves, those who feel unsure hand it over early. Both are understandable, and both mean comparable cases get treated differently.
Workable triggers are concrete and non-negotiable: a number of follow-ups, an amount, a hint of legal action, an accusation made in public. They do not have to be perfect – they have to be recognisable during the conversation, without looking anything up.
The customer should not have to tell it twice
The most common complaint about complaint handling is not the time it takes, but the repetition. Someone describing their case for the third time can hear that nobody internally wrote anything down.
A handover therefore needs less form and three facts: what has been promised so far, what has already been checked, and what the customer actually expects. Without that last point, escalations often end in a correct solution to a different problem.
The second contact is the warning sign
A good indicator of escalation risk rarely appears in complaint statistics: the customer who gets in touch a second time about the same matter without complaining. That contact is counted like any other – yet it is the moment that decides whether a complaint follows.
Making second contacts on the same case visible lets you see escalations coming instead of reacting to them.
Escalation also protects staff
A clear route upwards takes pressure out of the conversation. Someone who knows they are allowed to hand a case on does not have to hold it alone – and is more likely to stay calm when the tone sharpens.
Without that route you get the quietest form of escalation: commitments nobody can honour, made by someone who wants the call to end.
Analyse, do not just process
Individual escalations get resolved and filed. They only become interesting in aggregate: which three causes account for most of them? Which of those does not sit in service at all, but in a process upstream – in billing, in a delivery promise, in a product description?
That analysis is uncomfortable because it regularly points at other departments. Which is precisely why it is the only part of complaint handling that reduces the number of complaints.
