Lead Routing

A lead that sits unclaimed for four hours converts at a fraction of the rate of one claimed in five minutes, and lead routing is the machinery that decides which of those two outcomes happens. It's the automated assignment of an inbound lead — a demo request, a content download, a chat transcript — to a rep or queue the moment it lands in the CRM, based on rules the org sets in advance: territory, account size, product interest, round robin. Good routing is invisible. Bad routing is a lead rotting in an unowned queue for three days while two reps are also mid-argument about who owns the account.

How Lead Routing Rules Work

There's no single formula because routing is rule-based, not calculation-based, but the rule types repeat across every RevOps stack: round-robin (leads cycle evenly across a rep pool), weighted round-robin (reps with more open capacity or better win rate get more), account-based (named accounts always route to their assigned owner), territory-based (geography or vertical), and score-threshold routing (only leads above a lead score cutoff get routed to a human at all — the rest go to nurture). The number that actually gets measured is speed-to-lead: the time from lead creation to first assignment, and separately, to first human touch.

Worked Example

A company routes any lead from a 200+ employee company straight to its enterprise AE pool, weighted round-robin by open pipeline. A lead comes in from a 150-employee company but scores 85 out of 100 on intent signals — pricing page visit, three return sessions, competitor comparison download. The scoring rule overrides the headcount rule: it routes to enterprise, not SMB, and lands with whichever enterprise AE currently has the fewest active leads. Assignment happens in 90 seconds. The AE gets a Slack ping and calls in six minutes.

When Sales Teams Use Lead Routing

RevOps owns the rule logic and rebuilds it every time the org adds a segment, launches a product line, or reshuffles territories — routing rot is a real and recurring maintenance cost, not a one-time setup. Sales leadership audits routing when reps complain leads are landing unevenly, which is often the first symptom of a stale rule nobody updated after the last territory redesign. Ops gets pulled in specifically to referee account-conflict disputes, where an existing customer's expansion lead and a net-new lead for the same domain hit two different reps at once.

Common Lead Routing Failure Patterns

Reps game round robin the same way SDRs game meeting counts: claim fast, disqualify faster. A rep who wants a better lead next in the queue will mark a mediocre-but-workable lead as disqualified within minutes, freeing their slot for the next one in — a pattern invisible in aggregate routing metrics because "leads assigned" and "leads worked" look the same from the dashboard. The more damaging failure is structural: nested rule logic that grows one exception at a time until a lead matches no rule cleanly and falls into an unowned default queue — the "black hole" every RevOps team has a name for and no monitoring for, because the whole point of automated routing was that nobody had to watch it. A 400-rule routing tree audited only when someone notices a $200k lead sat untouched for nine days is the median state of lead routing at a company past 50 reps, not the exception.