How to alert your team to tickets nearing an SLA breach

Return to top
Have more questions? Submit a request

10 Comments

  • Joe Maloney

    I ran into two issues when trying to set up this automation (with brand, but not an about field):

    • Automation must test for at least one of the following ticket properties in the ALL conditions section: Status, Type, Group, Assignee, Requester.
    • Automation must not run multiple times per ticket. It must have a time-based condition that is only true once (Hours since created is 24) or an action that nullified a condition ("Priority Is High" and an action setting it to "Priority Is Urgent").

    Possibly related to our particular setup, but wanted to flag in case others were getting the same error. Any advice? I can add in group easily, and was thinking about adding in a tag to hopefully correct the second error. 

    Thanks!

    Update: added in group and tag ("upcoming_sla_breach") and was able to submit the automation - but a ticket could breach an SLA multiple times depending on the metric/setup. Does anyone have advice on how to handle notifications for that?

    0
  • Elissa
    Zendesk Community Team

    Hi Joe Maloney

     

    Thank you for pointing this out! The example conditions in this article are definitely more of a skeleton and will definitely need to be fleshed out with your teams particular needs before it is ready to go.

    I'm glad you were able to use groups and tags to get those errors sorted out. Here are two resources that may be helpful to others encountering the same errors as they get their own automations up and running: 


    In regards to the conflict between the requirement of a nullifying condition and the reality that SLAs can breach on the same ticket multiple times, this is an excellent point! While no easy solution within the automation itself comes to mind right away, you definitely could use this work-around: 1) set up a nullifying condition using a tag (as you have already) and 2) create a trigger that removes that tag any time it is added.

    Other community members may have better suggestions as well!

    I hope that helps. Let us know if you have any further trouble!

    0
  • Joe Maloney

    The trigger to remove the tag is a great idea! I'll try that. Thanks Elissa!

    Update: trigger working well! Thanks again!

    0
  • Valerie Trenholm

    Hi Madison,

    I was certain that the automation only ran every hour so by the time we get an email notification the ticket may have already breached.

    This is why we've been using 2 hours to give us some wiggle room. 

    Can you shed some light on this?

    0
  • Ben Van Iten
    Zendesk Community Team

    Hi Valerie!

    The amount of hours you use in this case is up to you. I can certainly understand using two hours to give you more of a buffer. Like many workflows/features in Zendesk, one size definitely does not fit all.

    Let us know if I have not addressed the question properly and we'll be glad to help further!

    0
  • Ben Van Iten
    Zendesk Community Team

    Hi Joe Maloney and Valerie Trenholm,

    Thank you both for your feedback and suggestions. With that in mind, we have made the following updates to the article:

    • Added the additional conditions/actions in relation to the additional automation condition/nullifying condition that is needed for the Automation to save
    • Updated the hours to less than 2 as this use case might be more appealing to a wider customer base given how automations function
    • Updated the screenshot to reflect all of this

    Please let us know if you have any further thoughts or questions on this.

    0
  • Emelie Stjernquist

    Hello,

    I've a problem related to that we have one SLA metric (1st Reply time) that is more important than the other ones and the only one we would like to have an Alarm for via Automation. Unfortunately, SLA metric is not possible to use in Automations nor for Triggers. Does anyone know a workaround for this?

    Thanks!

    0
  • Brandon Tidd
    Community Moderator

    Hi Emelie Stjernquist,

     

    There are probably a couple of ways to tackle this - but the simplest workaround that comes to mind is using tags.  This would be a two step process.  First, you would trigger a tag based on the first public reply:

     

    Then, you would include a condition in your automation that looks for that tag as a way to negate it: 

    In this case, the automation would fire if it's one our until the next SLA breach AND the tag is missing.  Once the tag is added (on the agent's first reply), this automation would be negated and not run.  Hope this helps!

    Brandon

    1
  • Emelie Stjernquist

    Hi Brando,

    Thank you, that's smart. I will definitly try that.

     

    Thanks!

    1
  • Jiri Kanicky

    The fact that automation runs only one time every hour is a big flaw of Zendesk.

    Another flaw is that you have to create/removes tags to actually be able to create Automation (eg. for notifications). Adding or removing tags updates the ticket, which basically skews the reporting.

    I am really surprised that Zendesk team is not doing anything to removes these flaws and they keep advising people to create workarounds with Tags.

    Why don't they add a function to run it just one time, if they want to run it just one time?

    0

Please sign in to leave a comment.

Powered by Zendesk