Route multi-tier support tickets using policy-defined escalation triggers and handoffs.
npx skills add https://github.com/erphq/skills --skill escalation-erphq
Please help me install this Agent Skill. Skill: escalation Source: https://github.com/erphq/skills/tree/main/departments/customer-support/03-org-1k-plus/escalation Command: npx skills add https://github.com/erphq/skills --skill escalation-erphq
Escalation management solves the challenge of routing tickets when expertise, authority, or urgency exceed the current handler's capability. It defines clear paths for L1-L3 tier escalations, functional and management escalations, and after-hours on-call procedures to preserve customer satisfaction and SLA commitments.
Configure an initial escalation policy by defining tier criteria and on-call routing for typical tickets.
High-intent search queries and answers about installing and using this skill.
Automate tiered support ticket routing by defining escalation policies that detect issue type and SLA urgency, then route tickets to appropriate L2 or L3 specialists automatically. This preserves customer satisfaction by ensuring tickets reach the correct expertise level without manual delay.
On-call management uses defined escalation triggers and routing policies to contact available team members during after-hours incidents. It applies tier-based criteria to notify the correct specialist, maintaining SLA commitments when standard support channels are unavailable.
Context-preserving handoff transfers customer history, attempted actions, and diagnostic data alongside escalated tickets. This prevents customers from repeating information across L1 to L3 tiers, reducing resolution time and frustration during complex incident management.
Configure de-escalation rules within your escalation policy definitions to automatically downgrade or close tickets once resolution criteria are met. This ensures resolved incidents exit the tiered support routing queue, freeing specialist capacity for active escalations.
Functional escalation routing is needed when an issue requires expertise outside the current handler's department, such as vendor escalations or management escalations. It uses customizable policies to transfer tickets across multi-team operations while preserving context.
Yes, you can customize escalation policies to cover functional, management, and vendor escalations across multi-team operations. Define tier criteria and on-call routing parameters to match your specific SLA requirements and support center workflows.
manutejAnalyze customer-support ticket data for SLA compliance and agent performance.
AbsolutelySkilledAutomate customer-support triage, SLA management, macros, and escalation workflows.
masharrattDetect intervention requirements during CFN Loop iterations using configurable thresholds.
GACLoveClassify, prioritize, and route incoming support tickets with P1-P4 and tier rules.
