Lead routing is the rule that decides who owns an enquiry the moment it arrives. It sounds like a small piece of plumbing and it is usually the difference between a lead answered in four minutes and one answered tomorrow.
Teams reach for routing software when the manual version breaks. Before buying anything it is worth being clear about which routing rule you actually need, because the rule is the hard part and most of the cost sits in getting it wrong.
The four rules, and when each one fits
Round robin. Leads go to each rep in turn. Fair, simple, and the right answer when your reps are genuinely interchangeable. It fails the moment they are not, because the enquiry that needed your enterprise specialist went to whoever was next in line.
By territory or segment. Region, industry, company size, product line. This is what most teams actually want. It needs the data on the lead to be present and clean at the moment of arrival, which is where it usually breaks: a form that does not ask for company size cannot route on company size.
By capacity. The rep with the fewest open leads gets the next one. Better than round robin when deal cycles vary a lot, because it stops a rep who is buried from being handed five more.
By ownership. If the account already exists, the lead goes to whoever owns it. This should sit above every other rule, and it is the one most often missing. Nothing damages a relationship faster than a second rep cold-calling an existing customer about something their account manager already knows.
Most working setups are a short chain: existing owner first, then segment, then round robin inside the segment as a fallback.
The parts that quietly fail
Routing is easy to build and easy to build badly. Four failure modes account for most of the pain.
No fallback. The rule matches nothing, so the lead sits unassigned. Nobody notices because it is not in anyone's queue, which is exactly why nobody notices. Every routing chain needs a final rule that catches everything, and somebody needs to own that bucket.
Routing on data that is not there yet. Enrichment that takes thirty seconds and routing that runs on submit means half your leads route on a blank field. Either wait for enrichment or route on what the form actually captured.
No timer. A lead is assigned correctly and the owner is on leave. Without an escalation that fires after a set period, it sits with a named owner, which looks fine on every report and is worse than being unassigned, because now it is invisible.
Nobody owns the rule. Territories change, reps leave, products get added, and the routing rule is in a system nobody has opened in a year. Then leads quietly go to a person who left in March.
When routing software is worth it, and when it is not
Dedicated routing tools exist and are priced accordingly. The honest split:
Buy when you have complex territory logic that changes often, a large team where fairness disputes are real, or a need for routing analytics that your CRM genuinely cannot produce. At that scale the subscription is cheap against the admin it removes.
Do not buy when the real problem is that your form does not capture the field you want to route on, or that there is no fallback rule, or that nobody escalates stale leads. A routing platform layered over those problems adds a monthly cost and routes the same leads to the same silence.
The test: write your routing rule out in plain sentences. If it fits in five lines, your CRM and a small amount of automation will do it, and you will spend less time configuring a platform than you would writing the rules into one.
Build it where the data already is
The version that holds up over time runs inside the systems the business already uses, for one reason: it stays close to the data that drives it.
The shape is usually the same. The form or inbound channel writes into the CRM on submit. A small automation reads the record, checks for an existing account owner, then applies the segment rules, then falls back to round robin. It writes the owner and a timestamp. A second automation checks at intervals for records assigned but untouched past your window, and escalates.
That is a handful of steps. The thinking is in the rule chain, not the technology, and the whole thing can live in n8n, your CRM's own automation, or a mix, depending on what you already run.
The advantage of building it where your data is, rather than renting a layer above it, is that it keeps working when you change CRM plan, and there is nothing to migrate or cancel later. That is the approach Regna Operations takes: built in your own accounts, documented, handed over, no subscription attached.
Before you build, check the rule is worth it
Routing only pays off if leads are actually being lost or misdirected. Two checks that take an afternoon:
Pull last quarter's leads and count how many were assigned to someone other than the person who should have had them, and how many were never contacted at all. If the second number is large, your problem is escalation rather than routing.
Then check how many arrived outside working hours. If most of your delay is overnight, routing will not fix it and an acknowledgment with a booking link will.
If the numbers say the problem is real, the Revenue Roadmap scores it against everything else on the list and puts a fixed price on building it, so the decision is made on value against effort rather than on which vendor called first.
Common questions
What is lead routing?
The rule that assigns an incoming enquiry to an owner automatically. Good routing covers existing account ownership first, then segment or territory, with a round robin fallback and an escalation timer for leads nobody touches.
Is round robin lead assignment a good idea?
It is fine when reps are genuinely interchangeable and a poor fit when they are not. Most teams want segment-based routing with round robin only as the fallback inside a segment.
Do we need lead routing software or can our CRM do it?
If your routing rule fits in about five plain sentences, your CRM plus a little automation will handle it. Dedicated software earns its cost with complex territories that change often, large teams, or routing analytics your CRM cannot produce.
What happens to leads that match no rule?
In most setups, nothing, which is the single most common routing failure. Every chain needs a final catch-all rule and a named person who owns that bucket, or those leads stay invisible because they are in nobody's queue.
