Omnichannel routing is a highly configurable routing solution that can route tickets from email (including web form, side conversations, and API), calls, and messaging conversations. Agents are considered available to receive work through omnichannel routing when they have an eligible status and spare capacity for the channel.
When configuring omnichannel routing, you can choose whether to assign work based on the highest spare capacity or based on the time elapsed since agents last received work for that channel, which is commonly referred to as round robin.
Understanding how round robin routing changes the standard omnichannel routing behavior
The assignment methods for omnichannel routing are straightforward on the surface: either you're routing based on spare capacity or time since last assignment for the channel. However, the way these methods interact with other routing configuration options can help you make an informed decision when setting up your own omnichannel routing workflows.
- Any ticket assignment to an agent, whether manual or by omnichannel routing
- A call or messaging ticket is offered to an agent
- A ticket assigned to an agent is reopened
Scenario 1: Agents available
- Agent 1: Has a spare capacity of 1. Was assigned a messaging conversation ticket 5 minutes ago.
- Agent 2: Has a spare capacity of 2. Was assigned a messaging conversation ticket 3 minutes ago.
- Agent 3: Has a spare capacity of 3. Was assigned a messaging conversation ticket 1 minute ago.
Round robin
If you're using the round robin method, omnichannel routing assigns the messaging ticket to agent 1 because they've had the longest time elapsed since being assigned a ticket for the channel. This behavior is consistent across all channels.
Highest spare capacity
If you're using the standard method of highest spare capacity, omnichannel routing assigns the messaging ticket to agent 3 because they have the most spare capacity for the channel. This behavior is consistent across all channels.
Scenario 2: No agents have spare capacity
- Agent 1: Has no spare capacity. Was assigned a messaging conversation ticket 5 minutes ago.
- Agent 2: Has no spare capacity. Was assigned a messaging conversation ticket 3 minutes ago.
- Agent 3: Has no spare capacity. Was assigned a messaging conversation ticket 1 minute ago.
In this scenario, omnichannel routing would behave the same way for both routing methods. The ticket would be assigned to the first agent that drops below their maximum capacity. This is true for all channels.
Scenario 3: Routing with focus mode turned on
- Agent 1: Has a spare capacity of 4. Was assigned a messaging conversation ticket 5 minutes ago. Is on an active call.
- Agent 2: Has a spare capacity of 2. Was assigned a messaging conversation ticket 3 minutes ago. Isn't on an active call.
- Agent 3: Has a spare capacity of 4. Was assigned a messaging conversation ticket 1 minute ago. Isn't on an active call.
Round robin
If you're using the round robin method with focus mode, omnichannel routing assigns the messaging ticket to agent 2 because they've had the longest time elapsed since being assigned a ticket for the channel while also not having an active call. This is because focus mode prevents omnichannel routing from assigning messaging tickets to an agent while they're working on a call and vice versa. Email tickets are excluded from focus mode, and therefore would be routed to agent 1 in this scenario.
Additionally, if focus mode wasn't enabled but all other factors remained the same, omnichannel routing would assign the ticket to agent 1 because they've had the longest time elapsed since being assigned a ticket for the channel.
Highest spare capacity
If you're using the standard method of highest spare capacity with focus mode, omnichannel routing assigns the messaging ticket to agent 3 because they have the most spare capacity for the channel while also not having an active call. This is because focus mode prevents omnichannel routing from assigning messaging tickets to an agent while they're working on a call and vice versa.
Email tickets are excluded from focus mode, and therefore would be routed to agent 1 in this scenario because agent 1 and agent 3 have the same spare capacity, but agent 1 has gone longer without being assigned work for the channel. This would also be the behavior if focus mode was off but all other factors remained the same.
Turning on round robin routing
Round robin routing can be turned on in your omnichannel routing configuration.
- In Admin Center, click
Objects and rules in the sidebar, then select Omnichannel routing > Routing
configuration. - On the Routing Configuration page, click Edit next to the Initial routing configuration.
- Under Assignment method, select Round robin.
- Click Save.