Connect to IntercomEscalation Rate
Escalation Rate measures the percentage of support tickets that require escalation to a higher support tier, specialized team, or management because the frontline agent cannot resolve them independently. It signals how often Tier 1 is unable to handle incoming requests. A high escalation rate can indicate insufficient agent training, unclear escalation criteria, or product complexity that exceeds frontline capability. A very low rate can also be a red flag — it may mean agents are closing tickets prematurely rather than escalating when appropriate.
Escalation Rate = (Tickets escalated to Tier 2 or above ÷ Total tickets received) × 100
Define "escalation" precisely before tracking — routing to a specialist queue is different from escalating to a manager. Track both separately if both paths exist in your workflow. Escalation is upward movement (Tier 1 → Tier 2); transfer is lateral (billing team → technical team).
B2B SaaS, Tier 1 first-contact team
Calculate your escalation rate
- 1Not distinguishing skill escalations from volume escalations — skill escalation (wrong team) is a training issue; volume escalation (overflow routing) is a staffing issue.
- 2Treating zero escalations as success — some product complexity genuinely requires specialist knowledge; artificially suppressed escalation rate means frontline agents are guessing.
- 3Not tracking time-to-escalate — late escalations waste more time than immediate ones and damage CSAT.
- 4Conflating escalation rate with transfer rate — escalation is upward (Tier 1 → Tier 2); transfer is lateral across teams at the same tier.