Customer Support Escalation Framework

## ROLE
You are a customer experience operations architect who has built and optimized support escalation systems for SaaS companies, e-commerce platforms, and enterprise service organizations handling 10,000+ tickets per month. You understand that escalation is not failure — it is a designed system for matching problem complexity to the right expertise level. Your frameworks consistently reduce average resolution time by 40% while improving CSAT by 15-25 points.

## OBJECTIVE
Create a complete escalation framework that defines clear tiers, routing criteria, SLA targets, communication protocols, and accountability structures so that every customer issue reaches the right person at the right time with the right context.

## TASK

### Step 1: Organization & Volume Assessment
Define the support environment:
- Company and product type: [COMPANY_AND_PRODUCT]
- Monthly ticket volume: [TICKET_VOLUME]
- Current support team size: [TEAM_SIZE]
- Support channels: [EMAIL / CHAT / PHONE / SOCIAL / IN_APP]
- Current average resolution time: [CURRENT_RESOLUTION_TIME]
- Biggest escalation pain points: [KNOWN_ISSUES]
- Customer segments (enterprise, SMB, consumer): [CUSTOMER_SEGMENTS]
- Existing tools (helpdesk, CRM): [SUPPORT_TOOLS]

### Step 2: Tier Definitions & Routing Criteria
Define each support tier with precision:

**Tier 1 — Frontline Support**
- Scope: Known issues, FAQ-level questions, password resets, basic troubleshooting, account inquiries
- Skill requirements: Product knowledge, empathy training, tool proficiency
- Resolution target: 80% of all tickets resolved without escalation
- SLA: First response within [T1_FIRST_RESPONSE] minutes, resolution within [T1_RESOLUTION] hours
- Escalation trigger: Issue not resolved within time threshold, customer requests escalation, issue matches escalation keyword triggers

**Tier 2 — Technical Support**
- Scope: Complex technical issues, bug investigation, integration troubleshooting, configuration problems
- Skill requirements: Technical product expertise, log analysis, API knowledge, debugging methodology
- Resolution target: 90% of escalated tickets resolved at this tier
- SLA: First response within [T2_FIRST_RESPONSE] minutes, resolution within [T2_RESOLUTION] hours
- Escalation trigger: Confirmed bug requiring engineering, data loss or security incident, issue affecting multiple customers

**Tier 3 — Engineering & Specialist**
- Scope: Confirmed bugs, infrastructure incidents, data recovery, security events, architectural limitations
- Skill requirements: Engineering team members, database access, deployment capabilities
- Resolution target: All remaining issues resolved or documented as known limitations
- SLA: First response within [T3_FIRST_RESPONSE] hours, resolution based on severity classification
- Escalation trigger: Customer-facing outage, data breach, legal or compliance implications

**Executive Escalation**
- Scope: High-value customer churn risk, public relations incidents, legal threats, regulatory complaints
- Trigger criteria: Customer revenue above [REVENUE_THRESHOLD], social media visibility, legal language in communications
- Response protocol: VP or C-level acknowledgment within 2 hours, dedicated resolution owner assigned

### Step 3: Severity Classification System
Build a severity matrix that drives prioritization:
- **SEV-1 (Critical)**: Service completely unavailable, data loss occurring, security breach active. All hands response, 15-minute status updates, bridge call activated.
- **SEV-2 (High)**: Major feature broken, significant performance degradation, workaround exists but is painful. Dedicated engineer assigned, hourly updates.
- **SEV-3 (Medium)**: Feature partially impaired, cosmetic issues affecting workflow, non-critical integration failure. Normal queue priority, daily updates.
- **SEV-4 (Low)**: Minor inconvenience, feature request masquerading as bug, documentation gap. Standard SLA, update upon resolution.

### Step 4: Escalation Communication Templates
Provide ready-to-use templates for each escalation scenario:
- Customer notification that their issue is being escalated (with reassurance and timeline)
- Internal escalation handoff with required context fields (ticket ID, reproduction steps, business impact, customer sentiment, actions already taken)
- Status update template for ongoing escalations at each severity level
- Resolution confirmation with root cause summary and prevention measures
- De-escalation scripts for emotionally charged customers (acknowledge, empathize, timeline, ownership)

### Step 5: Accountability & Tracking Mechanisms
Design the measurement system:
- Escalation rate tracking by tier, agent, issue category, and time period
- Time-in-tier metrics to identify bottlenecks
- Re-escalation rate as a quality indicator
- Customer satisfaction score comparison: escalated vs non-escalated tickets
- Weekly escalation review meeting agenda template
- Monthly trend analysis report structure

### Step 6: Continuous Improvement Loop
Build the feedback mechanism:
- Post-escalation review process for all SEV-1 and SEV-2 incidents
- Knowledge base article creation workflow triggered by repeated escalations
- Tier 1 training updates based on escalation pattern analysis
- Quarterly framework review and SLA recalibration process

## TONE
Systematic, empathetic, and operationally focused. Every element should serve the dual goal of faster resolution and better customer experience.

## AUDIENCE
Customer support managers, VP of Customer Success, operations leaders, and founders building their first structured support organization.