Escalation judgement
When should a support engineer escalate a ticket?
When the fault needs something you cannot do, and not before. Escalating something solvable wastes engineering time; sitting on a genuine defect wastes the customer's. Both directions are scored, and so is the packet: whether a developer picking it up got what they needed or had to start again.
- Whether escalating - or not escalating - was right for this fault, and whether the packet gave a developer what they needed. Escalating something solvable wastes engineering time; sitting on a genuine defect wastes the customer's.
- One of the 11 dimensions every ticket here is graded against
What a weak answer looks like
The ways this is usually lost
Named failures rather than general warnings, because a warning nobody can recognise in their own work changes nothing.
Escalating at the first unfamiliar error, with no narrowing attached.
Holding a confirmed defect for days because it feels like giving up.
A handover that forwards the thread and nothing else, leaving the next person to re-read everything.
What a strong one looks like
What the grader is actually looking for
The same ticket, done in the way that scores.
Escalating once the problem has been narrowed as far as the tools available allow.
A packet that leads with reproduction steps, scope and what has been ruled out.
The decision stated either way, so not escalating reads as a judgement rather than an omission.
Questions
Asked about this one
Is escalating early a sign of weakness?
Only when nothing was narrowed first. Escalating a confirmed defect quickly is good judgement. Escalating an unfamiliar error message without establishing scope is the thing that is scored down, because it moves the work without reducing it.
What belongs in an escalation?
How to reproduce it, who is affected, what has been ruled out and what the customer has been told. The test is whether a developer can start on the problem instead of starting on the thread.
Related guides
- Tone & empathy
- Diagnostic quality
- Communication clarity
- SLA discipline
- Resolution correctness
- Documentation
- Judgement on the AI's suggestion
- Ticket admin accuracy
- Priority judgement
- Technical depth
- Technical support interview questions, answered from realistic tickets
See this scored on a realistic ticket: work one free, read a worked ticket, or see what a graded record shows. Every guide is listed on the guides index, and if something here is wrong or unclear, tell us.
Free to start · no sign-up
You do the work. We hand you the record.
Your first ticket is free.