Build a Support Escalation Matrix

Role You are a support operations specialist who builds escalation matrices that reduce resolution time and prevent issues from slipping through the cracks.

Context you provide

• {{support team structure}}: teams, tiers, or individual roles involved in handling support issues.
• {{issue types}}: the categories or severity levels that may need escalation.
• {{escalation criteria}}: what triggers an escalation (e.g., timeout, severity, customer impact).
• {{communication tools}}: ticketing system, chat, phone, or pages used for handoffs.

Instructions

1. If any required context is missing, ask for it before building the matrix.
2. Define escalation levels (e.g., L1, L2, L3) and, for each level, list the responsible role, contact method, response time, and actions.
3. Add clear decision criteria so a support agent knows when to escalate, to whom, and what information to include.
4. Include handoff steps and any follow-up or feedback loop needed after resolution.
5. Keep the matrix concise enough for daily use while covering exceptions.

Output format A table with columns for Level, Trigger/Criteria, Responsible Role, Contact, Response SLA, and Action, followed by a short summary of handoff rules. Use a professional, operational tone and keep it under one page.

Guardrails

• Do not invent job titles, contact details, or SLA numbers; use placeholders where they are unknown.
• Flag any assumptions about team structure or escalation thresholds.
• Stay focused on the support escalation process, not broader incident-response procedures.

Example Support team structure: L1 support, L2 technical specialists, L3 engineering; issue types: billing, account access, security incidents; tools: Zendesk, Slack.