Lead routing: round-robin vs rule-based assignment
By the OrbitPi product team · Updated · 5 min read
Lead routing decides which sales rep or team gets each new enquiry. Round-robin assigns leads to reps in turn, which spreads work evenly. Rule-based routing assigns leads by attributes such as branch, product, channel or language, which sends each lead to the best-placed person. Most teams combine them: ordered rules choose the right team, round-robin spreads leads within it, and a shared pool with a response-time target catches anything left unassigned.
Key takeaways
- Round-robin is simple and fair but ignores fit; rule-based routing matches fit but can overload one person.
- Order routing rules from most specific to most general, and always finish with a fallback.
- Round-robin should skip reps who are on leave, off shift or at capacity.
- Shared pools work for small teams if every pooled lead has a first-response target.
- Measure routing by time to first response and by conversion per source, not only by volume.
What is lead routing?
Lead routing is the set of rules that decides who owns a new enquiry as soon as it arrives, whether from a website form, an ad campaign, a walk-in or an imported list. Good routing gets each lead to someone who can help, quickly, without a manager assigning it by hand.
Poor routing shows up as leads nobody follows up, two reps calling the same person, or a few reps overloaded while others wait for work.
The main lead routing methods
| Method | How it works | Best for | Watch out for |
|---|---|---|---|
| Manual | A manager reads each lead and assigns it | Very low volumes | Delays outside office hours; bottleneck on one person |
| Round-robin | Leads go to each rep in turn | Teams where any rep can handle any lead | Ignores language, location and product fit |
| Weighted round-robin | Some reps get a larger share | Mixed seniority or part-time reps | Weights drifting from real capacity |
| Rule-based | Attributes such as branch, product or channel decide the owner | Multi-branch or multi-product teams | Rule conflicts and gaps with no fallback |
| Shared pool | Leads wait in a queue for any team member to claim | Small teams and overflow | Cherry-picking and leads left waiting |
When round-robin works best
Round-robin works when reps are interchangeable: the same product, the same region and the same language. It is easy to explain, feels fair to the team and needs no maintenance.
Plain round-robin breaks down when a rep is on leave, off shift or already handling too many open leads, because the next lead still lands with them. Availability-aware round-robin skips those reps and moves to the next person, which is the version worth using.
When rule-based routing works best
Rules are needed as soon as fit matters. Typical routing attributes are the branch or city nearest the customer, the product or project enquired about, the channel (website, ad campaign, partner, walk-in), the customer’s language, and deal size for B2B.
Rules are evaluated in order, and the first match wins. Put the most specific rules first, such as a named key account or a premium project, and general rules later, such as city-based assignment. Always end with a fallback rule, so no lead is left without an owner.
Worked example: routing for a three-branch business
A company with branches in Pune, Nashik and Mumbai receives enquiries from its website, Google and Meta ads, and walk-ins. It sets up these ordered rules.
- Enquiries for bulk or enterprise orders go to the key accounts team, round-robin among its two managers.
- Walk-ins are assigned to the rep who logged them at that branch.
- Enquiries with a Pune, Nashik or Mumbai PIN code go to that branch team, round-robin among reps who are on shift and below their open-lead limit.
- Everything else goes to a shared inside-sales pool with a 30-minute first-response target and escalation to the sales manager.
The key accounts rule comes first because a bulk enquiry from Pune should not be handled as a routine Pune lead. The pool at the end is the fallback, and the response target stops pooled leads from waiting unseen.
How to measure whether routing is working
- Time to first response, by source and by branch.
- Share of leads that breached the first-response target, and where they were waiting.
- Open leads per rep, to spot overload.
- Conversion from lead to next stage, by source and by rep.
- Number of leads reassigned by hand, which points to missing or wrong rules.
Review these every month. When manual reassignments cluster around one type of lead, add a rule for it rather than relying on a manager to fix it each time.
Common lead routing mistakes
- No fallback rule, so leads that match nothing sit unowned.
- Round-robin that still assigns to reps who are on leave.
- Duplicate enquiries from the same phone number or email routed to different reps.
- Routing on data the form does not collect, such as city, when the form only asks for a phone number.
- Changing rules without recording why, so nobody knows how a lead reached its owner.
How OrbitPi Leads helps
OrbitPi Leads assigns leads with ordered routing rules by branch, channel and purpose, spreads them by round-robin that skips reps on leave, off shift or at capacity, and keeps unassigned leads in shared pools. First-response and stage SLAs warn before a breach.
Explore OrbitPi Leads