Recent searches
No recent searches
Apply First Reply Time SLA to Tickets Created from Talk Voicemails
Posted Dec 30, 2020
Right now, tickets created from Talk voicemails do not have the First Reply Time SLA target applied because they lack an initial public comment. However, a voicemail left by the customer is essentially a "public comment" in that it is the initial ticket request directly from the customer (just via a different channel).
Our company's new customer service policy states that we will provide a human response within 2 business hours to tickets opened by customers, regardless of the channel (email, widget, or voicemail). We really need Zendesk's SLA logic to apply the First Reply Time target to tickets created by voicemails. Otherwise, they will be missed, and we will be on the hook for missed SLAs with our customers.
20
22 comments
Steve Francis
Having run into this same limitation of Zendesk - I've found a kludgy workaround:
- create a new SLA policy that targets channel voicemail, and applies only if a specific tag (hasInitialResponse) is not present. This SLA measures Requester Wait Time (which does apply to tickets created from Talk voicemails.)
- create a trigger that adds the hasInitialResponse tag to any ticket that has a public comment.
Effectively this means that the voicemail SLA will track (and be in violation) if there is no comment before the SLA period. Once someone comments (which is effectively a First Reply), the voicemail SLA will not apply, and regular SLAs will, but they will work effectively now.
I'm sure this will break reporting and other things, and its a bit of a fragile hack, so definitely still need Zendesk to fix this limitation.
6
Dave Dyson
Thanks for posting this workaround, Steve!
0
T.J. (ZenBros)
@... would love an upvote on this feature request, as its related.
[TALK] Feature Request(s): Custom attributes for logical conditions/triggers, automations, SLAs and KPI metrics are unavailable and far overdue
3
Steve Francis
Done!
0
Keystone Precision Solutions
This is amazing, thank you Steve! Our company is setting SLAs around missed VMs and this work around works just as you described. This is definitely a blind spot Zendesk should fix so we can include it in our reporting on Explore.
2
Lauren G
Hi Steve,
This is something I'm trying to do for missed chats & missed calls. Do you have any screenshots of the trigger/SLA set up so I can see how it is set up? I have set up both a trigger and SLA and for some reason it doesn't seem to be working. Thank you!
0
Steve Francis
Sure:
And the trigger:
0
Steve Francis
We have different (but similar) SLA policy for non-premium support voicemail.
0
Josh Rogers
We have followed these directions to a T and still cannot seem to get this SLA to function as described. Anyone else have difficulties with this?
0
Dave Dyson
0
Justin Worley
Josh Rogers, I've found that it won't work if you have the voicemails set to an internal note. I don't know if that is your case, but suspect it could be.
0
Josh Rogers
@... thanks for the article recommendation. Took a spin through and none of the use cases seem to be applicable. What's really odd is that the SLA Policy shows as applying to the ticket
But no SLA presents in the queue for measurement
Justin Worley can you point me in the direction of an article on your thoughts? I do not think these are set as a private comment but would like to confirm and potentially troubleshoot.
0
Justin Worley
Josh Rogers From your screenshot, it does look you are using the public setting; so, never mind my previous comment. As an FYI, it is possible to have them be internal (yellow background) instead.
0
Kaitlyn
Hey there! Unfortunately, the work around that Steve provided is not working for me either - Similar the issues Josh mentioned above.
This is an essential function of our service that goes often missed by our team members due to not having an SLA time so it would be amazing to have SLA apply here.
0
Scott Allison
I'm the Product Manager for our SLA feature set. Thank you everyone for your feedback, this is really appreciated. This year, we do have a plan to introduce the ability to configure exactly how your SLA targets get activated or fulfilled. One of the use cases we want to meet is tickets created by an agent on behalf of an end user. This is very similar to the voicemail use case, so it's possible we may solve this too. We'll do some investigation here and I will update this thread once we know the outcome of that. Thanks again and please do continue to upvote this or comment with your feedback.
1
Aaron Doane
Thank you for your attention to this. We are currently implementing Talk and trying to navigate this exact hurdle.
0
Zach Gilbert
We need this too. Mainly voicemails. If a VM is left and agents are working on tickets based on SLAs, those VM ticket sit waiting as they get a solve SLA vs first reply. @...
0
Zach Gilbert
Scott Allison any update on this? @... (for some reason there are two of you in Zen)
0
Scott Allison
Zach Gilbert Thanks for the bump on this. We're working on this and a number of other enhancements which will give you the ability to customize the logic for how first reply time is activated and/or fulfilled. This will solve a number of needs including this one for voicemails. You can expect to see this in Q3.
0
Scott Allison
I wanted to provide you all with an update here, and point you to a release that we started rolling out today that provides a solution for First Reply Time on voicemail tickets.
We're introducing advanced settings to three of the SLA metric types, first reply time, next reply time and periodic update. These new settings are optional, and give you the ability to change the logic for when an SLA metric is activated or fulfilled, on an individual policy basis.
Once the rollout is complete, go to the Admin Center page for SLAs, select your policy, edit First Reply Time and then click on Advanced Settings. Then check the box next to “When any ticket is created for an end user with an internal note”. Any new voicemail tickets will then have FRT applied.
This is what it looks like on a ticket:
Read more in the announcement here:
https://support.zendesk.com/hc/en-us/articles/7411959450778-Announcing-advanced-SLA-configuration-settings
0
Revant Admin
It looks like the ability to add SLA's for Voicemails based on that internal note was just deleted by Zendesk. It's imperative that our team has this availability on all of our VM tickets. Is there a work around knowing that you took out the following things from advanced settings?
- First reply start settings:When any ticket is created for an end user with an internal note
- First reply end settings:When an agent adds an internal note to a ticket
- Next reply start settings: When any end user replies to a ticket and that reply is added as an internal note
- Next reply end settings:When an agent that is not the requester adds an internal note following activation
- Periodic update start settings: When an agent adds an internal note reply
0
Lara McCaleb
Scott Allison The instructions you've notated above “edit First Reply Time and then click on Advanced Settings. Then check the box next to “When any ticket is created for an end user with an internal note”. Any new voicemail tickets will then have FRT applied. ” is not available. Can you please advise ZenDesk's new recommendation?
0