How to stop missing SLA breaches in Intercom

Intercom's SLA feature is good at one thing: telling you, after the fact, that you missed a target. By the time a conversation shows up as "breached" in your reporting, the customer has already been waiting too long — and there's nothing left to do but apologize.

The problem with after-the-fact reporting

SLA reports are useful for spotting trends over a week or a month, but they're useless in the moment. A support lead reviewing yesterday's SLA misses can't go back in time and reply faster. What teams actually need is a warning before the breach happens — while a teammate can still pick up the conversation.

Pre-breach alerts, based on Intercom's own timers

Support Alerts reads the next_breach_at value Intercom already calculates for every conversation under an SLA — the same value that accounts for office hours, holidays, and snoozes. When a conversation is within your configured warning window (say, 10 minutes) of breaching, an alert fires automatically.

• No separate SLA configuration to maintain — it mirrors what's already set up in Intercom.
• Office hours and holiday schedules are respected automatically.
• Alerts can go to the assigned agent, a shared channel, or both.
• If nobody acknowledges in time, escalation chains kick in.

Setting it up

Create a rule with the "SLA about to breach" trigger, set a warning window in minutes, and choose where the alert should go. That's it — the next time a conversation approaches its SLA deadline, your team will know before the customer does.