Lead routing rules that a human can read (and therefore trust)
Round-robin, territory, segment, load and availability — how to write routing logic that is fair, explainable and survives the next reorg.
13 Oct 2025 · 2 min read · by HeiSyn
The fastest way to lose a sales team's trust in an inbound system is routing they cannot predict. If nobody can say why a lead went to Priya rather than Tom, every missed quota becomes an argument about the router. Routing rules should be short enough to fit on one page and deterministic enough that a manager can replay any assignment by hand.
The order of operations
First, existing relationships: if the company has an owner in the CRM, the lead goes to that owner, always. Second, disqualification: leads that fail hard filters go to a nurture pool, not a rep. Third, segment: enterprise, mid-market, SMB by employee count or revenue band, each with its own pool. Fourth, territory within the segment, by country or region. Fifth, round-robin within the resulting pool, weighted by capacity if capacities differ. Sixth, availability: skip anyone out of office or already over a daily cap, and fall through to the next.
Write it as a table, not a flowchart
A table of rules — condition, pool, priority — is easier to read, easier to test and easier to change than nested branches. Keep it in a sheet the RevOps lead owns, and have the automation read the sheet rather than hard-coding it. When the territory map changes, the sheet changes; the workflow does not.
Log the reason on every assignment
Every lead should carry a one-line explanation: 'Mid-market, EMEA, round-robin position 3 of 5, Priya'. When a rep asks why, the answer is on the record. The log also makes fairness auditable: pull a month of assignments and check the distribution matches the weights.
Test it before it is live
Replay last month's leads through the new rules and compare the assignments to what actually happened. Surprises found in a spreadsheet cost nothing; surprises found in a rep's pipeline cost trust. Then run new and old in parallel for a week with the new one only logging, and switch when the log looks right.
Questions people ask next
- How do we handle round-robin fairness when reps have different capacities?
- Weight the rotation: a full-time rep gets two turns for every one a part-time rep gets. Cap daily assignments per person and skip anyone at the cap. Publish the weights. Fairness is a perception, and perception depends on the rules being visible.
- What about leads that match an existing account?
- They go to the account owner, always, before any other rule runs — including leads from a different person at the same company. Matching is by email domain with a manual exception list for shared domains such as generic mail providers.
- How do we route leads that do not match any rule?
- To a named fallback — usually a manager or a shared queue with a short response target — with an alert, never silently to nobody. Review the fallback queue weekly; leads that land there consistently reveal a missing rule.
Want this built for your team?
A free scoping call: we map your motion, name the number that should move, and quote a fixed-scope build.
Related
- Speed-to-lead: what to automate in the first five minutes after a form fill
- Real estate lead response: the automation that gets a viewing booked before the competing agent calls
- Inbound automation for education and coaching businesses: from enquiry to enrolled
- Lead scoring that sales actually uses: explainable, current and tied to routing
