Customer support ticket escalation
Most escalation processes exist as a shared understanding rather than a document, which means escalation depends on who is on shift and how confident they feel. The result is that the loudest customer gets escalated and the most affected one does not. Written severity definitions fix that, because they let anyone escalate correctly on their first week.
- 1
Support Agent assigns a severity based on customer impact, using the written definitions rather than the customer's own wording.
Support Agent
Impact, not tone. An angry message about a cosmetic issue is not severity one, and a calm message about a data problem is.
- 2
Support Agent attempts resolution using the documented known issues and procedures, and records what was tried.
Support Agent
Record the attempts. Whoever picks this up next should not repeat them, and a repeated question across tickets means a missing procedure.
- 3
Support Agent checks the severity against the escalation criteria.
Support Agent
Resolvable at first line: go to step 4
Meets escalation criteria: go to step 5
- 4
Support Agent resolves the ticket, tells the customer what was wrong, and records the resolution against the issue category.
Support Agent
Categorise the resolution. Category counts are what tell you which documentation gap or product defect is costing the most support time.
Resolved: the procedure ends
Reopened by customer: go to step 5
- 5
Support Agent escalates to the Support Lead with the severity, what was tried, and the reproduction steps.
Support Agent
Reproduction steps are the difference between an escalation and a forwarded complaint. Without them the next person starts from nothing.
- 6
Support Lead acknowledges to the customer within the response target for that severity, even without an answer yet.
Support Lead
Timing: Per the severity response target
Acknowledge on time regardless. Silence during an unresolved issue damages trust faster than the issue itself.
- 7
Support Lead determines whether the issue needs engineering or can be resolved at second line.
Support Lead
Second line can resolve: go to step 4
Needs engineering: go to step 8
- 8
Support Lead raises it with Engineering On-Call, including severity, affected customer count, and business impact.
Support Lead
Affected customer count is what lets engineering prioritise honestly between two escalations. One customer and forty look identical without it.
- 9
Support Lead provides the customer with an update at the interval promised for that severity, until resolution.
Support Lead
"Still investigating, next update in four hours" is a real update and it is what people actually want.
Resolved: go to step 10
No progress past the next interval: go to step 11
- 10
Support Lead confirms resolution with the customer, then records the root cause and whether documentation needs updating.
Support Lead
If the answer existed but the agent could not find it, that is a documentation problem, not a training problem.
Closed: the procedure ends
- 11
Support Lead re-escalates, raising severity or engaging the next level, and tells the customer it has been escalated.
Support Lead
A stalled escalation must have a defined next move, or tickets sit at second line indefinitely with everyone assuming someone else is on it.
Re-escalated: go to step 9
Change these before you use it
- Write your severity definitions with concrete criteria, since "customer impact" needs to mean something specific. This is the most important adaptation on this page.
- Set response and update targets per severity, and make sure they are achievable with your actual staffing.
- Name your real channels and tools. "Escalates to the Support Lead" is not followable at 2am without naming where.
- If you have contractual SLAs, align the targets here with them and check which take precedence.
- Add out-of-hours cover explicitly, including who is reachable and how, or the procedure silently only works during office hours.
This is a starting point, not compliance advice. It is written to be adapted, and a procedure that touches access, money, or customer data needs to match how your business actually operates and whatever rules apply to you. Use it as a first draft to edit, not a policy to adopt.
Make it yours in a couple of minutes
Rather than retyping this and editing it, describe your own version of the process out loud or click through it once, and get a first draft with your actual steps, roles, and systems in it. No account needed to see the result.
No account neededNo credit cardSee the whole SOP before you sign up