Recent searches


No recent searches

Customizing your SLAs with advanced settings



image avatar

Colleen Hall

Zendesk Documentation Team

Edited Nov 13, 2024


2

21

21 comments

When we will have the option to define when a SLA is not fulfilled?

 

We want to have a stable reporting and this is only possible when the SLA breach is visible without any public or private comment.

Otherwise it will jump, depending on when the SLA was updated.

2


image avatar

Scott Allison

Zendesk Product Manager

Johannes Garske Thanks for the feedback! Can you tell me more about this need, specifically?

0


Hey,

at the moment the SLA is only achieved/ breached when an agent reply (i don't include the news from the post).

 

When we report on these numbers the calculation in Explore is constantly changing because some tickets are getting older (e.g. potential bugs). Thic ticket counts into the week where the SLA breaches or achieve (SLA update), independent from the date we solve it.

 

We need one number and this is only possible when the SLA breach shows in the week it breaches, independent from an reply or an internal note.

The reporting is totally inaccurate without this. It just jumps randomly between different achievement-rates.

0


image avatar

Brett Bowser

Zendesk Community Manager

Hey Johannes Garske , it looks like we have a ticket open with you regarding this issue you're running into with your reporting. We will continue working with you in that ticket to figure out what's causing issues with reporting on your SLA's.

 

Appreciate you bringing this to our attention!

1


Hello! We have the next reply time start setting, "When any end user replies to a ticket and that reply is added as an internal note", enabled. 

However, we have noticed that third-party internal note responses where the response is flagged because the end-user was not “part of this conversation” are not setting a next reply time. 

Is this an expected behavior? Is there anything we can do to change this?- We want all external end-user internal notes to set a target regardless of whether they were originally part of the conversation

 

1


Wondering if anyone got answers to their questions?

0


I have this same question Cameron Eng 

0


image avatar

Colleen Hall

Zendesk Documentation Team

On October 31, 2024, Zendesk removed advanced SLA settings for the Next reply time and Periodic update metrics. Additionally, the options available for the First reply time metric advanced setting have changed. Please follow the announcement for updates.

-1


Hi Scott Allison , we have some internal SLAs that cannot be achieved by group SLA, for example Jira updates,that require us to update the customer (so the customer will receive a message, but it will not be due to them sending one, but due to our communication). We would love to see an option of customizing SLA based on those updates, regardless of end-user activity, since we want to ensure those updates are relayed to the customer in a timely fashion. Will this be available sometime?

0


Colleen Hall Where is the communication that functionality has been removed and the reasoning? When can we expect to hear an update? I have a need to track SLA first reply time when a ticket is created with an internal note (read: voicemail). A customer leaving a voicemail, regardless of whether we want that set to internal or public for our ticketing system, should technically be considered a public message from a customer and I need to be able to track our first reply SLA metric against it. 

0


Hi,

 

I have an SLA in place for first reply time via Live Chat. However, I’ve noticed that if a chat is initially missed by Agent A, the SLA is breached, and when the chat is reassigned to Agent B, the breach is recorded against Agent B.

 

Is there a workaround to ensure that the SLA breach is not attributed to Agent B when it was missed by Agent A?

 

Best,

Rose

0


image avatar

Sydney Neubauer

Zendesk Luminary

Colleen Hall we have been excited to use Advanced settings for SLAs. It was unclear as to what settings were being removed but bu the looks of it, SLAs for internal notes has been removed:

Does this also apply for Voicemails?

 

When will this setting be returning? We have had a request for this since February and we were about to implement until it was removed. Is there a timeline?

0


image avatar

Salvador Vazquez

Zendesk Product Manager

Hello all, 

Thank you for continuing to check in on these advanced settings. I understand this is not the ideal case to have some of the settings removed but we wanted to make sure you all have reliable SLA activations and fulfillments. Customers who were already using the new advanced SLA settings were notified by email. Zendesk is working toward a long-term fix before reintroducing these settings; however, the date when they will be available again is still being determined. 


In the meantime you can refer to this document for which settings are still enabled and working. And follow this announcement to keep up with the changes to the advanced settings. 

 

Thank you all for your patience as we work through this and get your functionality back. 

 

1


image avatar

Sydney Neubauer

Zendesk Luminary

Salvador Vazquez 

Thanks for the update. However we are not seeing the settings that is described in that article. Here is what we see in regards to Next reply:

Compared to what should be there for Next reply:

There is no option for advanced settings for Next reply. And we can't comment on the article you mentioned. Can you confirm if the article is up to date or if there is an issue?

0


image avatar

Colleen Hall

Zendesk Documentation Team

Hi Sydney Neubauer, this article, Customizing your SLAs with advanced settings, is up to date.  Advanced settings for Next reply time and Periodic update were temporarily removed on October 31, 2024.

1


Colleen Hall do you have any clearer definition of ‘temporarily’ at this time?

0


image avatar

Colleen Hall

Zendesk Documentation Team

Hi Nicky Clark, not at this time.  As soon as there is more to share, the announcement will be updated. Please follow the announcement so that you're notified of any new information. 

1


Follow up on this inquiry 

Hello! We have the next reply time start setting, "When any end user replies to a ticket and that reply is added as an internal note", enabled. 

However, we have noticed that third-party internal note responses where the response is flagged because the end-user was not “part of this conversation” are not setting a next reply time. 

Is this an expected behavior? Is there anything we can do to change this?- We want all external end-user internal notes to set a target regardless of whether they were originally part of the conversation

 

0


Are there any plans to enable the configuration of SLAs based on a field other than "Priority"? Our SLA agreements are centered around "Severity," which presents several challenges:

  1. I am unable to rename the "Priority" field to "Severity," resulting in discrepancies between our reporting and contractual language.
  2. It is confusing for my agents to instruct them to "Set the Priority field to match the Issue Severity."

Priority and Severity represent different concepts. While they are often aligned, there are instances where they differ, leading to reporting inaccuracies across systems. Engineering uses "Priority" to determine the resolution timeline, whereas "Severity" reflects the impact of the issue on our systems.

 

It would be beneficial if we could either rename the "Priority" field or configure our SLAs based on a "Severity" field.

 

Currently, I have created a "Severity" field and instructed our team to set both the Severity and Priority to the same values. This approach ensures our reporting terminology aligns with our contractual language and will also provides accurate SLA times based on the Priority field.

0


Is there any news when advanced functionality will be put back in?

 

In particular we would need the ability to track “Periodic Updates” based on internal notes.. this way Private or Internal tickets are still tracked and would require regular updates to be kept up to date.

 

Thank you

 

Tom

1


+1 for Tom's question above…

 

We've struggled to maintain quality and efficiencies without the ability to fully rely on SLAs for all tickets - especially those created with First Reply Time generated from APIs.

 

It's been months without these features, when will they be returned? Is there a plan, a timeline, or anything?

0


Please sign in to leave a comment.