Escalation is the act of moving an issue to a person or team with more expertise, authority or resources when the current owner cannot resolve it, or when it is at risk of breaking a deadline. In support, it usually means moving a ticket from a first-line agent to a specialist or engineer, or to a manager.
Why it matters
Clear escalation paths prevent serious problems from sitting in a queue. They define who gets involved, when and with what information. Support teams often use tiers: level 1 handles common requests, level 2 handles technical investigation, and level 3 involves engineering. In operations, the same idea appears in on-call policies, where an unacknowledged alert pages the next person after a set time.
Example
Ticket: payments failing for all users
Level 1: confirms it is not an isolated account -> escalate (severity 1)
Level 2: finds an error in the payment gateway integration
On-call engineer paged; manager informed after 15 minutesCommon mistakes
- Escalating without logs, steps to reproduce and impact, so the next person starts from zero.
- Having no criteria, so everything is escalated or nothing is.
- Failing to tell the customer who now owns the issue.
- Treating escalation as blame rather than routing.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.