What a routing rule is actually deciding
A lead routing rule is the piece of logic that decides, the moment a form fill, chat request or demo booking hits the CRM, which rep owns it. Every CRM and sales engagement platform ships some version of this: a queue, a set of conditions, and an assignment action. The output looks simple. The mechanics underneath it determine whether a hot prospect reaches a rep in minutes or sits untouched for a day.
Routing is separate from lead scoring, which decides whether a lead is worth working at all. Routing assumes the lead already qualifies and asks a narrower question: out of the reps eligible to take it, who takes it right now.
Why the rule exists
Before routing software, most teams assigned leads by hand or by a spreadsheet-based rotation. That broke down the moment volume grew past a few reps, because nobody was watching the queue at 11pm when a form came in from a different time zone.
The urgency is not folklore. The most-cited study in this space, a 2007 audit of over 15,000 leads and 100,000 dials across six companies conducted with MIT's Sloan School of Management, found that contacting a lead within five minutes made it 100 times more likely to result in contact and 21 times more likely to result in a qualified conversation than contacting it after thirty minutes (MIT/InsideSales.com, 2007, Lead Response Management Study, foundational). A 2011 Harvard Business Review audit of 2,241 US companies found firms that responded within an hour were roughly seven times more likely to qualify the lead than those responding within twenty-four hours (Oldroyd, McElheran and Elkington, Harvard Business Review, 2011). A more recent operational study of 1,000 B2B sales teams found the average response time across companies that responded at all was over 29 hours, and 63% of the companies tested did not respond to a test inbound lead at all (RevenueHero, 2024, vendor study; the finding is directionally consistent with the earlier HBR and MIT figures). Routing rules exist to close that gap without relying on a human to notice the lead arrived.
The three routing models teams actually run
Round robin. Leads rotate through a pool of reps in sequence, one after another. It is simple to configure and fair in the sense that everyone gets an equal share of volume. It has no concept of account history, so the same company can land with a different rep every time someone from that account fills out a form.
Weighted round robin. Same rotation logic, but reps get a different share based on capacity, tenure, quota attainment or territory assignment. A newer rep on a ramp plan might get a lighter allocation than a rep who is fully ramped. This fixes the fairness problem round robin creates when reps are not interchangeable, but it adds a maintenance burden: the weights have to be reviewed and adjusted as headcount and ramp status change, or the routing quietly drifts out of alignment with actual capacity.
Account-based routing. Before a lead is assigned to a rep, it is matched against existing account records so it lands with whoever already owns that account, not whoever is next in a rotation. This depends on lead-to-account matching working correctly upstream, since a mismatched domain, a personal email address, or a company name typed three different ways across three forms can all break the match and send the lead to a fallback queue instead of the account owner.
Most B2B teams running more than a few reps end up with a hybrid: account-based rules apply first for named accounts and existing pipeline, and whatever is left falls through to round robin or weighted round robin as the default.
What breaks in practice
The failure mode is rarely the routing logic itself. It is almost always the data feeding it.
A routing rule that checks industry, employee count or territory fails silently when that field is blank on the incoming lead. It does not throw an error. The lead just does not match any rule and drops into a catch-all queue, where it can sit until someone happens to check it. Account-based routing has the same weak point one level up: if the lead cannot be matched to the right account record because of a formatting mismatch, it gets treated as new business and handed to whichever rep is next in line, even if another rep has been working that account for months.
The second common failure is no enforcement after assignment. A rule that hands a lead to a rep is not the same as a rule that guarantees the rep works it. Teams that pair routing with a service-level timer, one that automatically reassigns a lead if it sits untouched past a set window, close that gap. Teams that rely on the rep noticing a new record in their queue do not, and the response-time numbers above are largely a record of that gap.
What to check before choosing a routing setup
- Whether the tool supports a hybrid model (account-based first, round robin as fallback) rather than forcing a single method across the whole funnel
- Whether there is a visible fallback queue, and whether someone actually monitors it
- Whether reassignment on a missed service-level window is automatic or depends on a rep or manager noticing
- Whether lead-to-account matching runs on a normalized field (verified domain) rather than a raw text field that a form can populate inconsistently
- Whether weighting for capacity or tenure is reviewed on a set schedule or left to run on configuration set once and forgotten
None of this is exotic. It is closer to plumbing than strategy. But it is the plumbing that decides whether the sales team's first move on a real prospect happens in minutes or in the following afternoon.