Escalation Matrix Template

Escalation Matrix — Customer Support

Overview

This matrix defines when, how, and to whom support issues should be escalated. Every agent should know this document and follow it without exception.

---

Escalation Tiers

Tier 1 — Front-Line Support

Handled by: Support Agents Scope: Common questions, known issues, account changes, billing inquiries Tools available: Knowledge base, canned responses, basic account admin Escalate to Tier 2 when:

• Issue requires code-level investigation
• Customer reports data discrepancy
• Agent cannot reproduce or diagnose the issue within 30 minutes
• Customer requests a manager

Tier 2 — Senior Support / Technical Support

Handled by: Senior Support Engineers Scope: Complex technical issues, integration problems, bug investigation Tools available: Admin panel, log access, staging environment Escalate to Tier 3 when:

• Issue requires a code change or hotfix
• Bug is confirmed and affects multiple customers
• Data recovery or migration is needed
• Issue has been open for 24+ hours without progress

Tier 3 — Engineering

Handled by: Engineering Team (on-call rotation) Scope: Bug fixes, infrastructure issues, data recovery, security incidents Tools available: Full codebase, production access, deployment pipeline Escalate to Tier 4 when:

• Issue is a confirmed security incident
• Outage affects 50%+ of customers
• Resolution requires executive decision (e.g., public communication)

Tier 4 — Executive / Crisis

Handled by: VP of Engineering, CTO, or CEO Scope: Major outages, security breaches, regulatory incidents, PR-sensitive issues Actions: Status page updates, customer communications, post-mortem initiation

---

Escalation Contacts

Tier	Primary Contact	Backup Contact	Availability
Tier 1	[Agent on shift]	[Team Lead]	Business hours
Tier 2	[Senior Engineer Name]	[Backup Engineer]	Business hours + on-call
Tier 3	[Engineering On-Call]	[Eng Manager]	24/7 via PagerDuty
Tier 4	[VP Engineering]	[CTO]	24/7 via phone

---

Automatic Escalation Triggers

Trigger	Action
P1 ticket open > 15 min without response	Auto-escalate to Tier 2
P2 ticket open > 2 hours without update	Notify Team Lead
Any ticket open > 24 hours without progress	Auto-escalate one tier up
Customer mentions "cancel," "legal," or "lawyer"	Alert Team Lead immediately
CSAT < 2 on a resolved ticket	Flag for manager review
Same customer contacts 3+ times about the same issue	Auto-escalate to Tier 2

---

Escalation Etiquette

1. Always inform the customer that their issue is being escalated and explain what happens next
2. Include full context in the escalation — ticket history, steps tried, screenshots, logs
3. Never escalate without attempting to resolve at your tier first (minimum 15 min effort for Tier 1)
4. The escalating agent stays on the ticket until the next tier confirms they've picked it up
5. Post-escalation updates go to both the customer and the original agent

---

De-escalation

Once the issue is resolved at a higher tier, it is handed back to the original tier for:

• Customer notification
• CSAT survey
• Knowledge base article creation (if applicable)
• Ticket closure