What is escalation?

Why it matters

Escalation design decides whether a hard case gets solved or gets passed around. Most escalation pain is not caused by the escalation itself but by what is lost in the transfer: the context, the diagnosis already done, and the customer patience for repeating themselves a third time.

What to know

• Distinguish functional from hierarchical escalation. They need different triggers and different destinations.
• The transfer must carry the full history, or the receiving person restarts work already done.
• Escalation criteria should be explicit, or agents escalate defensively and the specialist queue floods.
• Track escalation rate by topic. A spike in one topic is a training or documentation gap, not an agent problem.
• Customers should never be asked to re-explain after an escalation. That single rule fixes most escalation complaints.

An example

Example: an agent cannot approve a refund outside policy and escalates to a manager. If the escalation carries the account history, the reason, and a recommendation, the manager decides in a minute. If it carries a one-line note, the whole diagnosis happens again.

Common mistakes

• Escalating without a written summary of what has been tried
• Leaving escalation criteria to individual judgement
• Measuring agents on low escalation rate, which suppresses necessary escalations
• Making the customer repeat their story after every transfer

Questions