Selvo
PricingToolsBlogLogin
Free tool

Escalation matrix template

Pick your matrix type and get a ready-to-use escalation matrix — levels, triggers, owners, response times, and who to notify. Copy it to Notion in one click. Free, no signup.

Pick your matrix type

Helpdesk escalation from frontline agents up to a manager.

Customer support escalation matrix

4 levels
LevelTrigger / criteriaOwner / roleResponse timeNotify
L1First response — general questions, how-tos, known issues, password resetsFrontline support agentWithin 1 business hour—
L2Unresolved after L1, account-specific or technical issues, repeat contacts on the same problemSenior agent / team leadWithin 4 business hoursL1 agent who owns the ticket
L3Confirmed bugs, outages, or anything needing a code, infra, or config changeEngineering / product on-callWithin 1 business daySupport manager + L2 owner
ManagerComplaints, refunds beyond policy, churn risk, or a threat to escalate publiclySupport managerWithin 2 business hoursAccount owner / CS

Get all 3 matrices as one doc

Every matrix — customer support, incident severity, and customer success — in a single Markdown file with real tables you can paste into Notion, Google Docs, or your runbook. Yours to keep and customize.

Free. No spam, only the matrices.
The guide

Building an escalation matrix that works

A good matrix turns escalation from a judgment call into a rule: anyone can see who handles what, by when. Here's what an escalation matrix is, how to set the levels, owners, and timings, and how to make escalations actually route on their own.

What an escalation matrix is

An escalation matrix is a table that maps an issue's journey through your team. Each row is a level; the columns say what triggers that level, who owns it, how fast they should respond, and who else gets notified. It exists so no one has to guess where a hard ticket goes — the matrix already decided. The five columns the generator builds for you:

  1. 01LevelL1 / L2 / L3 — or SEV1–SEV4
  2. 02Trigger / criteriaWhat moves it up a level
  3. 03Owner / roleWho handles it here
  4. 04Response timeWhere your SLA targets live
  5. 05NotifyWho else gets looped in

Setting levels, owners, and timings

Keep it to the fewest levels that map to real, distinct owners — three or four is the norm. L1 is your frontline; each level up should mean a different person with more authority or expertise, not just a longer queue. Set the trigger for each level in plain language (“unresolved after L1,” “churn threat,” “full outage”) so it's obvious when to move. The response-time column is where your SLA targets live, level by level — tighter at the top, looser at the bottom.

Routing escalations automatically

A matrix on paper doesn't move anything — your tools have to. The difference between a matrix people follow and one they ignore is whether escalation is automatic. A shared inbox assigns and routes each issue to the right level, shows who's already replying so nothing gets double-handled, and lets anyone hand off with the full history attached. An AI agent acts as your L1 — clearing the routine questions and escalating to a human the moment it's unsure — so the top of your matrix only ever sees what genuinely needs it.

Selvo Shared Inbox + AI Agent

Make escalations actually route to the right person

A matrix only works if every ticket lands where it should. Selvo's shared inbox assigns and routes by rule, shows who's already replying so nothing gets double-handled, and the AI agent clears L1 — answering the routine questions and handing off to a human the moment it's unsure.

See how Selvo Shared Inbox works

Explore more free tools

Knowledge Base Article Template

Describe one help-center topic and generate a structured knowledge base article, plus ready-to-use article templates for how-tos, troubleshooting, getting started, and more.

Open tool

Customer Service Email Templates

Copy-paste support email templates for apologies, refunds, orders, onboarding, and more — customize any with AI.

Open tool

Onboarding Checklist Template

Pick employee, remote, customer, support, or manager onboarding and get a tailored, checkable checklist — copy it to Notion in one click.

Open tool

QBR Template

Pick Customer Success, Executive, Pre-Renewal, Sales, or Agency and get a slide-by-slide quarterly business review outline — trim it, then copy to Slides or Notion.

Open tool

Questions about escalation matrices

What is an escalation matrix?
An escalation matrix is a simple table that defines who handles an issue at each level, what triggers a move to the next level, how fast each level should respond, and who gets notified. It turns "who do I send this to?" into a rule instead of a judgment call, so issues reach the right person quickly and nothing stalls in someone's queue. The generator above gives you a ready-to-use matrix for support, incident response, or customer success — pick one and copy it.
What levels should an escalation matrix have?
Most teams run three to four levels. A support matrix is usually L1 (frontline agents) → L2 (senior agents or a team lead) → L3 (engineering or product) → manager for complaints and exceptions. Incident response uses severity levels — SEV1 (critical outage) down to SEV4 (cosmetic). Customer success escalates CSM → senior CSM → CS manager → executive. Keep it to the fewest levels that map to real, distinct owners; more than four usually means two of them do the same job.
What's the difference between an escalation matrix and incident severity levels?
They answer different questions. An escalation matrix defines the path an issue takes between people — who owns it at L1, L2, L3, and when it moves up. Incident severity (SEV1–SEV4) classifies how bad an issue is so everyone agrees on urgency. In practice they work together: severity decides how high to start and how fast to respond, and the matrix decides who that means. The "Incident severity" tab above shows a matrix built around severity levels.
How do I make escalations actually happen instead of sitting in a queue?
A matrix on paper doesn't move tickets — your tools have to. The fix is routing: assign each incoming issue to the right level automatically, make it obvious who's already working it so nothing gets double-handled, and let anyone hand off with full context. Selvo's shared inbox does that routing and assignment, and its AI agent acts as your L1 — answering routine questions and escalating to a human the moment it's unsure, so the matrix runs itself instead of relying on someone remembering to forward an email.
How is an escalation matrix different from an SLA?
An SLA is the promise — the response and resolution times you commit to. An escalation matrix is the mechanism that keeps that promise: it defines who an issue goes to and when it moves up so you actually hit those times. They're complementary. The response-time column in the matrix above is where your SLA targets live, level by level. If you need the promise itself, our SLA template generator builds that document.
Is this escalation matrix template free?
Completely. Picking a matrix and copying it as Markdown are free with no signup — the table pastes straight into Notion, Google Docs, GitHub, or a runbook. The only thing we ask for an email on is the optional one-click download of all three matrices as a single file you can keep.

Something we didn't cover? Email a founder — answer in your inbox the same day.

We built the support tool we wished existed.

Help center, chat widget, AI agent, and shared inbox. The whole support stack on one bill. Free for fourteen days, no credit card.

Book a demoTry for free for 14 days