.DkNUKaKx_ZLAT4m.webp?dpl=dpl_QxVchpYCYDqXdTvfbjVFxPBn4krt){kind=small}
Routing is the step that turns a record into someone’s responsibility. Everything before it prepares the lead. Routing decides who picks up the phone.
It is also the step that goes stale fastest, because it encodes the org chart, and the org chart changes constantly. Territories get redrawn, reps leave, segments get resliced, a region gets its own team. Each change should update the routing rules. Most of them do not.
What is lead routing automation?
Lead routing automation assigns each incoming lead to the right owner based on rules — territory, company size, product interest, account ownership, or a round robin within a team — without anyone triaging a queue by hand.
Good routing is invisible. The lead appears in the right person’s queue fast enough to act on, and nobody thinks about the mechanism.
Why routing rules go stale
Reps leave and the rules do not know. A rule names an individual, that person moves on, and leads keep routing to an inactive user. They land nowhere and nobody is waiting for them.
Territories change and the rules keep the old boundaries. A region splits into two, the new owner takes over on paper, and the routing logic still sends by the old postal-code ranges.
Nobody owns the default. Every routing setup has a catch-all for leads matching no rule, and over time that queue collects everything the rules did not anticipate. Because nothing routes out of it, nobody watches it, and it grows.
Rules accumulate and start contradicting. One says enterprise leads go to the enterprise team. Another says anyone from a target account goes to that account’s owner. A lead is both, and whichever rule evaluates first wins — which may not be the intended answer.
The pattern across all four is that routing depends on facts about your organization that live outside the routing system and change without telling it.
What stale routing costs
Speed, mostly, and speed is measurable.
The gap between a routing setup that works and one that does not is wide enough to see. Kevin Cassidy, Director of Marketing Operations at DocuSign, described the change after the company rebuilt how leads reached sales: from 90% of leads reaching the sales team in under ten minutes to 99% of our leads to the sales team in under 3 minutes.
The second cost is trust. When a rep receives leads that are wrong for them often enough — wrong territory, wrong size, already a customer — they stop treating the queue as a source of real work. Once that happens, fixing the routing rules does not immediately fix the behavior.
Built-in features, point tools, or build it
Three ways to route, and the calculation between them has changed.
| What it costs | Where it stops | |
|---|---|---|
| CRM built-in assignment | Nothing — already there | Limited to fields the CRM holds. Fine for territory and company size, insufficient the moment routing depends on product usage or intent data. |
| A dedicated routing tool | Distribution Engine lists at $45 per user per month, five-user minimum — $27,000 a year for 50 reps1 | Defensible in isolation, harder when every other lifecycle stage has its own contract. |
| Build it | An afternoon with a coding assistant | Nothing, at first. The rules are the easy part. |
The build option is where most teams are heading, and it is worth being clear about which part is hard. Writing the rules is not hard. What is hard is everything that keeps the rules correct six months later: knowing when a rep goes inactive, seeing what landed in the default queue, being able to change a territory without reading someone else’s code, and having any record of where a given lead actually went when someone asks.
What routing depends on
Routing consumes the output of every stage before it, which is why routing problems are so often not routing problems.
Territory usually derives from a field enrichment populated. Account-owner routing depends on matching having resolved the lead correctly. Priority depends on scoring. And whether any of it can be measured depends on CRM data hygiene.
When leads are reaching the wrong reps, the routing rules are worth checking second. The fields they read are worth checking first. Lead lifecycle management covers how each step feeds the next, and lead routing, end to end covers every stage, the systems it runs on and a build guide for each.
Which of your automations breaks first? Take the assessment — it ranks what your team already runs by who can change it, how you would find out it stopped, how many systems it touches, and what a break costs.
Sources
- G2 pricing, Distribution Engine, 2026. List price, not paid price.