In many cases, you may want to pause the SLA calculation when the ticket is in a certain status (often as you wait for a customer response) or, depending on the individual contract, on holidays or outside of working hours.
This is especially useful if you are supporting products in different time zones, and your contracts specify response times dependent on your customer's time zone. You can also pause the SLA on company holidays and/or on specific dates and days of the week.
Within Time to SLA, you can select statuses and field values that trigger the SLA countdown to pause.
Your options for Pause are:
Status is any of the selected status(es) – You can pick various statuses (To Do, In Progress, Done…). Once your SLA is in one of these statuses, it will stop counting and will continue to count only when it leaves this status.
The field value satisfies a condition – To pause the SLA on a certain field value, simply set the field you want for the statuses where it should be paused. You have numerous field options.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Important: Keep in mind that the SLA countdown does not pause if the SLA Goal is a negotiation date. |
You can see what a Paused SLA looks like on the SLA Panel below.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Tip: If you want to see the pause details on your SLA Configurations screen, simply click the columns drop-down menu on the top left-hand side and tick Pause on. |
🔁 Recap
We just learned how you can pause an SLA, which concludes the Creating SLA Conditions chapter. Let’s do a quick recap of some of the most important points:
You can add more than one condition. There is an “OR” function (not “AND”) between conditions, which means when any of the conditions are met, the SLA will start.
When there are multiple pause intervals, all of them will be applied to the SLA. Let’s take “assignee is EMPTY” and “team is EMPTY”, for example. Here, the SLA will be paused when the assignee is EMPTY, the team is EMPTY, or both of them are EMPTY.
For the resetting of finished SLAs, there are 3 use cases to keep in mind:
A finished SLA is a closed contract and a reset cannot change that⭐ A finished contract might be reactivated from zero with a reset
A finished contract might be completely invalidated with a reset. Even in FIRST cycle SLAs, the SLA can start from zero with a new START event.
With all that in mind, we will learn next how you can create SLA goals that meet your business goals.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Creating SLA Goals |