By the CodeStringers Team — Zoho Experts & Custom Software.
A lead that sits unassigned for an hour is a lead your competitor is already calling. Manually divvying up incoming records is where that hour goes — someone glances at the queue, decides who gets what, and forgets half the time. Knowing how to set up assignment rules in Zoho CRM kills that delay: every incoming record routes to the right owner the instant it lands. Teams ask our Zoho CRM consultants to build this all the time, and it's straightforward — as long as you understand the one thing that makes assignment rules fire. Let's set one up, and cover that gotcha before it bites you.
For the strategy behind who should get which lead, our assignment rules explainer covers the reasoning. This is the build.
An assignment rule automatically sets the owner of an incoming record — Leads, Contacts, Deals, Cases, or a custom module — based on criteria you define (source: Zoho help: Set assignment rules). Instead of "who's free to take this," the CRM decides by rule: enterprise leads to a senior rep, west-coast leads to the west-coast team, everything else split evenly.
Read this before you build anything. Zoho's documentation is blunt: "You can use Assignment rules for the records generated through import, Webform, and API only. You cannot use Assignment Rules if you are creating the Records manually." Rules also don't fire on records created by a workflow (source: Zoho help: FAQs: assignment).
So an assignment rule routes leads that arrive from your website forms, your bulk imports, and your API integrations — the channels where volume actually comes from. It will not reassign a record a rep types in by hand. Every "my assignment rule isn't working" ticket we see traces back to this. Build your rules for the automated inflow, and handle manual entries a different way.
Open the builder. Go to Setup > Automation > Assignment > Create Assignment Rule.
Name it and pick the module. Give the rule a clear name (Leads is the common case) and click Next.
Add rule entries. Each entry has two parts: which records it applies to (all records, or records matching conditions you set — up to 25 criteria per entry) and who gets them (a user, role, or group).
Turn on round-robin where you want even distribution. When you assign an entry to multiple users, Zoho distributes matching records among them in a round-robin rotation — the built-in way to split a shared queue fairly.
Set a default user. Point any record that matches no entry at a catch-all owner so nothing falls into a void.
Save, then invoke it. The rule only runs when you attach it: select it in the Import wizard, bind it to a Web form, or pass its id via the API.
Rule entries are evaluated top-down, and the first match wins — a record is assigned by "the first rule they qualify for." Order matters: put your most specific entries (enterprise, named accounts) above your catch-alls, or a broad entry near the top will grab records you meant to route elsewhere. In the automation sequence, assignment rules run first, before review and approval.
Worked example. On Leads, three entries in order: (1) Industry is Enterprise → your senior AE; (2) Region is West → the west-coast rep; (3) all remaining records → round-robin across the SDR group; plus a default user as the safety net. High-value leads reach the right person, everything else spreads evenly, and nothing sits unowned.
This pairs naturally with lead scoring: score first to find the good leads, then route them. If you've set up scoring rules, an assignment rule can send your highest scorers straight to your closers while the rest feed the round-robin — the score decides how good, the assignment rule decides who works it. It all starts with clean lead capture feeding the rules.
Assignment rules are one of the quietest, highest-return automations in Zoho CRM — set once, and every lead lands on the right desk from then on. If you'd like the routing logic mapped to your real team and territories, our business systems consultants build it as part of a wider Zoho integration. Book a free Zoho consultation and we'll make sure no lead waits on a human to hand it off.
In a no-risk discovery we look at your CRM, finance and operations systems and who owns each part, and show what a connected system would do differently. You pay only if you proceed. Or see how we approach it.
More on the same problem:
What Happens To A Lead At 6pm On Friday | Zoho CRM Assignment Rules And Routing (video)
Lead Distribution Software in Zoho CRM: Route and Rank, Not Either/Or (article)
How to Set Up Scoring Rules in Zoho CRM (Step by Step) (article)
Almost always because the record arrived by a channel the rule does not cover. Assignment rules run only on records created through import, web forms and the API, and only when the rule is attached to that channel. Records typed in manually or created by a workflow are not routed. Check that the rule is selected in the import wizard or bound to the form, then check the entry order and the default owner.
Use a workflow rule instead. A workflow that triggers on record creation can update the Lead Owner field based on criteria, which covers manual entry that assignment rules ignore. Round-robin distribution is not available this way, so teams that need even distribution for manual entries often use a custom function that picks the next owner from a list and writes it to the record.
Round-robin distributes evenly among the users in an entry, but it does not know who is on leave or already overloaded. Assignment rules can exclude users by editing the entry, and Enterprise editions add availability settings that skip users who are marked unavailable. For capacity-based routing, such as a cap on open leads per rep, a custom function that checks counts before assigning is the usual answer.
The limit depends on edition, and each rule can hold many entries with up to 25 criteria each. Most teams need only one rule per module, with the ordering of entries doing the real work. If you find yourself creating several rules for one module, it is usually a sign that the criteria should be combined into a single ordered list with a default owner at the bottom.
Territory assignment suits teams whose reps own regions or industries and where local knowledge matters. Round robin suits inbound volume that any rep can handle and where fairness matters more than fit. Many teams combine them: specific entries route named accounts and regions first, and a final round-robin entry shares everything else. Review the split quarterly against conversion by owner.
"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.
Say who you are and ask. A person replies within one business day.
