- Team and Growth don't support custom unified statuses.
- Professional supports up to five custom unified statuses.
- Enterprise supports up to 100 custom unified statuses.
Unified agent status is part of omnichannel routing and provides a way for agents to control availability for Support, Talk, and Messaging from a single menu. There are four default agent statuses: online, away, transfers only, and offline, as well as a customizable fallback status that's used when agents are idle. On Professional and Enterprise plans, admins can also define custom unified statuses to suit their workflows.
All unified statuses, including custom statuses, are automatically available to accounts that meet the requirements.
To add a custom agent status
- In Admin Center, click Objects and rules in the sidebar, then select Omnichannel routing > Agent statuses.
- On the Agent statuses page, click Create agent status.
- On the Create agent status page, configure the following:
- Name: Give the new status a short, unique name. The name can't exceed 100 characters. Dynamic content is supported if you want the status to be displayed in the agent's local language.
- Description: Optionally, give the new status a description that helps you identify it.
- Channel routing > Email: Define the agent's availability for incoming emails when this custom status is active.
- Channel routing > Talk: Define the agent’s availability for incoming Talk calls when this custom status is active.
- Channel routing > Messaging: Define the agent's availability for incoming Messaging conversations when this custom status is active.
The Status section shows a preview of how your agent’s icons will look depending on the selected status.
- When you are finished, click Create agent status.
Could we report times in creating status? For example I need to know which agent how mant time spent in these status?
Any updates to when this will be released to general ZD users?
Also interested in the ability to export report on time in the various status.
I can confirm that this is something our Explore team is looking into so stay tuned! I'd recommend following our Announcements page if you haven't done so already for any updates we have to share including new releases :) Zendesk Announcements
Are there any plans for the chat feature to be included in this beta test?
We are already transitioning to Messaging and we don't have any news yet if this will be available on the Classic Chat for this was primarily designed with Messaging and other main channels.
Alan apologies for the delay on replying to your question - could you describe the business rules you're concerned about creating a conflict for? Really, there is no risk of conflict, since the admin is creating a status like:
Status: Messaging Only (Support: Offline, Messaging: Online, Talk: Offline).
There's no risk of an agent going into a status that results in conflicting availabilities. If all channels are set to Online for a particular status (as with the forthcoming 'Online' status available in the EAP), it just means the agent will be able to receive inbound work from all three channels. I hope this helps but am happy to elaborate further!
What exactly does "work is added to the queue" mean for the away status? If we're making a custom status called "meeting" and someone could theoretically be in it for 1 hr or more, would that be correct or should we use offline? I wouldn't want work queueing for an agent for a long time and not get assigned to someone else. Thanks!
Remember, when you create a custom agent status, you will have the ability to choose to define an agent's availability in Support and Messaging (online, away, transfer only, offline).
If you create a new status called “In meeting”, you probably don't want the most time-sensitive channels of work routed to agents with this status. In that case, you could set Email (Support) to online, and Messaging to away. That would result in agents with the “In meeting” status only receiving tickets generated from Support email.
You can also find this here.
In case a ticket has been assigned to an agent, but the agent is on offline status, would there any impact on the SLA of this ticket?
Can someone please clarify if custom agent statuses can be utilized on agent workspace independent of Omnichannel routing on an account using chat and not message? The article says custom agent states become available once omnichannel is enabled, but I am trying to understand if there is a way to use custom states without using omnichannel.
It would be great to have agent statuses without omnichannel
Can you tell me if in the existing report on the status of agents we can see the status of "Transfer Only"?
Lila and Holley,
I was told that you can enable omnichannel routing and then set the capacity to zero for each agent to prevent tickets from being auto-assigned/automatically routed. Then you can use the custom agent statuses. I am currently looking into this option in my sandbox environment to see if that would work as expected.
However, I don't see a way for me to view which custom status each of my agents is currently in. We may hold off until we can see a list of our agents and which status they are in and possibly the ability for an Admin to make changes to those statuses. Also, I don't see a way to report time spent in each status yet. :)
Hi, is there a way to monitor agents' statuses from the admin perspective live time and manage it if needed? For example I've got an agent who's working but he set his status to `offline`. Am I able to change it if I'm a super user?
For Talk, Admin can change agent status on the Talk Dashboard.
It's not available for other Products. However, we already have it added on our roadmap where it will be integrated in our Live Dashboard. Please check the comment of our Community Manager.
Jen Cole did you have any luck with getting tickets to not assign to agents? We'd love to use the agent status for our team but don't want to automatically assign tickets to agents.
Moss Jen Cole,
I may be mistaken, but I believe all that you'd need to do in order to be able to use the custom agent statuses but NOT have anything automatically assign tickets to agents would be to NOT write any triggers that would add the auto-routing tag (shown in the screenshot below) to the ticket. At least, this was my plan for doing the same.
We haven't enabled omnichannel routing yet. We had to wait to implement this feature because we need to be able to see a live list of our agents and which status they are currently in.
Currently, I can go into Zendesk Chat or Zendesk Talk and see what status our agents are in. From what I understand, if we switch to Omnichannel routing there was no way for me to see what status each agent was in, so I'd be in the dark on that. And no reports for how long each agent was in each status.
Also, currently any of our agents can go into Zendesk Talk and adjust the Talk status for an agent. This helps if an agent forgets to change their status and we can update it. This isn't as important in omnichannel routing as it will change an agent to inactive after 15 minutes of inactivity, but it would be nice to have an Admin be able to make changes to an agent's status, if needed.
For these reasons, we decided it was important to wait until at least we could see a list of agents and their current statuses under the omnichannel routing feature. I'm hoping someone can share if they have been successful at not having anything automatically assigned after implementing omnichannel routing.
we're using omnichannel routing for a month or so now and it's a great feature. I can see agents' statuses with no issues. I can see it either via explore and a live board there or via the Assignee field. See below how I can see it. All greens are online agents and whites are offline.
This showed only when I enabled the routing as I can't recall seeing it before.
In explore live data I can drill into each box which gives me more detailed data:
Drill in for online agents:
Thank you Artur! That's so great! Looks like it might be time to try it out.
Are there plans to allow for the creation of more than 5 custom agent statuses?
Hi Steve Plichta, Did your theory on not setting up the trigger to avoid auto-assign work?
shelley I've tested my theory in our Sandbox, and everything seems to be ok there. Haven't been allowed to test it in production though, but I am optimistic.
Please sign in to leave a comment.