Recent searches
No recent searches

Shelbee Butler
Joined Mar 24, 2022
·
Last activity Mar 31, 2022
Following
0
Followers
0
Total activity
3
Votes
0
Subscription
1
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Shelbee Butler
Shelbee Butler commented,
Thank you Dainne, I appreciate you getting back to me about this. I will create that file and await your team's response.
View comment · Posted Mar 31, 2022 · Shelbee Butler
0
Followers
0
Votes
0
Comments
Shelbee Butler commented,
So, this has been happening to my team. However, the list given of reasons why this happens does not apply to us. Agent collision is not an issue since there are 3 people who update tickets, and none of them are ever on the same ticket at the same time. We do not use Play Mode. We do not use any APIs. We do not have any installed apps. We do not use calls through Zendesk. We do not use chat through Zendesk.
The only thing we do use is triggers and automations, but only the default ones upon setup: "Trigger Notify requester and CCs of comment update" is the only trigger we have. And the only automation we have is the default survey that sends out once the ticket is moved to a "Closed" status, so that should not be interrupting our tickets being saved.
Our agents are constantly getting this error when saving tickets, so we need to know how to rectify this error since it seems to be an issue not related to these causes.
View comment · Posted Mar 24, 2022 · Shelbee Butler
0
Followers
2
Votes
0
Comments