Recent searches
No recent searches
![Adam's Avatar](https://support.zendesk.com/system/photos/4789179064090/avatar-1658443374.jpg)
Adam
Joined Apr 15, 2021
·
Last activity Nov 09, 2023
Following
0
Followers
0
Total activity
53
Votes
20
Subscription
1
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Adam
Adam commented,
My apologize Barry Neary.
I read Laurens comment and your response as Zendesk being able to notify agents via a DM to a Slack channel that a ticket was assigned to them. Slack is a heavily used tool at our company so we are always looking for more ways that Zendesk can integrate with Slack.
View comment · Posted Nov 09, 2023 · Adam
0
Followers
0
Votes
0
Comments
Adam commented,
+1 We would also love to see a Slack DM on ticket assignment to agents.
View comment · Posted Nov 08, 2023 · Adam
0
Followers
0
Votes
0
Comments
Adam commented,
Hi Barry Neary,
Thank you for responding to my feedback. I appreciate you taking the time to discuss it with me.
-
Group them together and add them to a specific capacity rule? Or is there too much variation in what agents feel is their maximum capacity (requiring lots of individual capacity rules)?
I understand your point. However, I am worried that adding more groups to manage capacity may not be scalable in the long run. The current process of assigning agents to groups and being more specific with them seems to involve too much extra work. It would be better if managers could individually assess each agent's capacity and decide whether it should be increased or decreased. I will definitely consider discussing the possibility of adding more groups with our managers.
-
We could introduce a delay, but the fear is that will negatively effect metrics like time to first response.
I understand your concern regarding this matter. However, there are pros and cons to both approaches. If we assign too many urgent tickets to an agent simultaneously, they may struggle to provide the same quality of support for each one. On the other hand, if we incorporate a buffer time, it allows the agent to decompress and focus on one ticket at a time. Our Workato workflow was designed to automatically assign tickets to agents with this buffer time in mind. We have received positive feedback that this approach reduces stress and results in more thoughtful and deliberate responses. Additionally, we have observed situations where one agent receives several tickets at the start of their shift, while another agent receives none. Implementing a pause timer would help distribute the workload more evenly among the team and ensure a smoother flow of tickets.
-
Do you think that reassigning after the agent has been in an away or offline status for X mins (configurable) would address this fear?
I understand your concerns, but we have confidence in our agents to handle the tickets effectively. Additionally, our managers keep a close eye on the tickets and investigate any patterns or indications of an agent trying to pass on their responsibilities. We initially set our timer in Workato to 10 minutes but have now extended it to run every 30 minutes.
If I were to specify the conditions for the Zendesk built version, they would be something like:
IF
- Time since assigned = 30mins
- Last agent update = 30mins
- Agent Status = AWAY or OFFLINE
ACTION
- Move the ticket back to the group for re-assignment.
- There is one more thing that I may not have mentioned earlier. We have created four automations to transfer a new ticket to the next level of our support hierarchy if the first level is already at maximum capacity. Although this process is functioning, it's not efficient because we're limited to the Zendesk automation running hourly. In case all four of our groups are full, it would take roughly four hours for the ticket to be transferred to each group. Here are the conditions we have set for this workflow:
- Ticket SLA has breached
- Assignee is null
- Time since update is 1 hour
Action
- move ticket to next group
Then so on up the chain of groups.
Sometimes, when a ticket moves from one group to another, there can be delays if an agent becomes available in the previous group. This is because the ticket has to go through the other groups before it can loop back to the first one. Therefore, I suggest that Omnichannel routing should search for available agents in other groups when one group reaches capacity.
View comment · Posted Aug 02, 2023 · Adam
0
Followers
0
Votes
0
Comments
Adam commented,
For additional feedback, ask.
4. Our managers would like to generate a report using Livedata for Omnichannel Routing in Explore. The report should display the number of tickets assigned to an agent via Omnichannel Routing on an hourly basis, regardless of whether the agent retains the ticket or not.
View comment · Posted Jul 31, 2023 · Adam
0
Followers
0
Votes
0
Comments
Adam created a post,
Hello,
Last week we launched Omnichannel Routing, which was successful overall. However, we did encounter one issue where tickets were being assigned to agents in different time zones who were not online. To address this, we quickly developed a script to set all agents to offline. It would have been helpful if this feature was built into the Omnichannel Routing settings. We struggled for about an hour with Zendesk Support before I found documentation from Zendesk suggesting that we either ask all agents to set themselves to offline (which is not feasible for a global company), or use an API call to set all agent statuses to offline.
Aside from this issue, we have some feedback that we would like to share to help improve the functionality of Omnichannel Routing.
-
Individual Capacity Rules for Agents
We have received feedback from agents requesting more personalized capacity rules for ticket management. At times, the default group's capacity rules are too high for them and they would prefer to accept fewer tickets. While we could create a new group for these agents, this would result in an excessive number of groups, rather than managing capacity rules within the capacity rules UI.
-
Buffer Time Before Assigning Tickets to Agents
Our agents are currently receiving a high volume of tickets at once, sometimes up to 5-7 tickets when they set themselves to online. This can be overwhelming for the agent, and they have suggested that there be a buffer in place for ticket distribution to ensure a more equal distribution when another agent comes online. One solution could be to lower the agent's capacity to handle fewer tickets. Another suggestion is to implement a timer that prevents the assignment of new tickets for 5-10 minutes after an agent has been assigned a ticket. This will allow the agent to focus on the current ticket before receiving another one.
-
Waterfall Email Tickets
We have created a Workato recipe that regularly checks all open tickets every 10 minutes. If an agent assigned to a ticket is marked as "Away" or "Offline" within the last 10 minutes, the ticket is reassigned to the main group assigned by Omnichannel Routing. This is particularly important for tickets received through email, as assigning a ticket to an agent who is away from their computer or at the end of their workday can cause the ticket to go unattended.
Posted Jul 25, 2023 · Adam
0
Followers
1
Vote
3
Comments
Adam commented,
Hi Barry Neary
I have a question about reassignment and idle time.
If an email ticket gets assigned to an agent set to away and the idle time kicks in and sets them to offline, does that ticket automatically get pushed back to the main group to be reassigned to another agent?
View comment · Posted May 11, 2023 · Adam
0
Followers
0
Votes
0
Comments
Adam commented,
Hi Sabra
Looking through the API documentation, it's very unclear how to make an API call to set all agents to Offline. We always use Postman in testing, and I'm pretty confused about how to achieve this.
Can you provide an example of the API call needed to set all agent's statuses to Offline?
View comment · Posted May 11, 2023 · Adam
0
Followers
0
Votes
0
Comments
Adam commented,
I was able to get this working via this code and added it to the script.js file.
if (HelpCenter.user.role === "end_user" || HelpCenter.user.role === "anonymous") {
var communityRedirectUrl = 'addredirectDomain';
var supportRedirectUrl = 'addredirectDomain';
var currentUrl = window.location.href;
if (currentUrl.includes("https://[yourZendeskDomain].com/hc/en-us/community")) {
window.location.href = communityRedirectUrl;
} else if (currentUrl === 'https://yourZendeskDomain].com/hc/contributions/posts?locale=en-us' ||
currentUrl === 'https://yourZendeskDomain].com/hc/en-us/subscriptions') {
window.location.href = communityRedirectUrl;
} else if (currentUrl === 'https://yourZendeskDomain].com/hc/en-us/articles/preview' ||
currentUrl === 'https://yourZendeskDomain].com/hc/en-us/categories/preview' ||
currentUrl === 'https://yourZendeskDomain].com/hc/en-us/sections/preview') {
window.location.href = supportRedirectUrl;
}
}
View comment · Posted Feb 03, 2023 · Adam
0
Followers
1
Vote
0
Comments
Adam commented,
-
What was your first impression?
I'm still a little frustrated, the whole experience feels very disconnected. Being able to work in the one tab for years was great. Now a lot of aspects remain in "Support" or in "Admin," and I'm constantly needing to go back and forth. Today I was looking at the new team member page. It looks good, but to make changes, you send me out to a new tab in support. When I need to work on multiple things, this gets a little out of control.
-
What did you try to find using Search?
Everything, I had to relearn the entire setup as you'd changed it all. I still get lost.
-
What did you think of the Recents feature?
As mentioned in my first answer, each feature feels disconnected from the process I'm trying to follow. Working where I am and making changes there is much easier than being taken out of the environment to make a change, then going back to the other tab to confirm it or update something else.
-
How well did the settings work?
Settings work fine. Zendesk has always had issues in my experience updating the current status when I make a change. We have it hardwired into our documentation always to click the refresh page once you make a change since it takes so long to propagate across your servers.
-
Where did you need help?
Re-learning everything took time. Disconnected workflows are my most significant pain point and add unnecessary time to my day.
View comment · Edited Sep 29, 2022 · Adam
0
Followers
2
Votes
0
Comments
Adam commented,
We had the same issue, but it was Zendesk that turned off our Salesforce sync due to their bug and only notified our Zendesk owner and not the admins. Frustrating that no notification was sent out, as the downstream effects of this have not been good.
View comment · Posted Sep 20, 2022 · Adam
0
Followers
0
Votes
0
Comments