Omnichannel routing and capacity rules

Ref: D01 · Track: Admin & Reporting · Time to complete: ~6 min

Why this matters

Tickets, chats, and calls land. Who gets them? Omnichannel routing is how Zendesk assigns work to your agents automatically, respecting their skills, availability, and current load. Done well, your team feels an invisible hand helping them; done poorly, it either over-assigns one person or sends everything to the least-equipped agent.

The three pillars

Omnichannel routing has three moving parts:

1. Agent status

• Online: receiving work.
• Away: not receiving new work, but current work continues.
• Transfers-only (Talk): only takes transferred calls.
• Offline: fully unavailable.

This covers all channels. Agent sets their status from the top bar (see A02).

2. Capacity rules

Per channel per agent — how many concurrent items they can handle: - Talk: 1 call (calls are blocking). - Messaging: e.g. 3 concurrent chats. - Email: e.g. 10 open tickets.

When an agent is at capacity for a channel, Zendesk stops routing new items to them on that channel until they drop below.

3. Skills and groups

• Groups: agents are in groups (e.g. Tier 1, Tier 2, Billing, Technical). Tickets routed to the right group first.
• Skills: fine-grained tags on agents (e.g. French, certified-v3, enterprise-support). Triggers can add skills to tickets; routing matches skilled agents.

Routing modes

Round-robin

Tickets go to the next agent in rotation with capacity. Fair distribution, but doesn't respect skill.

Load-based

The agent with the most capacity headroom gets the next ticket. Keeps load balanced.

Skill-based

Only agents matching required skills are considered. Falls back if nobody's available.

Most mid-size orgs use a combination: skill-based with load-balancing among the qualified pool.

A worked example

Team setup: - Group: Tier 1 Support (6 agents) - Group: Billing Specialists (2 agents) - Skill: french (3 agents have it)

Ticket comes in tagged "billing" and written in French: 1. Routing filters to Billing Specialists group. 2. Of those, filters to agents with skill french. Say 1 qualifies. 3. That agent has capacity → ticket goes to them. 4. If that agent is at capacity, ticket queues (or falls back to Tier 1 French-speakers, depending on config).

Setting capacity rules (admin)

Admin Center → Objects and rules → Omnichannel routing:

1. Define a capacity rule: channel + max concurrent work (e.g. "Messaging: 3").
2. Assign capacity rules to agents — same rule for everyone, or different rules per team/seniority.
3. Save.

Capacity can also be inferred from plan defaults, but explicit rules are recommended.

The overflow scenario

What happens when nobody with the right skill is online?

Options (configurable): - Queue: ticket waits until a qualified agent appears. - Route to a broader group: falls back to Tier 1 if Tier 2 is unavailable. - Alert the admin if queue depth exceeds a threshold.

Chose poorly, this produces either angry customers (long waits) or overwhelmed Tier 1 (flooded with out-of-scope work). Watch queue depth reports weekly.

Reassignment rules

When an agent goes Offline, work they own can: - Stay with them (resumes when they return). - Auto-reassign (round-robin / group default).

For Talk and Messaging (real-time), auto-reassign is typical. For email tickets, stay-with-agent is usually fine; they'll resume tomorrow.

The day-to-day admin view

Admin Center → Omnichannel → Dashboard (or equivalent): - How many agents online per channel. - Queue depths. - Current load per agent. - Idle agents (online but no work).

Use this to staff up when queues are spiking and to coach agents whose capacity is maxed out while peers are idle.

Gotchas

• Capacity is per-channel, not global. An agent might be at Talk capacity (1 call) but still receive email. That's usually correct but needs to be understood.
• Skills are case-sensitive in some views. Maintain a short, controlled skill vocabulary and stick to it.
• Round-robin + time-off = bad. If an agent went offline mid-rotation, make sure they're fully excluded; half-in states can freeze rotation.
• Group overlaps. Agents in multiple groups get work from all of them. Capacity math gets non-intuitive — audit carefully.
• The "online idle" problem. Agents marked online but not receiving tickets usually indicates a skill or group mismatch. Dig in.

Quick check — have you got this?

• An agent is marked Online and Messaging capacity is 3. They're handling 3 chats. A new chat comes in. What happens?
• A ticket needs skill french. Nobody online has french. Options?
• Capacity for Talk is usually set to what?

Related articles

• A02 — Making sense of the top bar
• B01 — Talk: online, away, and transfers-only
• D02 — Explore: the Support dashboard
• D05 — Live dashboards for Talk