Blog/Sales & RevOps

Lead Routing Rules That Assign Every Inbound Lead to the Right Rep

Design lead routing rules by segment, territory and capacity so no lead sits unowned and the right rep gets it first time.

By Sagar Makker · 6 min read · October 2026
Work Business
In short
Write routing as an ordered rule table: account match, segment, region, product, then round robin.
Always have a fallback owner and a reassignment rule when a lead is not touched in time.
Review misrouted and unowned leads every week and fix the rule, not just the lead.
The problem

This is for RevOps managers, sales heads and marketing leaders whose inbound leads end up with the wrong rep, two reps, or nobody. Misrouted leads waste the effort spent generating them and create internal disputes over credit. This post shows how to write routing as an ordered rule table, handle existing accounts and partners, balance by capacity, and set fallbacks and reassignment windows so every lead has exactly one clear owner.

A manufacturing company in Pune fills in a demo form. The lead lands with a rep in the SMB team because the form had no company size field, even though the account is already owned by an enterprise rep who is mid-way through a renewal. Two reps call the same buyer in one afternoon, and the buyer wonders whether anyone at your company talks to each other.

Elsewhere, leads arriving on a weekend sit in a general queue until Tuesday, and a rep on leave keeps receiving round robin assignments. Reps start cherry-picking leads from shared views, managers spend time arbitrating ownership disputes, and marketing cannot see which leads were actually worked. The routing logic has grown through ad hoc fixes and nobody can explain it fully.

Why it happens
01No check for existing accounts or open opportunities before a new lead is assigned
02Forms do not capture the fields that routing depends on, such as company size or state
03Round robin ignores leave, capacity and current workload
04No fallback owner or reassignment rule when a lead goes untouched
05Routing logic is scattered across form tools, CRM workflows and manual reassignments
How to fix it
1
Write an ordered routing table
The RevOps lead writes routing as rules evaluated top to bottom: existing account owner, partner-sourced leads, named strategic accounts, segment and region, product line, then round robin. Each rule names its owner. The sales head approves the order.
2
Match before you assign
The CRM administrator adds matching on company domain, GST number where captured, and company name so new leads attach to existing accounts and owners first. Unmatched personal email domains go to a review queue rather than straight to round robin.
3
Capture routing fields at source
Marketing adds the fields routing needs, such as company size band, state and product interest, to every form and chat flow. Where buyers skip a field, enrichment or a short SDR qualification call fills it before assignment.
4
Balance by capacity and availability
Sales managers maintain each rep's availability and a maximum number of open new leads. The round robin skips reps on leave or at capacity, so leads go to someone who can respond within the window you define.
5
Set fallbacks and reassignment
RevOps defines a fallback owner per segment and a reassignment window, for example four business hours untouched. Untouched leads move automatically to the next rep, and the manager gets a notice listing what moved and why.
Worked example
A B2B software team ends ownership disputes

A B2B software company selling to Indian mid-market manufacturers had leads routed by a mix of form rules and manual reassignment. Existing customers often reached new-business reps, and weekend leads waited days. The RevOps manager wrote a single ordered routing table, added domain and company matching before assignment, and set a fallback owner with a reassignment window. Reps on leave were removed from the rotation automatically. Within a few weeks, ownership disputes in the sales channel largely stopped, account managers saw expansion enquiries promptly, and marketing could report on which leads were contacted and by whom.

Common mistakes
×
Round robin before account matching
Assigning leads before checking existing accounts creates duplicate outreach and credit disputes. Always match against accounts and open opportunities first, and route to the current owner when a match exists.
×
No owner for unmatched edge cases
Leads with personal emails or missing fields fall through the gaps. Send them to a named review queue with an owner and a response window instead of leaving them in a general pool.
×
Fixing leads instead of rules
Manually reassigning misrouted leads hides the cause. Log each misroute with a reason, review the log weekly, and change the rule so the same mistake does not repeat.
Where an AI agent helps
Input
New leads from forms, chat, WhatsApp and email, plus CRM accounts and rep availability
Agent does
Matches leads to accounts, applies the routing table and flags leads untouched past the window
Human gate
Sales manager approves reassignments of strategic or partner-sourced leads
Outcome
Assigned lead with routing reason logged, plus a daily misroute report
Checklist
Write routing as one ordered rule table
Match new leads to existing accounts first
Add routing fields to every form and chat flow
Remove reps on leave from round robin automatically
Set a fallback owner and reassignment window
Review misrouted leads every week
What to measure
Share of leads routed without manual change
Leads untouched past the reassignment window
Duplicate contacts on the same account
Median time from lead to first owner action
Questions
Is round robin the best way to distribute leads?

Round robin is a good last step, not the whole system. Route existing accounts, partners and named accounts first, then segment and region. Use weighted round robin within each group, adjusted for leave and capacity.

How do we handle leads from existing customers?

Match on company domain and name before assignment and route to the account owner or account manager. If the enquiry is for a different product line, notify both owners and let the sales manager decide who leads.

What should the reassignment window be?

Set it based on how quickly your buyers expect a response and your team's working hours. Many B2B teams choose a few business hours for demo requests and a longer window for content downloads. Review it once you see real data.

Who should own lead routing logic?

RevOps should own the routing table and its changes, with the sales head approving priority order and marketing confirming the form fields. Keep the logic in one system where possible, so changes are visible and testable.

Keep reading
All posts →
Business WorkingSales & RevOps
Speed-to-lead: build a process that responds to leads in minutes
4 min readRead →
Business MeetingSales & RevOps
Sales Territory Design: Build Fair, Balanced Territories for Your Reps
7 min readRead →
Business WorkingSales & RevOps
Deal Stage Definitions: Write Exit Criteria Your Whole Team Uses
6 min readRead →
Next step

Want this fixed in your business?

Send the workflow. You get a scope and a fixed price within two working days — or a straight answer that it isn't a fit.

Secure by default · find → fix → verify · authorised scope only
Send a brief →enquiry@xdqlabs.com