escalation matrix template for support teams

TL;DR

An escalation matrix answers three questions for every severity: who gets paged, how fast they must respond, and who decides to wake up leadership. Build it as a table: severity down the side, responder roles across the top, response targets in the cells. Review it quarterly. A matrix nobody has read is decoration; run a drill and the gaps show up fast.

The query

escalation matrix template for support teams

Use this when

• Escalations are ad hoc and inconsistent
• Pages go to the wrong people or nobody
• Writing incident response documentation
• Leadership asks "who decides" during incidents

Not for

• Engineering on-call rotation design
• Company org charts
• RACI charts for projects
• Individual performance issues

Steps

1. Define four severities in customer terms

SEV1: core function down for many customers. SEV2: major feature broken or degraded widely. SEV3: limited impact, workaround exists. SEV4: minor, cosmetic, single customer. Write the definitions with examples from your product.

Expected output: four severities with product-specific examples.

2. Fill the who and how-fast table

For each severity: primary responder (support lead), secondary (engineering on-call), decision maker (who can declare, who can page leadership), and response target (5 min, 30 min, 4 h, next business day). One table, one page.

Expected output: the completed matrix.

3. Name the leadership trigger

Write down exactly what pulls in leadership: SEV1 automatically, SEV2 after 2 hours unmitigated, any security or data-loss signal regardless of severity. Ambiguity here is what causes 3am "should I wake someone" paralysis.

Expected output: explicit leadership triggers.

4. Publish it where the team actually looks

The incident channel topic, the on-call handoff doc, the support wiki front page. Not page 40 of a PDF. If an agent cannot find it in 30 seconds during an incident, it does not exist.

Expected output: the matrix linked in three high-traffic places.

5. Drill it quarterly

Run a 30-minute tabletop: announce a fake SEV1 and watch who pages whom. The drill finds the stale phone numbers, the ex-employees still listed, and the severity everyone disagrees on.

Expected output: a drill log with fixes applied.

Template: the matrix

Severity | Example | Primary | Secondary | Decides | Respond in | Leadership
SEV1 | login down for all | support lead | eng on-call | support lead declares | 5 min | auto-paged
SEV2 | checkout broken, workaround none | senior agent | eng on-call | support lead | 30 min | after 2h unmitigated
SEV3 | one integration failing, workaround exists | agent | team lead | team lead | 4 h | no
SEV4 | typo in UI, single report | agent | backlog | agent | next business day | no

Leadership trigger: any SEV1, any SEV2 past 2h, any security/data-loss signal.
Liaison: support names one person per incident to talk to engineering.

Variant phrasings

support escalation policy template

Steps 1 through 3. Severities, the table, leadership triggers.

who to page for support incidents

Step 2 plus step 4. The table, published where people look.

sev definitions for customer support

Step 1. Customer-impact language, product examples.

Why it works

Incidents are bad; confusion about who does what makes them worse. The matrix converts judgment calls into lookups, which is exactly what you want when everyone is stressed. The drill matters because matrices rot: people leave, numbers change, and only a drill surfaces it.

Edge cases

• Security incidents: separate track, always page security lead, do not wait for severity debate.
• The support lead is the one on vacation: every role needs a named backup.
• SEV1 during a holiday: pre-assign holiday coverage. Do not improvise it at 2am.
• Vendor-caused incidents: the matrix still applies; add "open vendor ticket" as a primary action.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_oIOOrvwHQTEDuFoxu65yLg