An easier way to see upcoming SLA breaches

Return to top

14 Comments

  • Rafael Santos

    Cool update!
    Scott Allison Will we have the option to customise the amber badge's time threshold, instead of 15 minutes? If so, would it be customisable per SLA Policy?

    11
  • Scott Allison
    Zendesk Product Manager

    Rafael Santos Not in this initial release but configuration is something we're thinking about as an enhancement. Can you explain more about how you'd use this?

    1
  • Rudolph Beaton

    Looks great!

    And Scott Allison, we'd also love to customize the thresholds for each color. The main reason being is that we have many different departments with different tolerances on SLA breaches. 

    Stoked to see Zendesk improving SLAs.

    2
  • Steve Lacoss

    We have 10 minute SLA timers on our SMS messages.  This upgrade is not going to help with those.

    1
  • Rafael Santos

    Scott Allison, We'd use it to define what would be in risk of breach, though that can vary per SLA Policy, as there are different SLA Targets' times for different teams and lines of business.

    Team A could have targets of 30-60 minutes, benefitting from a 15 minute amber threshold, while Team B could instead have targets of 12 hours, where a 1-2 hour amber threshold would make more sense for them.

    6
  • Pedro Rodrigues
    Community Moderator

    This is looking neat! Additionally, the same SLA policy could have different thresholds, depending on the metric. For example, the threshold for my FRT could be 15 minutes, but 5 minutes for NRT.

    Also, you know how graphic design tools allow us to resize elements in pixels or percentage? Another nice little feature could be something similar: the ability to set a threshold percentage per policy (perhaps respecting a minimum of 1 min), so that we wouldn't have to manually input thresholds per metric, per SLA policy.

    1
  • Andrea Lee Bishop

    Scott Allison My teams would also like to customize the SLA window. We provide engineering support: many questions asked need an hour to debug, test, and provide an informative reply. Fifteen minutes is arbitrary and too late to provide a meaningful update. We discourage our staff from acknowledging a ticket to prevent an SLA breach, because it games our stats and masks the need for hiring to provide adequate coverage.

    • If I could change 15 minutes to 1 hour across the board, that would be a great version 2.
    • If I could change 15 minutes to 1 hour for first replies and 2 hours for pausable updates, that could help with those gnarly cases when you step into the middle of an ongoing issue to finish it out and need to build context.
    • If I have SLA levels (gold, silver, bronze, whatever, etc.) many questions are similar, it wouldn't change the fact that it takes an hour to answer the questions. I don't think that would help my team.
    • If I had granularity at the internal team or queue level, I could give Tier 1 support less time to solve something than Tier 2 or whatever combination to influence the behavior I need from the team. 
    • Being able to affect every cell in the SLA matrix for every level I've defined sounds like a process/tracking/risk challenge. 

    I can appreciate how this might be difficult for your team to build based on your different customer use cases. Thank you for approaching future updates with this kind of curiosity. 

    1
  • Christopher Kenrick

    I was excited at the announcement at first...until I saw its not customisable 😔 its a good starter but we really need it customisable

    4
  • Heather Rommel
    Community Moderator
    The Product Manager Whisperer - 2021

    I agree with Christopher Kenrick

    As admins, we know our Zendesk usage best and a way to configure red/yellow/green brackets would be best! Every instance is so different.

    2
  • Anthony Stenhouse

    If you intend to go down the route of adding customised SLA ranges, can you also tag on the ability to notify when an SLA hits the amber metric please? We'd like to be able to notify Slack/Other tooling when an SLA is within 30mins of breaching, which isn't possible with the current tooling.

    0
  • Scott Allison
    Zendesk Product Manager

    Anthony Stenhouse Thank you for that feedback! I'm the Product Manager for SLAs and we're right now on a big investment into this feature set with a number of enhancements. Real time alerting for SLAs is on the medium long-term roadmap. In the meantime partners like Sweethawk can provide these alerts for a small additional cost.

    1
  • Matt Natali

    Scott Allison some feedback from our team:

    People are having a hard time reading the badges for SLA. Even those who are not color blind are disappointed by this. 

    The ability to customize badge colors is an enhancement we are interested in. Should we submit a formal enhancement request to include with the other requests, or is visibility here appropriate enough? Whichever works best for you and your tracking, we can accommodate.

    Thanks!

     

    0
  • Scott Allison
    Zendesk Product Manager

    Matt Natali Thanks for asking the question! Yes, please do open a new thread here. Thank you.

    0
  • Martin Cubitt

    Great to see progress Scott Allison and I would love to be able to measure not by time remaining but by % remaining too. I know it's greedy but 3 levels of % would be even better! And if they can be configured per metric that would be awesome!

    The idea of using a configurable % remaining would allow consistency based on the target time. For example, if my 1st response SLA target times vary greatly from 5 minutes to 24 hours, the 15 minute setting we have now isn't going to work well because it's too high for a 5 min SLA target and too low for anything more than maybe 5 hours.

    If instead I had a warning state at 20%, I would be notified with 1 minute remaining for the 5 minute response SLA and with 4.8 hours for the 24 hour SLA.

    Maybe for resolution times (between 2 hours to 5 day) I would 25%, so would be warned with 30 mins left and 1.25 days left. This gives me time to act relative to the target times.

    Ideally I would like at least three %s defined, eg 75% remaining, 50% remaining, 25% remaining and defined based on metric. 

    Then we need a way to proactively inform based on that %, (eg 75% to assignee, 50% assignee and Support manager, 25%, assignee, Support manager and Customer Account Manager). We don't have a team able to sit and monitor each ticket to see when one hits SLA, but we'd like to get notified based on the % remaining,

    I know it's a lot Scott, and the start made already is progress, but SLAs are such a key part of Support and vary so much between customers/users.

     

     

     

    Eg:

     

    0

Please sign in to leave a comment.

Powered by Zendesk