Zendesk often releases new features and enhancements with little fanfare. Our CX experts are constantly monitoring these updates to bring you the insights that matter. This week, we’re looking at a much-needed improvement to omnichannel routing.
Stop Routing to Ghosts: Our Take on Zendesk’s Automatic Agent Status Change
What We Think:
This is a fantastic, long-overdue feature that directly addresses a major operational headache for any team using live channels. The ability to automatically change a Zendesk Agent Status after consecutive missed assignments is a simple, common-sense solution that will tangibly reduce customer wait times and improve routing efficiency. We see this as a must-implement feature for any organisation using Zendesk’s omnichannel routing, moving it from a ‘nice-to-have’ to a core part of intelligent workforce management.
The Reality Check: What’s Actually Changing?
Let’s be honest, we’ve all seen it happen. An agent is showing as “Online” and available, but they’ve just stepped away to grab a coffee or are deep in a complex email. A new call or messaging conversation comes in, routes to them, and… silence. The customer waits, the timer runs out, and the conversation is re-queued to hopefully find someone who is *actually* there. It’s inefficient for the team and frustrating for the customer.
Until now, Zendesk’s omnichannel routing would only change an agent’s status based on idle timeouts or disconnections. This new feature finally addresses the “away from keyboard” problem head-on. Admins can now configure Zendesk to automatically change an agent’s status after they miss a specified number of consecutive assignments. An assignment is considered “missed” when the agent neither accepts nor rejects it within the given timeframe.
The best part? This is highly customisable. You can set different rules for your voice and messaging channels, choosing both the number of consecutive misses that trigger the change and the specific unified status they are moved into (e.g., “Away,” “Lunch,” or a custom status like “Forced Break”).
Our Expert Opinion: The Deep Dive on Operational Impact
On the surface, this seems like a minor tweak. But in our experience, the operational impact is significant. The real power here lies in the granular control it gives to administrators and team leads.
Firstly, the ability to set separate thresholds for voice and messaging is crucial. A missed phone call is often a more critical service failure with a higher chance of customer abandonment than a slightly delayed messaging response. We would advise clients to set a much lower threshold for voice—perhaps even just one or two missed calls—before changing an agent’s status. For messaging, you might allow for a slightly higher threshold, depending on your SLA targets.
Secondly, think about the data and coaching implications. By creating a specific status, like “Auto-Away,” you can now accurately report on how often this happens and to which agents. This isn’t about punishing agents; it’s about identifying patterns. Is an agent frequently being put into “Auto-Away”? It could indicate a need for a wellness check-in, a discussion about breaks, or even a technical issue with their notifications. This transforms a simple routing problem into a valuable coaching and performance management tool. It’s a key step in maturing your omnichannel customer service strategy by ensuring agent availability is accurately reflected in the system.
Finally, this change directly improves your key CX metrics. By immediately taking an unavailable agent out of the queue, you shorten the time it takes for a customer to connect with an agent who is ready and waiting. This reduces average wait times, improves first response times on live channels, and ultimately limits customer frustration. It’s a cleaner, more intelligent way to manage your live interaction queues and the overall Zendesk Agent Status ecosystem.
How We’d Handle the Rollout: An Implementation Checklist
Rolling this out requires a bit more thought than just flipping a switch. To do it safely and effectively, we advise our clients to follow a structured approach. Here is what we recommend:
| Phase | Action Item | Our Recommendation |
|---|---|---|
| 1. Audit & Define | Analyse existing agent statuses and routing data. | Do you have a suitable status to move agents to, like “Unavailable”? If not, create a new custom status like “Auto-Away” so you can report on it specifically. Review your data to see how many re-routes currently occur to establish a baseline for your missed assignment threshold. |
| 2. Strategise & Configure | Set initial thresholds for voice and messaging channels. | Start conservatively. We suggest setting the threshold at 2 missed calls for voice and 3 missed messages for messaging. Choose the new custom status you created as the destination. |
| 3. Communicate & Train | Inform your agents and managers about the upcoming change. | Frame this as a positive change that helps them and the customer. Explain that it prevents them from being interrupted when they are genuinely busy and ensures customers get faster service. Train managers on how to interpret this new status in reports for coaching purposes. |
| 4. Pilot & Test | Roll out the feature to a small pilot group of agents. | Choose a trusted group of agents to test the new workflow. Gather their feedback. Does the threshold feel right? Are there any unexpected consequences? This allows you to fine-tune the settings before a full launch. |
| 5. Full Rollout & Optimise | Enable the feature for all relevant agent groups. | After a successful pilot, roll it out to everyone. Continue to monitor the data and agent feedback. Be prepared to adjust the missed assignment thresholds up or down based on real-world performance and business needs. A healthier Zendesk Agent Status landscape is an ongoing process. |
This new feature is a powerful addition for any team serious about optimising their live channel support. By automatically managing the Zendesk Agent Status of unavailable agents, you create a more efficient routing environment, empower managers with better data, and, most importantly, provide a faster and smoother experience for your customers. If you have questions about how to best implement this or other routing strategies, don’t hesitate to reach out to your alboz. Solution Consultant.
