Zendesk has enhanced the Next Reply Time SLA metric to offer more flexibility. It can now be configured to start when any end user replies to a ticket, not just the original requester. This is particularly useful when multiple end-users are involved in a ticket.
Moreover, the Next Reply Time can also start when an agent or light agent is the requester and leaves any subsequent comment on the ticket. These changes help ensure that all relevant interactions are accounted for in your SLA metrics.
Zendesk has introduced advanced settings for SLAs, offering more customization options. These enhancements allow you to apply SLAs in various situations, such as agent-created tickets, tickets with internal notes, and tickets from light agents. You…
The First Reply Time SLA metric in Zendesk can now be customized to start under various conditions. You can configure it to begin when a ticket is created on behalf of an end-user, whether by an agent, API, or other means, including voicemail…
With the new advanced settings, the Periodic Update Time SLA metric can now be configured to start when an agent leaves an internal note on a ticket, not just a public reply. This change allows for more comprehensive tracking of ticket updates,…
The new SLA settings in Zendesk will not retroactively apply to existing tickets. Any changes you make to the advanced settings of your SLA policy metrics will only take effect when a ticket is updated after the changes are made. Your reporting…
If you're satisfied with your current SLA policies, no action is required, and nothing will change. However, if you want to take advantage of the new advanced settings, you'll need to update your SLA policies accordingly. For guidance on…