A service level agreement (SLA) is a contract between you and your customers that specifies performance measures for support by ticket priority. You can use SLA information, visible in views and tickets, to prioritize the tickets you address.
For more information about setting up SLA policies, see Defining and using SLA policies.
Understanding SLA target statuses
- Active: An active SLA target is one whose metric has not yet been completed. For example, if the metric is "First Reply Time" and there has been no first public reply on a ticket, the "First Reply Time" target is still active on that ticket.
- Paused: A paused SLA target is one whose metric has not yet been completed, but we’ve temporarily paused the clock. A target can get into this state if its metric definition excludes certain statuses, like Requester Wait Time. When a ticket is put into pending, the Requester Wait Time target will be paused.
- Closed: A closed SLA target is one whose metric has been completed. For example, a ticket that’s already received a public reply will have a closed target for the “First Reply Time” metric.
- Active (breached), Paused (breached), and Closed (breached): There are also breached variants of each of these three states. Any given SLA target can be both active and breached, or paused and breached, or closed and breached. This just means that in addition to the definition above, the metric has surpassed the target time assigned to that ticket.
Seeing SLA statuses in views
You can view SLA target status in the Next SLA Breach view column.
If a ticket does not have an SLA policy applied or if all of the targets on that ticket are closed, the Next SLA breach value will be blank for that ticket.
If at least one target on the ticket is active, the calendar time remaining before that target is breached appears. Once the target has been breached, a negative time value, like -15m or 4h, appears in red.
If the next target is paused, a pause icon will appear in the Next SLA breach column. For targets that haven't been breached yet, a green pause icon appears. For targets that have already been breached, the pause icon appears in red.
If your view contains the Next SLA breach column, SLA information will appear in the ticket preview when you hover over the ticket in the view. This information won't appear if your view doesn't contain the Next SLA breach column.
If an SLA is applied to a ticket well after it is created, it uses the ticket's metrics to calculate its targets, rather than starting from the time it is applied. For example: A ticket is submitted at 9 AM. At 12 PM, an SLA is created and applied to that ticket, with a First Reply Time requirement set for 1h. That SLA will immediately appear as breached when the SLA policy is applied at 12 PM because SLAs can't put events in the past. However, the breach time itself starts counting from when the SLA policy is applied. In this example, the breach time starts from 12 PM and continues until the ticket is replied to.
Seeing SLA statuses in tickets
Once you start using SLAs, SLA information will automatically start appearing on any ticket where an SLA policy has been applied. The next action that needs to be taken by the agent will appear in the top-right corner of each ticket along with the amount of calendar time that is left before the target will breach. This should appear nearly identical to the formatting in views, with the exception of indicating the next action to be taken.
To view more information about the SLA target
Hover over the SLA badge in the top-right corner to see other active SLA targets for the ticket and the exact date and time when the target will be breached. Once the SLA policy is fulfilled, the badge disappears.
The SLA badge will always show the hours till the targets are due in calendar hours and days, but the target due date will be based on the hours as defined in your SLA policies and business hours. This means that SLA targets set with business hours can carry over to the following business day depending on the target set and what time of day the ticket was created.
For example, a ticket may have a target of eight business hours, but because it's a Friday afternoon, the target rolls over to Monday morning and the badge will show three days. This is because SLA badges are designed to help agents prioritize their workflows in real time. It's important to get all the badges on the same scale in a way that agents can easily understand.
Viewing which SLA policies have been applied to a ticket
You can see which SLA policy and corresponding targets have been applied to a given ticket by checking the ticket's events (see Viewing all events of a ticket).
Each time a policy or target is applied, removed, or changed, an event will appear. However, no event appears when an SLA is breached or fulfilled.