A service level agreement (SLA) breach is recorded when a ticket exceeds the time threshold set for first response, next reply, or full resolution. Breaches are typically tracked automatically by the support platform, which timestamps each status change against the agreed SLA policy.
Why it matters: SLA breaches are contractual failures for enterprise and B2B customers and can trigger financial penalties, escalations, or churn. Even for consumer support without formal contracts, breach rates serve as a leading indicator of team capacity problems or workload spikes.
Common causes of breaches:
- Unexpected volume spikes (product incidents, seasonal demand)
- Understaffing or scheduling gaps
- Tickets stuck in the wrong queue
- Overly aggressive SLA commitments
Key metrics to monitor:
- SLA breach rate (breached tickets ÷ total tickets)
- Breach rate by priority tier or channel
- Mean time over SLA threshold
Reducing breach rate requires both operational fixes (staffing, routing) and strategic ones (setting realistic SLA targets and communicating them clearly to customers).