Read a ticket's SLA
How to read the first response and resolution clocks, what At risk, Overdue, Met and Paused mean, and who gets the notification.
On this page
The SLA is the committed deadline for handling a ticket. Elion ITSM measures it with clocks that count only the business time of the corresponding calendar, and warns you before it is breached.
The two clocks
Each ticket can have up to two clocks, depending on the SLA policy that applies to it:
First response: from when the ticket is created until the first public reply from someone on the team. An internal note doesn't count.
Resolution: from when the ticket is created until it goes to Resolved.
The deadlines depend on the policy that matches the ticket (by priority, desk, type, service, category, department, account, catalog item or whether the requester is VIP). In a CSM desk, if the customer's account has an active contract with an SLA policy, the contract's policy is used (see Create a contract). If no policy matches, the ticket has no SLA and you don't see clocks.
Where to see it on the ticket page
In the side panel, the SLA section shows a block per clock: the name (First response or Resolution), its status text, a bar and, below, the policy name. The countdown updates by itself every 30 seconds.
What it says | What it means |
|---|---|
Due in 2 h 10 min | The clock is running and has that much time left. |
3 h business time left | The clock is running; time is measured in business hours. |
Paused · 3 h business time left | The ticket is on hold and the policy pauses for that reason. Time isn't running. |
Overdue by 40 min | The deadline has passed and the clock is still open. The text is red. |
Met | The clock stopped within the deadline. |
Met late | The clock stopped, but after it was breached. |
When the clock goes at risk, the text is amber. A clock goes at risk when it uses up its policy's warning percentage (75 % in the built-in policy).
The color bar in the list
In the ticket list, below each row, a thin bar shows the ticket's most urgent clock:
Violet: within the deadline.
Amber: at risk.
Red: breached.
Gray: paused or stopped.
Sort the list by SLA due date to see first what is due soonest (see Ticket list and views).
The At risk view
The list's At risk tab brings together the open tickets with a clock that has already passed its warning threshold or is already breached. Check it at the start of the day and before you leave.
What each status does to the clocks
Action or status | Effect |
|---|---|
First public reply from the team | Stops First response. |
On hold with a reason the policy pauses | Pauses Resolution. By default, Waiting for the requester and Waiting for a vendor pause it. |
Resume or a reply from the requester | Resolution starts running again from where it stopped. |
Resolved | Stops the clocks that are still open. |
Reopen | Resolution continues with the time it had already used. |
Closed or Cancelled | Stops whatever is left. |
Priority change | It may change the policy and, with it, the deadline. |
If your company changes a policy, the change applies to new tickets and to those whose priority changes, not to clocks that are already running.
Who gets the notification
When a clock goes at risk or is breached, Elion ITSM notifies:
The ticket's assignee or, if it has none, the group.
The leads, according to the escalation configured for the group.
When it is breached, also the recipients of the group's escalation steps, who can also reassign the ticket to another group.
The notifications arrive as SLA at risk and SLA breached through the channels each person has active (see Getting started). Escalation is configured in Settings → Resolver groups, Escalation button, and policies, the matrix and calendars in Settings → SLA and Settings → Calendars (see Settings).
If a ticket is about to be breached and depends on the requester, put it On hold with Waiting for the requester: the resolution clock is paused and it's clear the next step isn't yours.
Related
Reports: SLA compliance by desk and period