Settingsintermediate

Risk states reference

The four SLA risk states, how a conversation moves between them, and what happens to the timer when a conversation reopens or closes. Includes the one-way escalation rule and the First Reply Time reopen exception.

4 min read

Risk states reference

Every conversation with an active SLA policy moves through one or more risk states. This reference covers what each state means, how a conversation gets there, and what happens at the boundaries.

The four states

  • SLA — Grey — Policy is active. Plenty of time remaining. — Carry on; no urgency
  • At risk — Yellow — First threshold crossed. The window for a clean response is narrowing. — Look at it now if it’s yours; reassign if you can’t
  • Urgent — Red — Last threshold before breach. Minutes-to-hours from violation, depending on policy. — Drop everything that isn’t more urgent
  • Breach — Red, overdue — The SLA target was missed. Timer flipped to count up. — Respond as fast as possible to minimize impact

The visual indicators are consistent everywhere SLAs are surfaced: conversation list rows, the conversation header, the inbox sidebar counters, Analytics dashboards.

Escalation is one-way

A conversation’s risk state only climbs:

SLA → At risk → Urgent → Breach

It never walks back down while the timer runs. A timer pause (going outside office hours) does not return the badge to a calmer state. An agent reply ends a First Reply or All Messages timer, and the badge becomes Met or Breached. The exception is a reopen that restarts the timer: it begins a fresh countdown (see On reopen).

This is intentional. The risk state captures the worst point the conversation reached during the SLA’s life — useful for retrospectives (“how many of our resolved conversations breached at some point?”). If a conversation hit At risk and you replied in time, a First Reply or All Messages badge shows Met.

Apart from an agent reply, resets include closing the conversation and, when an Agent Stack’s reply had stopped the timer, the handover to a person (see the next sections). On reopen, some metrics restart their timer.

On reopen

When a conversation moves from done back to active (because the customer replied), whether the timer restarts depends on the metric:

First Reply Time and All Messages restart only if nobody had replied before the close. If a reply had already stopped the timer, it stays stopped and the badge keeps its Met or Breached result. An answered First Reply never restarts; an All Messages timer starts again when the customer writes again.

Resolution Time restarts on every reopen. It gets a new countdown — you have the full target duration again to resolve the reopened conversation. A timer that restarts begins a fresh countdown even if it had breached before the close.

On a team or channel change

When an agent or a team lead moves the conversation to another team, an automation assigns it, the AI hands it over, or the conversation switches channel, the SLA is chosen again for the new team and channel, and its deadline is counted again in the new team’s opening hours. The clock keeps the time the customer wrote in; it does not start again. The deadline can move later (the new team has shorter hours) or earlier (the new team has longer hours, or is open 24/7).

Two SLAs stay as they are:

  • An SLA that an automation set.
  • An SLA whose timer a reply already stopped, such as a First Reply SLA that is already answered. Its Met or Breached result does not change. This includes a First Reply SLA that the AI already answered: it stays Met or Breached after a handover, as long as the SLA chosen for the new team is also a First Reply SLA.

There is one exception to “the clock does not start again”. If an Agent Stack’s reply had stopped the timer and the new team’s policy is not a First Reply SLA, the handover starts a new timer for that policy at the moment of handover, counted in the team’s opening hours.

The Agent Stack’s handover message does not stop this timer. A person’s first reply does, unless the policy is a Resolution Time policy.

On close

When a conversation moves to done, the live countdown freezes. The badge flips from a counting timer to a static label:

  • Met — the metric was satisfied within target
  • Breached — the metric exceeded target before close

The final status is calculated once, at close. If the conversation later reopens and the timer restarts, the badge starts a new countdown and that close result is replaced. When an agent’s reply stops a First Reply or All Messages timer, whether it was on time is stored, so it still counts in Analytics after a reopen.

A breached SLA can’t be un-breached

Once the timer hits zero, the SLA is breached. There’s no “set the badge back to Urgent” override. A badge only leaves Breached when its timer starts again on its own: after a reopen (see On reopen) or, for All Messages, when the customer writes again.

What you can do: respond as fast as possible to minimize the negative-time count and the customer-impact window. The breach is logged regardless, but a 30-minute breach is meaningfully better than a 5-hour breach.

No history of earlier SLAs

A conversation keeps only its current SLA: the policy, the priority band, the start time and the due time. When the SLA is chosen again (for example, after a team or channel change) or the timer restarts, these are overwritten, and there is no record of the earlier ones.

What is kept: when an agent’s reply stops a First Reply or All Messages timer, the due time it was measured against and whether it was on time are stored, so that reply still counts in Analytics.

See also

Tags

Reference