Escalation Workflow Template
L1–L3 escalation matrix with triggers, notification rules, SLA breach actions, and role definitions. Configure and enforce from day one.
Included Templates
L1 — Frontline Support
Scope: General inquiries, account questions, known issues with documented fixes. Skills: Product knowledge, CRM navigation, template responses. Resolve Target: 80% of tickets. Escalation Trigger: Cannot resolve within 30 minutes or issue requires system access.
L2 — Technical Support
Scope: Complex technical issues, integration problems, configuration changes. Skills: Technical troubleshooting, API knowledge, admin access. Resolve Target: 90% of escalated tickets. Escalation Trigger: Requires code change, infrastructure access, or vendor coordination.
L3 — Engineering / Management
Scope: Bugs, outages, architectural issues, executive complaints. Skills: Code-level debugging, infrastructure management, stakeholder communication. Resolve Target: 100%. Escalation Trigger: Customer escalation to executive, SLA breach at L2.
Time-Based Triggers
P1: L1→L2 after 15 min, L2→L3 after 1 hour. P2: L1→L2 after 30 min, L2→L3 after 2 hours. P3: L1→L2 after 2 hours, L2→L3 after 8 hours. P4: L1→L2 after 8 hours, L2→L3 after 24 hours.
Condition-Based Triggers
Customer requests manager: Auto-escalate to L2 lead. VIP customer: Skip L1, route directly to L2. Negative CSAT: Auto-escalate to team lead. Repeated contact (3+ messages): Flag for proactive escalation.
L1 → L2 Notifications
Notify: L2 team via inbox assignment + Slack #support-escalations. Include: Ticket summary, customer history, L1 resolution attempt notes. SLA: L2 must acknowledge within 10 minutes.
L2 → L3 Notifications
Notify: Engineering lead via PagerDuty (P1/P2) or Email (P3/P4). Include: Full ticket timeline, technical diagnosis, impact assessment. SLA: L3 must acknowledge within 15 minutes for P1.
Customer Communication
On escalation: Send customer update — 'Your issue has been escalated to our specialist team. We'll update you within {{time_frame}}.' On resolution: Send resolution summary with prevention steps.
De-Escalation Rules
L3→L2: When code fix is deployed and verified, ticket returns to L2 for customer communication. L2→L1: When L2 creates a knowledge article, similar future issues stay at L1.
How to Use
- 1
Define Teams
Create L1, L2, and L3 teams in Lodgestory. Assign agents to each tier based on skill level.
- 2
Configure Routing Rules
Set up routing rules that direct tickets to L1 by default with overflow rules for VIP customers.
- 3
Set Escalation Triggers
Configure time-based and condition-based escalation triggers for each priority level in SLA settings.
- 4
Set Up Notifications
Configure escalation notifications via inbox, Email, Slack, and PagerDuty for each tier transition.
- 5
Monitor & Refine
Track escalation rates, time-to-escalate, and resolution rates per tier. Adjust triggers quarterly.
Tips for Best Results
- Aim for 80% L1 resolution — if it's lower, your knowledge base needs work
- Never skip tiers except for P1 outages and VIP executive complaints
- Every escalation should include a summary of what L1 already tried
- De-escalation is as important as escalation — build knowledge articles for recurring L2/L3 issues
- Review escalation patterns monthly to identify training gaps at L1
Frequently Asked Questions
How do I set up automatic escalation in Lodgestory?
Can I escalate to external teams?
How do I track escalation rates?
Can VIP customers skip L1?
What about customer communication during escalation?
Start using these templates today
Included in every Lodgestory plan. Customise and send in minutes.