The handoff is where trust dies
A customer's patience survives a hard problem. It rarely survives being bounced between three people, each asking them to re-explain from scratch. Escalation workflows exist to move a ticket up without losing context or accountability.
Define your tiers
- Tier 1: front-line. Handles the majority of tickets using KB and macros.
- Tier 2: specialists. Take what Tier 1 can't resolve in a defined window.
- Tier 3 / Engineering: bugs and edge cases requiring code or data access.
Keep the tiers shallow. Every additional layer adds a handoff where context leaks.
Write explicit escalation criteria
Don't leave it to "when the agent feels stuck." Define triggers:
- Issue unresolved after 2 agent replies or 24 hours.
- Requires access the current tier doesn't have.
- Customer explicitly requests a manager.
- SLA breach is imminent on a P1/P2.
Escalate the ticket, not the customer
The cardinal rule: the customer should never have to repeat themselves. When a ticket escalates, the receiving agent inherits the full timeline, the diagnosis so far, and what's already been tried. The handoff happens behind the scenes.
Close the loop back down
When Tier 3 resolves a bug, the resolution should flow back to Tier 1 — both to update the customer and to teach the front line so the next instance is handled without escalation.
Track escalation rate
A rising escalation rate means either Tier 1 is under-equipped or the product is getting harder to use. Both are fixable — but only if you're watching the number.