Hourly automations in Zendesk can sometimes miss SLA breaches if the timing isn't perfect. For example, if an SLA is less than 1 hour and the automation runs just after the ticket is created, the breach might occur before the next cycle, resulting in no alert being sent.
To mitigate this, set your automation to trigger when the 'hours until next SLA breach' is less than 2. This provides a buffer to account for the hourly interval, ensuring alerts are sent in a timely manner.
To automatically alert your team about tickets nearing an SLA breach, you need to create an automation in Zendesk. Start by setting up SLA policies for your tickets. Then, create a new automation with conditions such as 'Ticket: hours until next…
When dealing with both Business and Calendar Hours SLAs, choose the operator that matches the type of SLA you want to address in your automation. If your SLA is based on Calendar Hours, use the Calendar operator, and if it's based on Business…
If you have multiple SLAs, like 1st response and resolution SLAs, for the same priority, you can manage them by adding more conditions to your automation. Instead of using a single tag or priority, consider adding another tag to distinguish between…
Currently, Zendesk automations require whole numbers for hours, which means you can't directly set notifications in minutes. However, Zendesk is planning to introduce a feature that allows for more granular SLA alerting, potentially including…
To send SLA breach notifications to a Slack channel, you can set up a webhook in Zendesk. Replace the trigger action in your automation with a webhook that sends notifications to your desired Slack channel. This integration allows you to keep your…