Escalation Protocol Document
Customer Issue Escalation & Crisis Management Framework
Protocol Overview
Escalation Metrics
Severity Level Definitions
Definition: Complete service outage or critical functionality unavailable. Major business impact affecting multiple users or entire organization.
Examples:
- Complete platform outage (cannot login, 500 errors)
- Data loss or corruption affecting customer records
- Security breach or data privacy incident
- Payment processing failure preventing business operations
- Executive escalation with threat of cancellation
Definition: Major functionality degraded. Significant business impact but workaround available.
Examples:
- Core feature not working (reports, dashboards, integrations)
- Performance severely degraded (5x+ slower than normal)
- Multiple users unable to complete key workflows
- Renewal at risk due to unresolved issues
- Negative NPS feedback with specific concerns
Definition: Partial functionality affected. Moderate business impact with acceptable workaround.
Examples:
- Non-critical feature bug or inconsistency
- UI/UX issues affecting usability
- Minor performance degradation
- Customer dissatisfaction requiring attention
- Request for product enhancement or customization
Definition: Minor issue with minimal business impact. Cosmetic or nice-to-have improvements.
Examples:
- Cosmetic/visual issues (alignment, colors, typos)
- General questions or feature inquiries
- Documentation requests
- Low-priority feature suggestions
- General feedback or recommendations
Escalation Flow & Process
CSM or Support Agent identifies issue, assesses severity level (P1-P4), and documents in ticketing system with all relevant details.
Acknowledge issue to customer within defined SLA. Provide ticket number, expected response timeline, and point of contact.
For P1/P2: Immediately notify Team Lead → Manager → VP → C-Level (as needed). Assemble cross-functional response team.
Technical team investigates root cause. Provide regular updates to customer (hourly for P1, daily for P2, as needed for P3/P4).
Implement fix, deploy to production, and validate with customer. Ensure issue is fully resolved before closing ticket.
Conduct debrief with customer and internal team. Document lessons learned, implement preventive measures, and monitor account health.
Escalation Contact Matrix
| Escalation Level | Role/Title | Name | Phone | |
|---|---|---|---|---|
| Level 1 | Customer Success Manager | |||
| Level 2 | CS Team Lead / Manager | |||
| Level 3 | VP of Customer Success | |||
| Level 4 | Chief Customer Officer (CCO) | |||
| Level 5 | CEO / Executive Leadership | |||
| Technical | Engineering Lead / CTO | |||
| Product | Product Manager / CPO |
Communication Templates
Initial Acknowledgment (P1/P2)
Status Update Template
Resolution Confirmation
Escalation Response Checklist
| Action Item | P1 | P2 | P3 | P4 |
|---|---|---|---|---|
| Acknowledge within SLA | 15 min | 1 hour | 4 hours | 1 day |
| Create ticket in system | ✓ | ✓ | ✓ | ✓ |
| Notify internal team (Slack/Email) | ✓ | ✓ | — | — |
| Escalate to Manager/VP | ✓ | If needed | — | — |
| Assemble response team | ✓ | If needed | — | — |
| Schedule customer call | ✓ | ✓ | If needed | — |
| Provide hourly updates | ✓ | — | — | — |
| Document root cause | ✓ | ✓ | ✓ | If applicable |
| Conduct post-mortem review | ✓ | ✓ | If needed | — |
| Monitor account health post-resolution | 30 days | 14 days | 7 days | — |
Best Practices & Guidelines
| Principle | Guidance |
|---|---|
| Speed & Transparency | Respond quickly and communicate frequently. Over-communication is better than silence during escalations. |
| Empathy & Ownership | Take ownership of the issue, even if it's not your fault. Show empathy for the customer's frustration. |
| Set Realistic Expectations | Be honest about timelines. Under-promise and over-deliver when possible. |
| Document Everything | Keep detailed notes in the ticketing system. Document all customer interactions and internal discussions. |
| Escalate Early | Don't wait too long to escalate. If you're uncertain, involve your manager immediately. |
| Follow Through | After resolution, schedule a follow-up call to ensure customer satisfaction and rebuild trust. |
| Learn & Improve | Conduct post-mortem reviews for P1/P2 issues. Identify preventive measures and update processes. |
