Can I be notified of an SLA breach?

Have more questions? Submit a request

10 Comments

  • Max McDaniel
    Comment actions Permalink

    Hello, just noting that, as our team works in much tighter time constraints, hourly automations unfortunately do not do the job here. Ideal would be for some version of a trigger to fire upon SLA Status = Breached. Alas. 

    7
  • Jessie Schutz
    Comment actions Permalink

    Hi Max!

    I can definitely understand why you'd need more granular SLA breach notification on your most critical tickets. Other folks have mentioned this need as well, in our Product Feedback topic.

    While I can't guarantee that someone from our Product Team will be able to weigh in on the request, I'd still encourage you to head over to the post and share your detailed use case. This information is helpful for our Product Managers to understand what kinds of functionality our customers need.

    In the meantime, if you haven't already looked into it, you can create a View that shows any tickets that are approaching a breach in a timeframe you determine. It's not a notification, but it can help to give more visibility to tickets that are on the verge of going over the SLA time.

    -1
  • Vijayaragavan S
    Comment actions Permalink

    Hello Jessie, 

    Do we have a SLA for the SLA notification that is less than 1 hour?

    thanks,

    Vijay 

    2
  • Jessie Schutz
    Comment actions Permalink

    Hi Vijay!

    Unfortunately not. In my comment right above, though, I mention that you can set up a View to show tickets that are closer to approaching a breach.

    0
  • Pedro Rodrigues
    Comment actions Permalink

    I need to fire an SMS 10 minutes after a specific type of ticket is solved. Since there is no way to have conditions in "minutes since solved", I'd like to trigger it with an SLA breach.

    Anyone faced a similar situation?

    2
  • Vijayaragavan S
    Comment actions Permalink

    Pedro,

    There's no direct way you can do this with Zendesk. But with the Apps. There are two apps that can do this AFAIK. 

    1. https://www.zendesk.com/apps/support/due-time/?source=app_directory
    2. https://www.zendesk.com/apps/support/myndbend-ticket-reminder/?source=app_directory

    The third way is, you can write a cron that fire the Tickets API /api/v2/tickets/<ticket_id>?include=slas. This give the following output along with other information of the ticket.

    "slas": {
    "policy_metrics": [
    {
    "breach_at": "2018-06-28T06:04:31Z",
    "stage": "achieved",
    "metric": "agent_work_time",
    "minutes": -32
    }
    ]
    },

     

    You can use breach_at variable or stage and minutes (if -2) and trigger your SMS service.

     

    Hope this helps.

     

     

    1
  • Jessie Schutz
    Comment actions Permalink

    Thanks for helping out, Vijayaragavan!

    0
  • Pedro Rodrigues
    Comment actions Permalink

    Many thanks, Vijayaragavan, I'll review those options.

    1
  • Andrew Yoward
    Comment actions Permalink

    I have implemented this automation, but I would rather just have one email per day that lists all the tickets that will breach in the next 24 hours.  Is that possible?

    0
  • Pedro Rodrigues
    Comment actions Permalink

    Hi Andrew Yoward, it's not exactly what you want, but you could consider the following workaround:

    Add a specific tag with an automation to the tickets. Then create a table in Insights so that you can schedule it once per day.

    The automation should include time-based conditions, and another one for the tag.

    For example:

    • Status less than Solved
    • Hours until next SLA breach greater than 22
    • Hours until next SLA breach less than 25
    • Tags do not contain any of the following: your_tag

    Please note, however, that automations run every hour. This means that every hour there will probably be a few additional tickets that will match those conditions.

    Now you can create your table in Insights, filtered for this tag, and schedule it.

    Alternatively, you might consider creating a View with similar conditions (except the tag). In this case, you can be more accurate with the hours (i.e. more than 23, less than 25). Then all you have to do is export the view on a daily basis.

    Perhaps other members of the community can share other and better workarounds. For the time being, hope this helps!

    0

Please sign in to leave a comment.

Powered by Zendesk