Support escalation matrix template: who to pull in, and when

By Draft First, October 2026

An escalation matrix answers one question at 2 a.m.: who do I call? Without one, escalations depend on who happens to be online and who shouts loudest. With one, the support engineer knows the next step and the customer hears from the right person on time.

The template

Severity	Example	First response	Escalate to	CS told?
Sev 1	Production down, data at risk	[e.g. 1 hour]	Support lead and engineering on-call at once	Yes, right away
Sev 2	Major feature broken, workaround hard	[e.g. 4 hours]	Tier III after [e.g. 8 hours] without progress	Same day
Sev 3	Feature broken, workaround exists	[e.g. 1 business day]	Tier II after [e.g. 3 days]	Weekly summary
Sev 4	Question or cosmetic issue	[e.g. 2 business days]	None	No

Fill in the times your contracts actually promise. Don't copy numbers from another company's matrix.

Three kinds of escalation

Technical: the problem is hard. Goes up through Tier II, Tier III and engineering.
Time: the problem is taking too long. Goes to the support lead, even if the next tier is already working it.
Relationship: the customer is upset or the account is at risk. Goes to the CSM and CS leadership, whatever the severity.

Most matrices only cover the first one. The third is the one that loses renewals.

Rules that make it work

One owner per escalation, named in the ticket.
Status updates on a schedule, even when there's no news.
Any Sev 1 or 2 on an account renewing within 90 days goes to the CSM, no matter what.
Close with a short written summary of cause, fix and what changes.

A sample escalation note

ESCALATION | Sev 2 | Larkspur Labs (fictional) | Ticket #4821
Issue: dashboard down for EU users, 5 days open
Owner: Priya (support lead) | Engineering: on-call ticket ENG-311
Customer impact: 60 EU users, renewal Dec 12
Next update: today 4 p.m. ET, to Tom Ng (customer) and the CSM
Ask: engineering fix date by end of day

Next steps

For the leadership summary, use the escalation brief guide. For the customer side, see the escalation email templates or the free escalation email generator.

Questions

What is a support escalation matrix?

A table that sets severity levels, response times and who gets pulled in at each step, so escalations follow a plan.

What are the levels of support escalation?

Most teams use Tier I frontline, Tier II deeper troubleshooting, Tier III experts, then engineering, plus time and relationship escalations to leads and CS.

When should customer success be told about a support escalation?

Right away for Sev 1, same day for Sev 2, and always when the account renews within 90 days.

Want the full routines?

The CS Agent Playbook has 14 ready-to-paste agent routines like this one, each with guardrails, a sample result and the failure to check for first. $39 for the PDF and a plain-text prompts file.

Get the playbook or get the free sample play