Assignment rules are one of the first things I set up in a new Zoho CRM account, and one of the first things I fix in an inherited one. The feature is simple, but its behaviour has edges that are easy to miss: which records trigger it, what happens when a rep is offline, and how the rule order works. Everything below is based on Zoho's help article "Setting up Assignment Rules" plus what I see in real implementations. Edition availability changes, so check the Zoho CRM features page for your edition.
What triggers an assignment rule, and what does not
According to Zoho's help documentation, assignment rules apply to records created through import, web forms and the API. Records created manually inside the CRM do not trigger them. That one fact explains most "the rule is not working" tickets I get. If your SDRs create leads by hand after a call or event, either they set the owner themselves, or you need a workflow rule that runs on create and updates the owner. Also check your web form settings. Zoho web forms let you choose an assignment rule on the form itself, and if no rule is selected there, leads land with the default owner. The same applies to integrations: confirm the API call or connector actually requests the rule to run.
Setting up a lead assignment rule step by step
Go to Setup, then Automation, then Assignment Rules, choose the Leads module and create a new rule. Give it a name that says what it does, such as "Inbound India SMB", not "Rule 1". Inside the rule you add entries. Each entry has criteria (or applies to all leads) and an assignee: a specific user, a role, or a group. Entries are evaluated in order, so put the most specific criteria at the top and the broadest at the bottom. Then set a default user who receives leads that match nothing. Zoho lets you add a follow-up task for the assigned user, which I always enable with a short due date so the lead appears on the rep's task list. Users need the "Assignment Rules and Threshold" permission in their profile to manage these rules.
How round robin works in Zoho CRM
When an entry assigns to more than one user, Zoho distributes records among them in round robin order. I usually build round robin on a group or a hand-picked user list per segment, rather than a role, because role membership changes for reasons unrelated to sales capacity. One limitation to test: some users on the Zoho community have reported that rotation order appears to restart on each import, which can favour the same reps when you import small batches several times a day. If you rely on imports, run a test with a few batches and check the distribution before trusting it. Zoho also offers availability checks before assigning, based on a user's online status, their shift hours, or both, so leads do not go to someone who is offline or off shift.
Writing criteria that hold up
Criteria can compare a field to a value or to another field, and Zoho's documentation caps a rule entry at 25 criteria. Encrypted fields cannot be used. In practice, the limit that bites is data quality, not the criteria count. If Country or Industry is a free-text field on your form, "India", "IN" and "india " will not match the same entry. Convert routing fields to picklists before building rules. I also keep a "Lead Source" condition out of most routing entries unless sources genuinely go to different teams, because adding a new campaign source later then silently breaks assignment. Document each entry in your CRM data dictionary so the next admin knows why it exists.
Pitfalls I find in inherited Zoho accounts
The same issues come up repeatedly. A default user who left the company months ago. Zoho falls back to the default user when the selected user is unavailable, deactivated or deleted, so an outdated default means leads pile up somewhere no one is looking. Overlapping entries where a broad entry sits above a specific one, so the specific one never fires. Workflow rules that also update Lead Owner, fighting with the assignment rule. Duplicate leads from web forms, assigned to a different rep than the existing record. And no reporting: nobody checks leads per owner, so an imbalance runs for weeks. A monthly report of leads created by owner and source catches most of these early.
Going beyond assignment: Blueprint and escalation
Assignment rules decide who owns the lead. They do not make sure the owner acts. For that, I pair them with a workflow rule or Blueprint state that sets an SLA on the New status and escalates when it is breached, as described in my sales and marketing SLA template. Zoho also offers Zia-suggested owners when there is enough history, and the documentation mentions it needs activity data from the previous six months. I treat that as a later optimisation, not a starting point. Bigin, Zoho's lighter CRM, handles assignment differently, so do not assume these steps carry over one to one.
FAQ
The most common reason is that the leads were created manually, which does not trigger assignment rules. Other causes include the web form or API call not specifying the rule, criteria that do not match free-text values, and a broader entry above the intended one.
Yes. When a rule entry assigns to multiple users, Zoho distributes records among them in round robin order, and can check online status or shift hours before assigning. Test the rotation with your import pattern before relying on it.
Availability and limits vary by edition and change over time. Check the current Zoho CRM edition comparison and features page for your plan before designing your routing.