What Happens When an Agent Cannot Solve the Issue?
A defined path, not an agent improvising under pressure.
Escalation exists so a problem lands with the right person quickly, instead of stalling with an agent who lacks the authority or information to resolve it. The structure is defined before go-live, not improvised the first time it is needed.
Escalation tiers
| Level | Handles |
|---|---|
| Level 1 — Agent | Documented contacts within their approved authority |
| Level 2 — Supervisor | Authority exceptions, unhappy customers, undocumented questions |
| Level 3 — Client contact | Decisions requiring your judgement or approval |
| Critical | Immediate escalation, bypassing the normal queue entirely |
What typically triggers an escalation
- Billing exception outside agreed limits
- Refund exception above the agent's authority
- Legal complaint or threat of legal action
- Safety issue
- Payment dispute
- A genuinely angry customer who has asked for a manager
- Technical outage affecting service delivery
- Sensitive information disclosed or requested
- A high-value account, where extra care is warranted regardless of the specific issue
The escalation matrix template
A downloadable structure for defining your own triggers, tiers, owners and response commitments — useful for any support operation, outsourced or internal.
Escalation Matrix Template
A tiered Level 1 / 2 / 3 / Critical escalation structure, ready to adapt.
FAQs on this stage
How are escalations handled?
By rules you define in writing during onboarding: what triggers an escalation, who it goes to, and how urgently. Agents follow the rule rather than improvising, and escalations are reported so you can see what keeps hitting the threshold.