## TL;DR
Tell them plainly: the SLA was missed, by how long, and what you are doing about it. Then name the next update time. Customers dont need groveling; they need the facts and a credible plan. Hiding a breach always costs more than admitting it.

## The query

```text
SLA breach: what to tell the customer
```

## Use this when

- A response or resolution SLA was missed
- The customer noticed the breach before you did
- You need a standard breach message for the team
- An enterprise account's SLA clock expired

## Not for

- Writing the SLA policy itself
- Negotiating SLA terms or credits in contracts
- Internal SLA reporting and dashboards
- Deciding SLA targets for your team

## Steps

### 1. State the miss in the first sentence

"Our response SLA for this ticket was 4 hours, and we replied in 9." Numbers, no padding. The customer already knows; saying it first shows you track your own commitments.

Expected output: the breach stated with the target and the actual, up front.

### 2. Own it without excuses

One clean sentence: "That is on us." No "due to higher than normal volume," no "unfortunately." Explanations can come later; accountability comes first.

Expected output: an excuse-free ownership line.

### 3. Say what is happening on the ticket right now

The breach message is not the place to stall again. Name the current status and the next action: "Your issue is now with our [team], and they are [current action]."

Expected output: a live status and next step, not just an apology.

### 4. Name the next update time and keep it

"I will update you by [time] today." After a breach, the update commitment is the trust repair. Missing it again is far worse than the original breach.

Expected output: a specific update time, kept without fail.

### 5. Note any remedy your policy allows

If your SLA includes credits or remedies, mention it plainly: "Per our agreement, this qualifies for [remedy]. I have started that process." Dont make the customer ask for what the contract promises.

Expected output: the remedy initiated, not just mentioned.

## Ready-to-use template

```text
I need to be straight with you: we missed our SLA on this one.

Target: [target, e.g. first response within 4 hours]
Actual: [actual, e.g. 9 hours]
That is on us.

Where things stand: [current status and next action].
I will update you by [time] today, no exceptions.

[If applicable:] Per our agreement this qualifies for [remedy],
and I have started that process for you.
```

## Variant phrasings

### how to communicate an SLA breach to a customer

Steps 1 and 2. Numbers first, ownership second. Everything else is detail.

### missed SLA response template

The template as-is. Fill the brackets and send; dont add paragraphs around it.

### what to say when support misses the response time

Steps 3 and 4. The customer cares less about the apology than about what happens now.

## Why it happens

Teams hide breaches because they feel like failures, but customers experience the breach as a fact long before you mention it. The gap between their knowledge and your silence reads as dishonesty, not as a delay. Naming the numbers closes the gap, and the plan that follows is what actually repairs trust.

## Edge cases

- The customer did not notice the breach: tell them anyway if your policy requires it. Quiet fixes work for internal misses; contract SLAs get disclosed.
- The breach was the customer's fault (they went dark): say so kindly with the timeline. "The clock paused while we waited for [info] on [date]" is a fact, not blame.
- Repeated breaches on one account: escalate to a lead and review the account's routing. A pattern means the system failed, and one apology per ticket wont fix it.
- The remedy is unclear: say you are checking and give a time for the answer. "I am confirming what applies here and will tell you by [time]."
- Breach during an incident: one breach message per customer, referencing the incident. Dont send five separate SLA apologies for the same outage.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_3-LBKosfr04_fvTWP3OjOQ