Eve library

Escalation Procedures

Runbook

Revision 1

On this page

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:

  1. Security Incidents

    • Account compromise reported
    • Data breach suspected
    • Payment fraud detected
    • Harassment/threats
  2. Safety Concerns

    • User expresses self-harm intent
    • AI generated harmful content
    • Minor safety issue
  3. Legal/Compliance

    • Subpoena or legal request
    • GDPR/CCPA data requests
    • Copyright claims
    • Government inquiry
  4. 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:

  1. Set reminder to check status in 2 hours
  2. Update customer with escalation confirmation
  3. Monitor escalation channel for updates
  4. 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#

  1. Do NOT promise anything or admit fault
  2. Do acknowledge their concern professionally
  3. Do use template: LEGAL-THREAT-001
  4. Escalate immediately to Legal team
  5. Document all communication verbatim
  6. Pause any account actions pending legal review

Customer Expresses Self-Harm#

  1. Do express genuine concern
  2. Do provide crisis resources:
    text
    National Suicide Prevention Lifeline: 988
    Crisis Text Line: Text HOME to 741741
    International: findahelpline.com
    
  3. Do let them know we care
  4. Escalate to Support Manager immediately
  5. Do NOT try to counsel or provide therapy
  6. Do NOT minimize their feelings

Media/Press Inquiry#

  1. Do NOT provide any statement
  2. Respond: "I'm not authorized to speak with media. Let me connect you with our communications team."
  3. Escalate immediately to Communications/PR
  4. Document reporter name, outlet, and inquiry
  5. Do NOT share customer information

VIP/Celebrity Customer#

  1. Verify identity carefully
  2. Escalate to Tier 2 immediately (even simple issues)
  3. Protect privacy strictly (no screen sharing, no public discussion)
  4. Document minimally (use initials, no screenshots with PII)

De-escalation Techniques#

Before escalating, attempt de-escalation:

When Customer is Frustrated#

  1. Acknowledge their frustration

    • "I understand this is frustrating, and I'm sorry you're dealing with this."
  2. Take ownership

    • "Let me personally make sure we get this resolved for you."
  3. Set clear expectations

    • "Here's exactly what I'm going to do and when you'll hear back."
  4. Offer small win

    • "While we work on the larger issue, let me [quick fix] for you right now."

When Issue is Complex#

  1. Break it down

    • "Let's solve this one piece at a time. First..."
  2. Confirm understanding

    • "Let me make sure I understand correctly: [restate issue]"
  3. Provide timeline

    • "This will take some time to investigate properly. I'll update you by [time]."

When Customer Demands Escalation#

  1. Understand the ask

    • "I hear that you'd like this escalated. Can you help me understand what outcome you're hoping for?"
  2. Offer alternatives

    • "I may be able to resolve this without escalation. Would you be willing to try [solution] first?"
  3. Escalate gracefully

    • "Absolutely, I'll escalate this right now. My colleague [Name] will be in touch within [timeframe]."

Post-Escalation Follow-Up#

After resolution:

  1. Confirm with customer that issue is fully resolved
  2. Update ticket with complete resolution details
  3. Add to knowledge base if new issue type
  4. Feedback to escalation team on resolution effectiveness
  5. 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