Skip to main content

SLA-Breach Watchdog: Auto-Escalate Breached Tickets

By the end of this recipe, no support ticket sits silently past its deadline — the moment a ticket breaches its SLA, Copera flags the row, summarizes what the customer needs, and escalates it to the owner and your support lead, automatically. Because your tickets, your SLA timers, and your team chat all live in one workspace, the escalation reaches the right person the instant the clock runs out, instead of surfacing hours later in a report nobody reads in time.

Readiness: Available now (built as an Automation). The version where a single named teammate watches SLAs across every board and escalates on its own is rolling out in early access.

What it does​

The moment a ticket's SLA countdown timer passes its goal — resolve within 4 hours, first response within 30 minutes, whatever your agreement says — this watchdog acts. It doesn't wait for a human to notice the red timer on the board; it fires on the breach itself and drives the escalation for you.

A breach is not a mystery event you have to poll for. On your ticket board, a Countdown SLA timer already turns amber at 75% of the goal, red at 90%, and red-pulsing the instant it breaches. This watchdog turns that final, unmissable state into action. When a ticket breaches, it:

  • Flags the row Escalated and stamps the exact breach time, so the miss is on the record and shows up in every filter and view.
  • Summarizes the case — an AI step condenses the subject, description, and latest replies into a one-line "here's what the customer needs and why it's stuck," so no one has to open the ticket to understand it.
  • Escalates to the owner with a direct message they can't miss, and loops in your support lead by posting the breached ticket and a link to a support-leads channel.

The key distinction from a deadline concierge, which nudges before a due date, is that a watchdog fires on the breach — the point at which a promise to a customer has actually been broken and someone needs to own the recovery now:

The signalWhat the watchdog doesWho hears about it
SLA timer breaches (goal exceeded)Flags Escalated, stamps the breach time, drafts a one-line summaryThe ticket owner (direct message) and the support lead (channel)
Optional: approaching breach (early warning)Warns while the countdown is still amber, before the promise breaksThe ticket owner, privately
Optional: urgent tier (condition on priority)Alerts a lead immediately and drafts a customer emailThe lead, plus a draft for a human to send

Build it yourself​

Give every ticket an SLA timer

On your support board, add a Countdown SLA column with a goal duration (for example, 4 hours to resolve). Configure it to start when a ticket enters Open or In Progress, pause on Waiting for Customer, and stop on Resolved or Closed — so the clock only runs while your team is actually responsible. Attach a business calendar if your SLA counts working hours, not overnight. This live timer is the signal the whole watchdog runs on.

Trigger: SLA breached

In Automations, add an SLA breached trigger on the support table. It fires for a specific ticket the exact moment its SLA timer passes its goal — no polling, no scheduled scan, no gap between the breach and the response.

Condition: route by severity (optional)

Add a condition right after the trigger to keep the response proportional. A Compare check — Priority equals Urgent or High — can split the flow: urgent breaches take the full escalation below, while routine ones just message the owner. Skip this if every breach deserves the same treatment.

AI step: summarize the case

Add an AI → Summarize step that condenses the ticket — subject, description, and latest replies — into a one-line note of what the customer needs and why it stalled. This is what makes the escalation instantly readable: the owner and lead see the situation without opening the ticket.

Actions: flag and stamp the breach

Add a Set field action to move the ticket's status to Escalated, and a Set date to now action to stamp a Breached at column. Now the miss is visible on the board, sortable, and countable — you can build a view of everything that breached this week from these two fields alone.

Actions: escalate to the owner and the lead

Add a Send direct message action to the ticket's assigned owner with the summary and a link to the row — a ping they can act on in one click. Then add a Post channel message action to your support-leads channel so leadership sees the breach in real time. Prefer a quieter escalation? Swap the channel post for a Send notification or Assign user(s) action that pulls a manager onto the row.

tip

Catch it before it breaks. The watchdog above fires on the breach. To warn before it, stamp a Resolution due date when a ticket opens (a Set date relative action — created time plus your SLA window), then add a second automation with a Date reached trigger set a chosen time before that date — say 30 minutes before a 4-hour SLA. It direct-messages the owner while the countdown is still amber, so many breaches never happen. Same board, one extra automation, a complete early-warning system.

tip

One trigger per automation, so tier with conditions. An automation has exactly one trigger, but a condition block can branch it. Trigger once on SLA breached, then branch: Urgent → post to the leads channel, assign a manager, and draft a customer email; everything else → just DM the owner. One watchdog, a response scaled to how much the breach actually matters.

Or just ask Copera AI​

You don't have to assemble the graph by hand. Open Ask Copera AI and describe the watchdog:

"On our Support board, build an automation: when a ticket's SLA breaches, summarize what the customer needs, set the ticket's status to Escalated, direct-message the assigned owner that it's breached, and post the ticket with a link to the #support-leads channel."

Ask Copera AI plans, drafts, validates, and creates the automation graph for you — the SLA-breached trigger, the summarize step, and the set-field and messaging actions — then hands it back for review. With the default Ask before acting permission mode, it shows a review card before the automation is created, so you approve the wording and the routing before anything goes live.

It also handles the one-off sweep on demand: "Which tickets on the Support board have breached their SLA and aren't resolved? Summarize each and DM the owners." It reads the board, lists the current breaches, and messages each owner — no waiting for the next event. See What Copera AI Can Do for the full list of actions it can take.

Make it a standing teammate​

Early access

Standing AI teammates are rolling out gradually. When one reaches your workspace, a named "SLA Watchdog" teammate can own this end to end: watch SLA timers across every support board, escalate each breach to its owner, loop in the right lead, keep the breached-ticket view current, and report the week's misses — all on its own schedule, under its own identity. Until then, the automation above does this today. Everything here can be built now as an Automation.

Tips​

tip

Pause the clock when the ball is in the customer's court. Configure the SLA column to pause on a Waiting for Customer status so the timer never counts time that isn't your team's fault — and the watchdog never fires for it. You can also start, pause, or stop the timer from an automation with the SLA timer control action when a status change alone isn't enough.

tip

Read the room with sentiment. Add an AI → Sentiment or AI → Classify step before you escalate, so a furious or VIP customer's breach routes straight to a manager while a routine one just pings the owner. The breach is the trigger; the tone decides how loud the alarm is.

tip

Keep anything customer-facing behind a draft. Internal direct messages and channel posts can send straight through — nobody outside sees them. But if a rung of your escalation emails the customer an apology or an update, use draft or approval delivery on the Send or draft email action so a human signs off on the wording first.

tip

Set a spend cap on the watchdog. Because it runs an AI summary on every breach, give the automation a per-automation spend cap and watch the usage dashboard. A rough day full of breaches can then never run past a budget you choose — the run simply stops and reports it.

Frequently Asked Questions​

Can Copera automatically escalate a ticket when its SLA is breached?​

Yes. An SLA breached trigger fires the moment a ticket's SLA countdown timer passes its goal. The automation can flag the row Escalated, stamp the breach time, direct-message the assigned owner, and post the ticket to a support-leads channel — all without anyone watching the clock.

How does Copera know an SLA has been breached?​

Each ticket carries a Countdown SLA timer with a goal duration, such as resolve within 4 hours. When elapsed time passes that goal, the timer breaches and fires the automation. If the SLA column uses a business calendar, the breach is measured in working hours, so it never fires for nights or weekends your team wasn't on the clock.

Does the watchdog escalate before or after the SLA breaks?​

The core watchdog fires on the breach itself. To catch it earlier, add a companion automation with a Date reached trigger set a chosen time before the resolution-due date, so the owner gets a warning while the countdown is still amber and there's time to recover.

Who gets notified when a ticket breaches its SLA?​

Whoever you choose. The common pattern direct-messages the ticket's assigned owner and posts to a support-leads channel, but you can also send an in-app notification, assign a manager to the row, or draft an email — and route urgent breaches differently with a condition on priority.

Can it prioritize which breaches get escalated hardest?​

Yes. Put a condition right after the trigger that checks the ticket's priority or tier. Urgent breaches can alert a lead and draft a customer email, while routine ones just message the owner — one watchdog, a tiered response.