Lead routing is where marketing spend either becomes pipeline or dies quietly. A lead that sits unassigned for four hours converts at a fraction of the rate of one touched in five minutes. Yet most orgs treat routing as an afterthought - a single assignment rule written years ago that nobody fully understands anymore. Here is how to think about routing as an architecture, not a rule.
The Three Core Models
Round robin is the simplest: leads are distributed evenly across a queue of reps. It is fair, easy to explain, and trivial to implement. It breaks the moment your reps are not interchangeable - when some carry enterprise deals and others handle SMB, when time zones matter, or when a lead belongs to an account someone already owns. Round robin also silently punishes your best reps: distribute leads evenly and you have optimized for fairness to reps, not for revenue.
Territory-based routing assigns leads by geography, industry, company size, or a combination. This aligns routing with how your sales org is actually structured. The failure mode is territory drift: the org chart changes quarterly but the routing rules change annually. Every reorg leaves behind orphaned rules routing leads to reps who changed roles six months ago. If you run territory routing, the routing logic needs an owner and a review cadence tied to sales planning cycles, or it rots.
Account matching (lead-to-account) is the model most B2B orgs should run and many do not. Before any assignment logic fires, check whether the lead belongs to an account you already know - an open opportunity, a customer, a named target account. If it does, route it to the account owner regardless of what round robin or territory rules say. Nothing burns trust with sales faster than an SDR cold-calling a contact at an account their teammate is actively closing.
The Architecture That Actually Works
Mature routing is a waterfall, evaluated in strict order:
1. Deduplication -> Is this an existing lead or contact? Merge, don't create.
2. Account match -> Does this belong to a known account? Route to owner.
3. Disqualification -> Competitor, student, spam? Route out of sales entirely.
4. Segmentation -> Enterprise / mid-market / SMB by firmographics.
5. Territory -> Geography or vertical within the segment.
6. Round robin -> Final tiebreaker within the matched territory group.
7. Escalation -> No touch in X minutes? Reassign and notify a manager.Round robin is the last step, not the first. It is the tiebreaker after every intelligent decision has been made, not the strategy itself.
The Details That Separate Good From Broken
Working hours and capacity. A rep on vacation should exit the queue automatically, not accumulate a backlog of dead leads. Integrate routing with calendar or out-of-office status, and cap leads-per-rep-per-day so a demand spike does not bury one person.
Speed-to-lead SLAs with teeth. Routing without escalation is a suggestion. If a lead is untouched for 15 minutes, it should re-route and someone should be notified. The SLA needs to be measured from form-fill timestamp, not from assignment timestamp - the gap between those two numbers is where routing latency hides.
Auditability. When a rep asks "why did I get this lead?" - and they will ask weekly - you need an answer better than "the rules." Log which rule fired on every assignment. In Salesforce, a simple custom field stamped with the routing reason turns every debugging session from an hour into a minute.
The Metric That Tells You If It Is Working
Most teams measure routing by distribution fairness. The better metric is time-to-first-touch by segment, because it captures the whole system: dedup speed, assignment accuracy, rep responsiveness, and escalation. If your enterprise leads have a slower first touch than your SMB leads, your routing is optimized backward - and no amount of round robin fairness will fix that.
Routing is one of the highest-leverage systems in GTM because it multiplies everything upstream of it. Marketing can double lead volume, but if routing loses 20 percent of leads to bad rules and slow escalation, you paid twice for the same pipeline.