Zendesk Omnichannel Routing: Queues, Capacity Rules, and Round Robin Ticket Assignment

What is Zendesk omnichannel routing?

Omnichannel routing is Zendesk's built-in assignment engine, and it replaces the older pattern of triggers that shove a ticket at a group and hope somebody picks it up. It handles three channel families: email (which includes web form, API, and side conversation tickets), messaging (native messaging, WhatsApp, SMS, Facebook Messenger and the rest), and calls. The engine watches agent status and current workload and pushes work out, rather than leaving a pile for agents to pick through. Two prerequisites are easy to miss. Agent Workspace has to be active on the account, and if you use Chat then native messaging or Sunshine Conversations has to be active too. Omnichannel routing also cannot be turned on if live chat is the only channel you run. Worth knowing before you plan around it: predictive routing applies to messaging tickets only, voice tickets cannot be reassigned after the first assignment, light agents are never assigned tickets, and tickets handled by an AI agent do not route until they escalate to a human. None of those are dealbreakers, but each one has produced a support thread from somebody who assumed otherwise.

Turning it on without breaking a day of tickets

The path is Admin Center, then Objects and rules, then Omnichannel routing, then Routing configuration, then Turn on omnichannel routing. Before you click it, know the two things that happen next. First, the moment omnichannel routing is turned on, every agent is set to offline. Email tickets need an agent who is online or away, and messaging and calls need online, so until your team changes status nothing routes anywhere. Turn it on at a quiet hour and tell people to set themselves online, or you will spend the first afternoon convinced the queues are broken. Second, email tickets do not route on group assignment alone. You define an auto-routing tag during setup, and a ticket trigger has to do two things to every email ticket you want routed: assign a group and add that auto-routing tag. Miss the tag and the ticket sits with a group and never enters a queue, which looks identical to a queue misconfiguration and is diagnosed nowhere near the queue. On Professional and above you can also set priority and add or update skills from the same trigger. The third gotcha arrives after setup: triggers only run on new or updated tickets. Everything already open when you flipped the switch stays exactly where it was. If you want the existing backlog routed, it has to be touched so the triggers fire, usually with a bulk update.

How Zendesk decides which agent gets the ticket

This is the part worth reading slowly, because the word round robin is doing some work it has not earned. Zendesk assigns to the available agent who has gone the longest time without being assigned work for that channel. That is longest-idle selection, not a circular rotation through a list. In a steady state with similar agents the two look identical, which is why the distinction goes unnoticed until it matters. It stops matching intuition as soon as agents differ. Idle time measures how long since the last assignment, not how much is currently open. An agent who picked up one brutal multi-day escalation two hours ago looks busier to the counter than someone who closed six quick tickets in that time, and the counter is what decides. Ordering within the queue depends on your plan: Team uses the oldest eligible-for-routing timestamp, Growth and above lets you choose oldest timestamp or soonest SLA breach, and Professional and above orders by highest priority first and then by timestamp or SLA breach. Skills sit on top of this. Agents must hold the skills a ticket requires, and you can define up to 10 skill types with 30 skills each. Skills-based routing and custom queues need Suite Professional or above, or the Enterprise tier on standalone Support plans, which is the single most common reason a team reads this page and finds the feature they want is one tier up. If you are weighing that upgrade specifically for routing, our Zendesk skills-based routing alternative lays out the cost comparison honestly.

Queues and capacity rules, and the limit that is not a limit

Every account gets a standard queue, where eligibility comes from the ticket's assigned group and nothing else. On Professional and above you can build custom queues with their own conditions, evaluated when the ticket arrives, and anything that matches no custom queue falls through to the standard queue. That fallthrough is a feature and also a hiding place: a ticket nobody wrote a queue for is not an error, it is a ticket sitting in the standard queue waiting on group-based eligibility that may not exist. Build a deliberate catch-all queue with a real owner rather than letting the standard queue serve as one by accident. Capacity rules cap how many items an agent can hold at once, set per channel, defined as a number or a percentage of spare capacity. They are the closest thing Zendesk offers to workload awareness, and they come with a caveat straight from the documentation: agents can assign themselves work in excess of these limits if they want to. So capacity is a ceiling on what the engine pushes, not a ceiling on what an agent ends up holding. In practice the fastest and most willing people route around their own limit, which is the exact distribution problem capacity rules were meant to solve. If enforced ceilings matter to you, workload balancing that distributes open effort rather than assignment counts is the mechanism to look for, and availability routing covers the shift and time-off half of the same problem.

When omnichannel routing is enough, and when it is not

It is enough more often than a vendor page usually admits. If your tickets are broadly interchangeable, your agents have similar skills, and you are on a plan with custom queues, omnichannel routing is a well-built engine and adding anything to it would be waste. Turn it on, tag your email properly, set sensible capacity rules, and move on. The honest boundary is the point where the decision stops being about the ticket and starts being about the person. Longest-idle selection cannot see current open effort. Capacity rules can be exceeded by the people most likely to exceed them. Skills matching is real but gated a tier up, and capped at 10 types. And omnichannel routing routes Zendesk tickets, which means the leads your sales team is chasing and the internal ops tasks nobody has a system for stay unrouted, each with a different half-solution. That is the gap Assigner fills, beside Zendesk rather than instead of it. One engine handles support ticket routing, sales lead routing, and ops task assignment, with skills-based routing and enforced load limits included at $12 per user per month, and every assignment records the rule it used and the candidates it considered. It is a companion rather than a live two-way sync, and it is built to help rather than to guarantee an outcome.

What is Zendesk omnichannel routing?

Omnichannel routing is Zendesk's built-in engine that assigns email, messaging, and call tickets to agents using queues, agent status, capacity limits, ticket priority, and optionally skills. It pushes work to agents rather than leaving tickets in a pile to be picked up. It requires Agent Workspace to be active and cannot be enabled if live chat is your only channel.

How do you turn on omnichannel routing in Zendesk?

Go to Admin Center, then Objects and rules, then Omnichannel routing, then Routing configuration, and click Turn on omnichannel routing. Enter an auto-routing tag, create your queues, then build ticket triggers that assign a group and add that auto-routing tag to email tickets. Save. Every agent is set to offline the moment you turn it on, so nothing routes until they come back online.

How does round robin work in Zendesk omnichannel routing?

Zendesk assigns work to the available agent who has gone the longest time without being assigned work for that channel. That is longest-idle selection rather than a fixed rotation through a list, and it measures time since the last assignment rather than how much work is currently open. An agent holding one heavy escalation can look busier to it than someone who closed six quick tickets.

What plan do you need for Zendesk omnichannel routing?

Basic omnichannel routing is available on Suite Team and above, and on Support Team plans and above. Custom queues, skills-based routing, and priority-based ordering start at Suite Professional, or the Enterprise tier on standalone Support plans. Team and Growth accounts are limited to group-based routing through the single standard queue.

Why are my Zendesk tickets not routing after enabling omnichannel routing?

Check three things in order. Are your agents online, since turning omnichannel routing on sets everyone offline. Does your trigger add the auto-routing tag as well as assigning a group, because email tickets need both. And is the ticket new or updated, since triggers only run on new or updated tickets and anything already open when you enabled routing stays where it was.

What is the auto-routing tag in Zendesk?

The auto-routing tag is a tag you define during omnichannel routing setup that marks an email ticket as eligible for routing through the standard queue. A ticket trigger has to add it in addition to assigning a group. Without the tag the ticket keeps its group and never enters a queue, which is the most common reason email tickets appear to ignore routing entirely.

What are Zendesk omnichannel routing queues?

A queue is the holding area that decides which agents are eligible for a ticket. Every account has a standard queue where eligibility comes from the ticket's assigned group. Suite Professional and above can create custom queues with their own conditions, evaluated when the ticket arrives. Tickets matching no custom queue fall through to the standard queue.

How do Zendesk capacity rules work?

Capacity rules cap how many items an agent can be assigned at once, set per channel as a number or as spare capacity. They limit what the routing engine pushes to an agent. They do not lock the agent out: Zendesk documents that agents can assign themselves work in excess of these limits, so capacity is a ceiling on automated assignment rather than on total workload.

How many skills can you use for Zendesk skills-based routing?

You can define up to 10 skill types, and each skill type can hold up to 30 skills. Agents must possess the skills a ticket requires to be eligible for it. Skills-based routing needs Suite Professional or above, or the Enterprise tier on standalone Support plans, which is often the deciding factor for smaller teams.

Does Zendesk omnichannel routing balance workload?

Partly. Capacity rules cap concurrent assignments per channel, which is workload awareness of a kind, and agent selection uses longest idle time rather than open effort. So it spreads assignments rather than balancing work, and its ceiling can be exceeded by agents self-assigning. Genuine load balancing needs the engine to weigh open effort and enforce the limit.