- crm
- lead routing
- sales automation
Lead Routing Is a Rules Problem: Stop Assigning CRM Leads by Hand
Most small sales teams assign new leads by hand, or let reps cherry-pick them. Here's how to automate lead routing in your CRM with simple rules, a fallback, and a timeout, plus the math on what it's worth.
Kamal Farooqi5 min read
The Quiet Gap Between "Lead Created" and "Lead Owned"
A new lead lands in your CRM. Someone has to decide who calls them. In many small teams that someone is a sales manager who checks the lead list when they get a minute, or it's a free-for-all where reps grab whatever looks good.
Both approaches leak money. The manager is busy, so leads sit. The free-for-all means the best-looking leads go to the fastest clickers, and the rest go to nobody.
This isn't a hard problem for software. Lead routing is a pure rules problem: if X, assign to Y. It's one of the cheapest CRM automations to build and one of the easiest to justify.
What Unrouted Leads Cost: A Worked Example
Here's a hypothetical 5-rep team. The numbers are illustrative, so swap in your own.
- 200 new leads a month
- Average deal value: $2,000
- Normal close rate when a lead is contacted within an hour: 10%
- Close rate when a lead sits for a day or more: 5%
- Share of leads that sit that long under manual assignment: 15%
That's 30 leads a month sitting. At 5% instead of 10%, you lose 1.5 deals a month. Roughly $3,000 in monthly revenue, or $36,000 a year, from nothing more than assignment delay.
Add the manager's time. If they spend 15 minutes a day sorting and assigning leads, that's about 5 hours a month. Small, but it's a senior person doing clerical work.
Building routing rules in HubSpot, Zoho, or Salesforce is typically a day or two of work including testing. Even if the real loss is a third of the figure above, payback comes quickly.
Four Routing Methods and When Each Fits
| Method | How it works | Best for | Watch out for |
|---|---|---|---|
| Round-robin | Leads rotate evenly through reps | Similar leads, similar reps | Ignores who is on leave or overloaded |
| Territory-based | Assign by region, postcode, or country | Field sales, local services, real estate | Gaps where no territory matches |
| Attribute-based | Assign by deal size, industry, product interest | Teams with specialists | Rules multiply and become hard to maintain |
| Capacity-weighted | Assign to the rep with the fewest open leads | Uneven workloads | Needs reliable data on open leads |
Most small teams should start with round-robin plus one or two attribute rules. For example: enterprise-size companies go to your senior rep, everything else rotates. You can add complexity later. Starting with five layered rules usually means nobody can explain why a lead went where it did.
The Three Pieces Most Setups Skip
The basic assignment rule is the easy part. These three additions are what make it hold up in real use.
1. A fallback owner
Every lead that matches no rule needs somewhere to go. Pick a named person or a shared queue that someone checks daily. Without a fallback, odd leads get created with no owner and disappear. This is the most common failure in routing setups.
2. A timeout and reassignment
Assigning a lead isn't the same as someone working it. Add a rule: if the owner hasn't logged a call, email, or task within, say, 2 hours during business hours, notify them. If it's still untouched at 4 hours, reassign it to the next rep and alert the manager.
This turns routing from a one-time decision into a safety net. It also removes the awkward conversation about who is sitting on leads, because the system handles it consistently.
3. Availability awareness
A lead routed to someone on holiday is a lead routed to nobody. Add an "available for leads" field on each user record, and have the routing rule skip anyone marked unavailable. Reps update one checkbox, or you sync it from a shared calendar. It's a small field that prevents a lot of embarrassing delays.
Keep the Rules Visible
Reps trust routing when they can see how it works. Write the rules in plain language on one page: "Leads from the website form rotate between Sam, Priya, and Joe. Leads over 50 employees go to Dana. Anything unmatched goes to the shared queue."
Also log the reason for each assignment in a CRM field, such as "round-robin" or "territory: North". When a rep asks why they got a lead, or why they didn't, you have an answer in ten seconds rather than a debate.
Things to Check Before You Switch It On
- Clean the input data. Territory and size rules only work if the form fields and enrichment data are filled in consistently. A free-text "State" field will break a territory rule.
- Test with dummy leads. Create 10 test records covering every rule, plus a few that match nothing, and confirm each lands where you expect.
- Handle duplicates first. If an existing contact submits a new form, they should go to their current owner, not get re-rotated to someone else. Add a check for an existing owner before the round-robin step.
- Review monthly. Look at leads per rep, time to first contact, and reassignment counts. If one rep keeps triggering timeouts, that's a coaching conversation or a capacity issue, and now you have data on it.
Start Smaller Than You Think
You don't need a routing engine. You need a rotation, a fallback owner, and a timeout. That covers the vast majority of the value, and it can be live in a couple of days. Once you can see time-to-first-contact improving, you'll know which extra rules are worth adding.
If you're not sure how your leads are currently being assigned, or how many are sitting untouched, that's a good thing to find out. Book a free call and we'll look at your CRM setup together and work out whether routing is where your leaks are.