Guidelines for when and how to escalate support issues to appropriate teams.
Escalation Matrix#
By Issue Type#
| Issue Category | Tier 1 | Tier 2 | Tier 3 | Engineering |
|---|---|---|---|---|
| Login/Password | Resolve | Account recovery | Security review | Auth bugs |
| Billing/Refunds | Basic refunds | Complex billing | Finance review | Payment bugs |
| App Crashes | Troubleshoot | Collect logs | Reproduce | Fix bugs |
| Content Issues | Guide user | Content team | Legal review | CDN issues |
| AI Problems | Basic help | AI safety review | Policy review | AI bugs |
| Account Compromise | Lock account | Investigation | Legal | Security team |
| Data Loss | Document | Attempt recovery | Compensation | Database team |
By Customer Tier#
| Customer Type | Initial Response | Escalation Threshold | Executive Escalation |
|---|---|---|---|
| Free | 24 hours | 3 contacts | Not applicable |
| Premium | 8 hours | 2 contacts | Manager approval |
| Pro | 4 hours | 1 contact | Auto-notify |
| Enterprise | 1 hour | Immediate | Direct line |
Escalation Triggers#
Immediate Escalation Required#
Escalate immediately without attempting resolution:
-
Security Incidents
- Account compromise reported
- Data breach suspected
- Payment fraud detected
- Harassment/threats
-
Safety Concerns
- User expresses self-harm intent
- AI generated harmful content
- Minor safety issue
-
Legal/Compliance
- Subpoena or legal request
- GDPR/CCPA data requests
- Copyright claims
- Government inquiry
-
PR Risk
- Media inquiry
- Influencer complaint
- Viral complaint potential
- Public figure involved
Standard Escalation Criteria#
Escalate to Tier 2 after:
- 2 unsuccessful resolution attempts
- Issue persists beyond 24 hours
- Technical complexity beyond Tier 1 scope
- Customer requests escalation
- Multiple users report same issue
Escalate to Tier 3/Engineering:
- Bug reproduction confirmed
- Database-level issue suspected
- System outage identified
- Security vulnerability found
Escalation Process#
Step 1: Document Everything#
Before escalating, ensure you have:
text
Required Information:
- Ticket/case number
- Customer name and tier
- Email and account ID
- Issue summary (2-3 sentences)
- Steps already taken
- Screenshots/logs collected
- Customer's preferred resolution
Step 2: Choose Escalation Path#
Tier 2 Escalation
text
Channel: #support-tier2 (Slack)
Format:
π« Ticket: [ID]
π€ Customer: [Name] ([Tier])
π Issue: [Brief summary]
β
Attempted: [What you tried]
π― Needed: [What you need from Tier 2]
Engineering Escalation
text
Channel: #support-engineering (Slack)
Format:
π Type: [Bug/Outage/Performance]
π« Tickets: [IDs of affected users]
π Reproduction: [Steps to reproduce]
π Impact: [# of users, severity]
π Logs: [Link to log collection]
Security Escalation
text
Channel: #security-incidents (Slack) + Page on-call
Format:
π¨ SECURITY INCIDENT
Type: [Account takeover/Data breach/etc.]
Affected: [User IDs or scope]
Status: [What's been done]
Evidence: [Links to logs/screenshots]
Step 3: Follow Up#
After escalating:
- Set reminder to check status in 2 hours
- Update customer with escalation confirmation
- Monitor escalation channel for updates
- Close loop with customer once resolved
Escalation Contacts#
Business Hours (9 AM - 6 PM PT)#
| Team | Primary | Secondary | Channel |
|---|---|---|---|
| Tier 2 Support | @support-tier2 | @support-lead | #support-tier2 |
| Engineering | @eng-support | @eng-oncall | #support-engineering |
| Security | @security-team | @ciso | #security-incidents |
| Billing/Finance | @billing-team | @finance-ops | #billing-support |
| Legal | @legal-team | legal@lilith.com | #legal-requests |
| AI Safety | @ai-safety | @ai-lead | #ai-safety |
After Hours#
| Severity | Contact Method |
|---|---|
| P1 Critical | Page on-call: pd trigger "Support P1: [summary]" |
| P2 High | Slack: @eng-oncall in #support-engineering |
| P3/P4 | Next business day via ticket |
Executive Escalation Path#
text
1. Support Manager
β If unresolved after 4 hours
2. Head of Support
β If customer threatens legal/media
3. VP Customer Success
β If significant financial impact
4. CEO (via EA)
Special Escalation Procedures#
Customer Threatens Legal Action#
- Do NOT promise anything or admit fault
- Do acknowledge their concern professionally
- Do use template: LEGAL-THREAT-001
- Escalate immediately to Legal team
- Document all communication verbatim
- Pause any account actions pending legal review
Customer Expresses Self-Harm#
- Do express genuine concern
- Do provide crisis resources:text
National Suicide Prevention Lifeline: 988 Crisis Text Line: Text HOME to 741741 International: findahelpline.com - Do let them know we care
- Escalate to Support Manager immediately
- Do NOT try to counsel or provide therapy
- Do NOT minimize their feelings
Media/Press Inquiry#
- Do NOT provide any statement
- Respond: "I'm not authorized to speak with media. Let me connect you with our communications team."
- Escalate immediately to Communications/PR
- Document reporter name, outlet, and inquiry
- Do NOT share customer information
VIP/Celebrity Customer#
- Verify identity carefully
- Escalate to Tier 2 immediately (even simple issues)
- Protect privacy strictly (no screen sharing, no public discussion)
- Document minimally (use initials, no screenshots with PII)
De-escalation Techniques#
Before escalating, attempt de-escalation:
When Customer is Frustrated#
-
Acknowledge their frustration
- "I understand this is frustrating, and I'm sorry you're dealing with this."
-
Take ownership
- "Let me personally make sure we get this resolved for you."
-
Set clear expectations
- "Here's exactly what I'm going to do and when you'll hear back."
-
Offer small win
- "While we work on the larger issue, let me [quick fix] for you right now."
When Issue is Complex#
-
Break it down
- "Let's solve this one piece at a time. First..."
-
Confirm understanding
- "Let me make sure I understand correctly: [restate issue]"
-
Provide timeline
- "This will take some time to investigate properly. I'll update you by [time]."
When Customer Demands Escalation#
-
Understand the ask
- "I hear that you'd like this escalated. Can you help me understand what outcome you're hoping for?"
-
Offer alternatives
- "I may be able to resolve this without escalation. Would you be willing to try [solution] first?"
-
Escalate gracefully
- "Absolutely, I'll escalate this right now. My colleague [Name] will be in touch within [timeframe]."
Post-Escalation Follow-Up#
After resolution:
- Confirm with customer that issue is fully resolved
- Update ticket with complete resolution details
- Add to knowledge base if new issue type
- Feedback to escalation team on resolution effectiveness
- Close the loop internally on Slack threads
Escalation Metrics Tracked#
| Metric | Target | Review Frequency |
|---|---|---|
| Escalation Rate | <15% of tickets | Weekly |
| Escalation Resolution Time | <4 hours (Tier 2) | Weekly |
| Re-escalation Rate | <5% | Monthly |
| Customer Satisfaction (post-escalation) | >4.5/5 | Monthly |
| False Escalations | <10% | Monthly |
Updated: January 2026 Review: Quarterly with Support Leadership