Support Escalation
Determine when and how to escalate support issues. Structure escalation briefs that give receiving teams everything they need to act quickly, and follow escalation through to resolution.
When to Escalate
- Technical: Bug confirmed and needs a code fix, infrastructure investigation, data corruption.
- Complexity: Beyond support's ability to diagnose, requires access support doesn't have.
- Impact: Multiple customers affected, production system down, security concern.
- Business: High-value customer at risk, SLA breach imminent, executive involvement.
- Time: Issue has been open beyond SLA, customer waiting unreasonably long.
- Pattern: Same issue reported by 3+ customers.
Escalation Tiers
- Support Escalation (L1 -> L2): For deeper investigation or advanced troubleshooting.
- Engineering Escalation: For confirmed bugs, infrastructure issues, code changes.
- Product Escalation: For feature gaps, design decisions, prioritization.
- Security Escalation: For potential data exposure, vulnerabilities, compliance (Escalate IMMEDIATELY).
- Leadership Escalation: For high churn risk, SLA breaches, cross-functional decisions.
Structured Escalation Format
Every escalation should follow this structure:
ESCALATION: [One-line summary]
Severity: [Critical / High / Medium]
Target: [Engineering / Product / Security / Leadership]
IMPACT
- Customers affected: [Number and names if relevant]
- Workflow impact: [What's broken for them]
- Revenue at risk: [If applicable]
- SLA status: [Within SLA / At risk / Breached]
ISSUE DESCRIPTION
[3-5 sentences: what's happening, when it started, how it manifests, scope of impact]
REPRODUCTION STEPS (for bugs)
1. [Step]
2. [Step]
3. [Step]
Expected: [X]
Actual: [Y]
Environment: [Details]
WHAT'S BEEN TRIED
1. [Action] -> [Result]
2. [Action] -> [Result]
3. [Action] -> [Result]
CUSTOMER COMMUNICATION
- Last update: [Date — what was said]
- Customer expectation: [What they expect and by when]
- Escalation risk: [Will they escalate further?]
WHAT'S NEEDED
- [Specific ask: investigate, fix, decide, approve]
- Deadline: [Date/time]
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: support-escalation3description: Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when this capability is needed.4---56# Support Escalation78Determine when and how to escalate support issues. Structure escalation briefs that give receiving teams everything they need to act quickly, and follow escalation through to resolution.910## When to Escalate1112- **Technical**: Bug confirmed and needs a code fix, infrastructure investigation, data corruption.13- **Complexity**: Beyond support's ability to diagnose, requires access support doesn't have.14- **Impact**: Multiple customers affected, production system down, security concern.15- **Business**: High-value customer at risk, SLA breach imminent, executive involvement.16- **Time**: Issue has been open beyond SLA, customer waiting unreasonably long.17- **Pattern**: Same issue reported by 3+ customers.1819## Escalation Tiers20211. **Support Escalation (L1 -> L2)**: For deeper investigation or advanced troubleshooting.222. **Engineering Escalation**: For confirmed bugs, infrastructure issues, code changes.233. **Product Escalation**: For feature gaps, design decisions, prioritization.244. **Security Escalation**: For potential data exposure, vulnerabilities, compliance (Escalate IMMEDIATELY).255. **Leadership Escalation**: For high churn risk, SLA breaches, cross-functional decisions.2627## Structured Escalation Format2829Every escalation should follow this structure:3031```markdown32ESCALATION: [One-line summary]33Severity: [Critical / High / Medium]34Target: [Engineering / Product / Security / Leadership]3536IMPACT3738- Customers affected: [Number and names if relevant]39- Workflow impact: [What's broken for them]40- Revenue at risk: [If applicable]41- SLA status: [Within SLA / At risk / Breached]4243ISSUE DESCRIPTION44[3-5 sentences: what's happening, when it started, how it manifests, scope of impact]4546REPRODUCTION STEPS (for bugs)47481. [Step]492. [Step]503. [Step]51 Expected: [X]52 Actual: [Y]53 Environment: [Details]5455WHAT'S BEEN TRIED56571. [Action] -> [Result]582. [Action] -> [Result]593. [Action] -> [Result]6061CUSTOMER COMMUNICATION6263- Last update: [Date — what was said]64- Customer expectation: [What they expect and by when]65- Escalation risk: [Will they escalate further?]6667WHAT'S NEEDED6869- [Specific ask: investigate, fix, decide, approve]70- Deadline: [Date/time]71```7273---74> Converted and distributed by [TomeVault](https://tomevault.io/claim/frumu-ai) — claim your Tome and manage your conversions.75<!-- tomevault:4.0:skill_md:2026-04-11 -->
tomevault-io