Zoho Desk Ticket Assignment: Assign Tickets to Team, Round Robin Assignment, and Assignment Rules

How to set up ticket assignment rules in Zoho Desk

Assignment rules live at Setup, Automation, Assignment Rules, and every rule belongs to a department. You choose the trigger first: the rule evaluates on ticket creation, ticket update, or both. Then you set criteria, the same field conditions you would use in a view, and pick the assignment type.

There are two families. A direct assignment rule sends a matching ticket to one agent or one team. The FAQ is precise about the limit: the direct assignment rule allows assigning a ticket to only one agent or one specific team at a time. A round robin rule rotates matching tickets across a set of targets, up to five per rule, using one of three methods: load based, sequential, or skill based.

For round robin you also set a threshold, the maximum number of open tickets each agent can hold, anywhere from 1 to 200. Zoho added agent level thresholds on top of the department wide number, so a new hire can be capped at 15 while a senior agent carries 60. Then decide whether offline agents are included and whether backlog assignment is on.

Rule order matters more than most admins expect. When a ticket matches more than one rule, the first rule in the list applies. When a ticket matches none, it stays unassigned. So the job is not just writing rules, it is ordering them from most specific to most general and checking that nothing broad sits above a narrow rule you care about.

The execution order that decides who gets the ticket

The single most useful fact in the Zoho Desk documentation is the order automations run in when a ticket triggers several at once. Verbatim: Direct assignment > Workflow > SLA > Round robin (sequential > load balancing > skill based) > Blueprint > Notifications.

Read it as a chain of decisions. Direct assignment gets the first say. A workflow rule gets the second, which matters because workflows can also set the ticket owner or team, and plenty of Zoho Desk accounts carry workflow rules from before assignment rules were configured. Round robin is fourth. By the time a rotation is evaluated, the ticket may already have an owner that an older rule placed there.

The practical diagnostic is short. When a round robin rule seems idle, open a ticket that should have rotated and read its history. If the owner was set by a workflow or a direct rule, the rotation was never the problem. Disable or narrow the earlier rule, then retest with a new ticket, because rules evaluate on events, not retroactively.

The order inside round robin is also fixed: sequential, then load balancing, then skill based. Teams that mix types across departments should keep that in mind when a ticket moves department mid life and meets a different rule type on the update trigger.

Load based versus sequential round robin, and the fast closer problem

Load based round robin assigns tickets to the least loaded agent first, then keeps balancing until agents hold equal numbers, capped at the threshold. On paper that is fair. In practice it counts open tickets, and open tickets are a poor measure of work.

A community thread titled load balancing ruins round robin functionality describes the pattern exactly. An agent who closes quick tickets returns to zero load and immediately becomes the least loaded agent, so they receive the next ticket, and the next. Colleagues working a few complex escalations look busy and receive nothing. A Zoho support reply in that thread stated that you cannot disable load balancing for round robin assignment. An older Zoho automation post from 2020 even published a custom function workaround that cycled through an agent list stored on a record to force a strict rotation.

The Sequential type is the documented fix. It assigns tickets equally among agents in a sequential fashion, following the alphabetical order of agent names, or the order agents were added for the first assignment. Sequential ignores load, which trades one problem for another: an agent buried in a hard escalation still takes their turn.

Neither type weights agents. A senior agent and someone in their second week receive the same share unless you split them into separate rules or cap the new hire with an agent level threshold. That is the gap most growing teams hit first, and it is the one that shows up as a quiet argument in standup rather than an error anywhere in the product.

Why Zoho Desk tickets sit unassigned: offline agents, thresholds, and backlog

Three documented defaults produce nearly every unassigned ticket complaint.

Online status. By default, only agents who are online on the email channel are assigned tickets. An agent who forgets to set themselves online, or who works tickets from the mobile app without the right status, is invisible to the rotation. Overnight and weekend tickets queue unassigned until someone comes online. You can include offline agents, but then the opposite happens: tickets land on people who are asleep.

No reassignment. The assignment FAQ says it plainly: by default, if an agent is unavailable or out of office, the ticket remains assigned to them, and no automatic reassignment occurs. Status only affects new assignments. Nothing pulls work back from an absent agent.

Thresholds and backlog. When every agent reaches their threshold, new tickets cannot be assigned and wait. A community post asked the obvious question: once a queue opens up, will the waiting ticket go to the first available agent? The answer is the Assign Backlogs toggle, with a separate backlog threshold from 1 to 50. The documentation attaches a condition that surprises people: unassigned or backlog tickets are only assigned in a round robin manner if the ticket has received a customer response within 30 days. A customer who wrote once and went quiet can sit in the backlog indefinitely.

The Enterprise edition adds Assign ticket on closure, which hands the next backlog ticket to an agent the moment they close one. On Professional, backlog assignment happens on the round robin schedule instead.

Assign tickets to a team, and which edition you need

To assign a ticket to a team, create a direct assignment rule with the team as the target, or pick the team inside a round robin rule. A team target in a direct rule routes the ticket to the team queue; a round robin rule then decides which agent on it owns the ticket. Teams are department scoped, so a cross department escalation team needs membership in each department it serves.

Edition gating is where the budget conversation starts. From the Zoho Desk pricing page in USD, per agent per month: Express $7 billed annually ($9 monthly), Standard $14 ($20), Professional $23 ($35), Enterprise $40 ($50). Round robin assignment is listed in Professional, described as allocating tickets according to current workload or in a specific order. Skill based assignment, routing by proficiency and availability, is listed in Enterprise.

So a 12 agent team that needs skills routing pays the Enterprise rate for all 12 seats. Billed annually, that is $5,760 a year against $3,312 on Professional, a $2,448 annual step taken for one routing capability. Enterprise does include other things, 50 light agents among them, and for some teams that bundle is worth it. For a team whose only reason to move is skills, it is an expensive way to buy one rule type.

Where Assigner fits beside Zoho Desk, and where it does not

The Zoho Desk mechanisms share one design: they fill the owner once, from a static list, and never revisit. None of them weight agents by experience. None of them reassign when an agent goes out. Load counts open tickets, not effort, and the alternative ignores load entirely.

Assigner is task assignment software built for exactly that layer. You define the rules, round robin, weighted round robin, load balanced, skill based, or priority, and each assignment records the reason: who was eligible, who was skipped for being unavailable or at capacity, and why this person won. When someone is out, their work is visible and can be redistributed instead of aging in their queue. The same rules cover tickets, sales leads, and internal requests, so a team whose Zoho Desk work spills into other queues runs one routing policy.

It is priced at $12 per user per month billed yearly ($15/mo billed monthly), and it sits beside Zoho Desk rather than replacing it; Zoho Desk stays the system of record for the ticket and the customer conversation. It is not a live two way sync. The AI assists the routing, but the rules stay yours and every assignment is explainable.

If your team is small, your agents are interchangeable, and sequential round robin on Professional distributes work the way you want, keep it. Assigner is for the point where fairness, availability, and a written reason per ticket start to matter more than the rotation itself.

How do I set up ticket assignment rules in Zoho Desk?

Go to Setup, Automation, Assignment Rules, choose the department, and create a rule. Pick the trigger (ticket creation, update, or both), set the criteria, then choose direct assignment to one agent or team, or round robin across up to five targets. For round robin, set the method, the threshold, offline handling, and backlog assignment.

How do I assign a ticket to a team in Zoho Desk?

Create a direct assignment rule with the team as its target, or include the team in a round robin rule. The direct rule allows one agent or one team per rule, so different teams need separate rules ordered carefully. Teams are department specific, so the team must exist in the department where the rule runs.

How does round robin assignment work in Zoho Desk?

A round robin rule rotates matching tickets across its targets using one of three methods. Load based sends each ticket to the least loaded agent until loads are equal. Sequential rotates in alphabetical order of agent names. Skill based matches tickets to agents holding the required skill. Every method respects the per agent threshold.

Which Zoho Desk plan includes round robin assignment?

Round robin assignment is listed in the Professional edition, $23 per agent per month billed annually or $35 billed monthly, and in Enterprise. Skill based assignment is listed only in Enterprise, $40 per agent per month billed annually or $50 monthly. Express and Standard do not list round robin.

Why are tickets not getting assigned in Zoho Desk?

Usually one of four reasons: no active rule matches the ticket, an earlier rule or workflow already set the owner, no agent is online on the email channel, or every agent has reached their threshold. Backlog tickets are also only assigned if the customer responded within 30 days. Check the ticket history first.

What is the execution order of assignment rules in Zoho Desk?

Zoho documents it as direct assignment, then workflow, then SLA, then round robin (sequential, then load balancing, then skill based), then Blueprint, then notifications. If a ticket matches several assignment rules, the first rule in the list applies, so rule order acts as routing logic.

Can I disable load balancing in Zoho Desk round robin?

Not inside a load based rule. A Zoho support reply in the community stated that load balancing cannot be disabled for round robin assignment. Use the Sequential round robin type instead, which assigns tickets in a fixed rotation by agent name order and does not consider how many open tickets each agent holds.

Does Zoho Desk assign tickets to offline agents?

Not by default. Only agents who are online on the email channel receive round robin assignments. The rule settings let you include offline agents, which keeps tickets moving overnight but assigns work to people who are not working. Neither setting reassigns tickets already held by an agent who goes offline.

What is the ticket threshold in Zoho Desk round robin?

The maximum number of open tickets an agent can hold before round robin skips them, settable from 1 to 200. You can set one department wide threshold and override it per agent. When all agents hit the threshold, new tickets wait unassigned until the backlog setting hands them out.

What does Assign Backlogs do in Zoho Desk?

It lets round robin assign tickets that waited because every agent was at threshold or offline, using a backlog threshold from 1 to 50. The documentation limits it to tickets with a customer response within the last 30 days. Enterprise adds assign ticket on closure, which hands out a backlog ticket as soon as an agent closes one.

Does Zoho Desk reassign tickets when an agent is out of office?

No. The assignment FAQ states that by default a ticket remains assigned to an agent who is unavailable or out of office, and no automatic reassignment occurs. Redistributing an absent agent queue is a manual job or a custom function, which is a common reason teams add a routing layer beside the help desk.

Do I need Zoho Desk Enterprise for skill based ticket assignment?

Yes. Skill based assignment is listed in Enterprise only. For a 12 agent team billed annually that is $5,760 a year against $3,312 on Professional. Assigner offers skill based and weighted routing at $12 per user per month billed yearly, beside Zoho Desk, without moving every seat up a tier.