CX & Support Metrics

SLA Breach

Definition

An SLA breach occurs when a support team fails to meet a target defined in a Service Level Agreement — for example, not sending a first response or resolving a ticket within the promised time window.

Also known as: SLA violationSLA missmissed SLA

How it works

An SLA sets measurable commitments, such as "first response within 1 hour" or "resolution within 24 hours," often varying by ticket priority. Each ticket has a clock; when the clock runs past the target before the required action happens, the ticket is marked breached.

Help desks track this automatically, usually flagging tickets that are approaching their target so agents can act before a breach occurs rather than after.

Why it matters

Breaches are the concrete failures behind aggregate metrics. They can carry contractual penalties, erode trust, and signal capacity or routing problems. Watching breach rate and near-breaches is how teams manage risk in real time, not just report on it afterward.

Measured against response and resolution targets, often per priority
Frequently tracked as a breach rate: breached tickets ÷ total tickets
Prevention (acting before the clock runs out) matters more than reporting

Frequently asked

What causes SLA breaches?

Common causes include understaffing, poor ticket routing, unclear ownership, and volume spikes. Automating first responses and routing routine tickets to AI can protect SLAs by keeping clocks from running out.

How is SLA breach rate calculated?

Typically breached tickets ÷ total tickets subject to that SLA × 100, over a period. Teams often break it out by SLA type (response vs resolution) and priority.

Related terms

Service Level Agreement (SLA)

A Service Level Agreement (SLA) is a defined commitment to respond to or resolve support requests within a set time, often varying by priority, channel, or customer tier..

SLA Policy

An SLA policy is the configured set of rules inside a help desk that assigns service-level targets — like first-response and resolution times — to tickets based on conditions such as priority, channel, or customer tier..

First Response Time (FRT)

First Response Time (FRT) is the average time between when a customer submits a support request and when they receive the first human or meaningful reply..

Ticket Aging

Ticket aging is a measure of how long open support tickets have been unresolved, usually grouped into buckets (for example 0–1 days, 1–3 days, 3–7 days, 7+ days) to show where tickets are getting stuck..

Escalation

Escalation is the process of moving a support ticket to a higher tier, a specialist, or a manager when the current agent can't resolve it or when it risks breaching an SLA..

Put these ideas to work

Macha is an AI agent layer that sits on top of the help desk you already run — Zendesk, Freshdesk, Front, Intercom, or Gorgias.

Start Trial