Recent searches
No recent searches

Rachel W.
Joined May 16, 2021
·
Last activity Aug 15, 2022
Following
0
Followers
0
Total activity
9
Votes
5
Subscriptions
2
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Rachel W.
Rachel W. commented,
@... thanks for the response!
It looks like you accidentally linked to the same thread twice in your response; can you share the link to the thread that covers the partial fix for CC'd users who reply?
As for the SLA target stopping any time an agent takes an action, I agree that the request in the thread you linked is similar to what I'm asking. The scenario described in that thread is more specific than what I was thinking – as I want a way for any update by the agent to stop the SLA, kind of regardless of context – but generally it sounds like the same idea/need.
View comment · Posted Nov 16, 2021 · Rachel W.
0
Followers
0
Votes
0
Comments
Rachel W. created a post,
We've found that our goals with SLAs can't quite be achieved with the available targets, for the following two reasons:
1. We would like an SLA target that restarts whenever a ticket is opened for any reason (ie. response from requester, response from a non-requester/someone who's CC'd, automation/trigger opens ticket). Next Reply Time works well when the ticket opens due to the requester responding, but it doesn't treat a response from a non-requester in the same way, which means that we could miss responding to a message from a non-requester in a timely manner.
To get around this, we use both Next Reply Time and Agent Work Time, but it doesn't entirely fix the issue. If we set Agent Work Time to the same value as Next Reply Time, it handles the case where a non-requester replies, and ensures those get treated the same way, but then it ends up making some of our tickets look older than they really are since Agent Work Time is cumulative.
2. We also want an SLA target to stop any time the agent takes any action (ie. public response or internal note, or even setting the ticket back to pending/on hold manually or with a macro)
Currently we have found that the Periodic Update achieves # 1 and not # 2, since it requires a public response to reset it, and a combination of Next Reply Time and Agent Work Time achieves # 2, but doesn't achieve # 1 perfectly as explained above.
We would love to see some additional SLA targets added that could help achieve the above. Thanks!
Posted Aug 11, 2021 · Rachel W.
16
Followers
12
Votes
6
Comments