In this section (7)

SLA targets explained

When each SLA clock starts, pauses and stops, and what achieved and breached mean.

1 min read

Available on Growth, Pro, Enterprise. Compare plans

An SLA target is a clock. It starts when something happens on the ticket, can pause, and stops when the target is met.

The five metrics

  • First reply: Starts when the ticket is created. Stops at the first public reply from an agent.
  • Next reply: Starts when the customer replies. Stops at the next public agent reply. It runs again after every customer reply, so a ticket can have several cycles (#1, #2 and so on).
  • Periodic update: Measures the time between public agent replies while the ticket is unsolved.
  • Requester wait: Measures how long the ticket is unsolved, but pauses while it is Pending, because then you are waiting for the customer.
  • Resolution (agent work time): Measures how long the ticket is unsolved, but pauses while it is Pending or On-hold.

When clocks pause

  • Pending pauses Requester wait and Resolution.
  • On-hold pauses Resolution.
  • With business hours, every clock pauses outside the schedule’s opening hours and on holidays.

Statuses of a target

StatusMeans
RunningThe clock is on.
PausedThe clock stopped for now.
AchievedThe target was met in time.
BreachedThe time ran out. The clock keeps counting so you see by how much.
CancelledThe target no longer applies, for example the policy changed.

When the policy changes

ChaosDesk checks the policies again when the ticket is updated. If its priority or group changes, it can get another policy or other targets. Achieved and breached results stay in the ticket’s SLA history.

Was this article helpful?