Escalation

Definition

Escalation is the handoff of a ticket from the technician working it to someone with more skill, more authority, or more time – typically from a Tier 1 (T1) help desk tech to T2, from T2 to a T3 senior engineer or the owner, or from a technician to a vendor. Management escalation – pulling in an account manager for an unhappy client – follows the same logic.

Why it matters to an MSP

Escalation is where labor cost, SLA compliance, and client satisfaction meet. T1 labor is your cheapest hour and T3 your most expensive; every ticket sitting with the wrong tier either costs too much or takes too long. The failure mode is almost never over-escalation – it is ticket-hogging, where a stuck tech spends half a day on a problem a senior would solve in twenty minutes. The fix is a written escalation path with time-based triggers, not judgment calls: commonly, T1 escalates after 30 minutes without progress, T2 after two hours, and a priority-1 outage goes to T3 immediately. Escalating on the trigger is following process, not admitting failure, and the dispatcher enforces that framing.

Define who owns each tier, what a ticket must contain before it moves (steps tried, error text, business impact), and who is notified when the SLA clock is at risk. Track escalation rate per tech and per tier – a T1 escalating 60 percent of tickets needs training or better runbooks; a T1 escalating 5 percent is probably sitting on things. For a solo owner hiring a first technician, the escalation path is the point of the hire: you become T2 and T3, and the tech owns the queue. The full tiering model is in the ticket management process.

Related terms: SLA, Runbook, First Call Resolution, Ticketing System