Key Takeaways
- The five-minute response statistic this category is sold on is not from Harvard Business Review. It traces to a 2007 vendor-funded conference study that gets relabeled across hundreds of buyer guides.
- The genuine HBR audit of 2,241 companies is the stronger number: 23% never responded to a submitted lead at all, and the average first response among those who did took 42 hours.
- HubSpot rotates records by load balance, round robin, or random assignment but has no weighted distribution. Salesforce assignment rules stop at the first match, allow one active rule, and have no native round robin.
- Salesforce reported 130,000 of its own assigned leads went unworked until automated agents swept them, which produced 3,200 opportunities in four months. Those leads all had owners. Routing was never the failure.
- Measure before shopping: timestamp arrival, assignment, first contact, and second touch across 200 leads. If the gap is after first contact, a router will not close it.
Buy a router when leads have an owner problem, not a speed problem
Lead routing software assigns inbound leads to a rep automatically, using rules about territory, account ownership, company size, availability, or round robin order. Chili Piper, LeanData, Default, and RevenueHero sit in this category, and HubSpot and Salesforce both include routing in the CRM you already pay for.
Almost every buyer's guide for this category opens with the same claim: respond within five minutes and you are 21 times more likely to qualify the lead. That number is usually credited to Harvard Business Review. It is not from Harvard Business Review, and the sourcing problem behind it points at the real reason routing projects underdeliver.
Speed is the easy half. A rule that fires in eight seconds and hands the lead to a rep with 40 open opportunities and no context about why this account raised its hand has moved the problem, not solved it. This post covers what the underlying research actually says, what your CRM already does for free, the four signatures that justify a dedicated tool, and the failure routing cannot touch.
The founding statistic of this category is misattributed
The five-minute claim traces to a 2007 study by Dr. James Oldroyd, first presented at a marketing conference and circulated as a PDF by the vendor that funded it. It is not an HBR study. It is not an MIT Sloan Management Review study, despite being labeled one across hundreds of vendor pages. The number gets reprinted because it is convenient, and nobody checks the trail back.
The genuine HBR research is a different paper, and its numbers are better. In The Short Life of Online Sales Leads, Oldroyd, Kristina McElheran, and David Elkington audited 2,241 US companies by submitting a test lead to each one. Only 37% responded within an hour. 24% took more than a day. And 23% never responded at all. Among companies that did respond within 30 days, the average time to first contact was 42 hours. A separate analysis in the same work, covering 1.25 million leads across 42 companies, found firms that made contact within an hour were roughly seven times likelier to qualify the lead than firms that waited an hour longer.
The study is from 2011, and I would not present 15-year-old figures as current benchmarks. Use it for the shape of the problem rather than the precise multiplier. The shape has not changed: a quarter of companies never reply to a hand-raiser, and the median company is measured in days.
That 23% is the number worth sitting with. Those companies did not lose the lead to a slow rule. They lost it because nobody owned the lead and no system noticed. Routing software fixes that specific failure well. It fixes very little else.
Check what your CRM already does before you buy
A meaningful share of routing purchases duplicate a feature the team already pays for and never switched on.
HubSpot handles this through a workflow action that rotates records to owners. Per HubSpot's documentation, it supports load-balanced assignment (the owner with the fewest open records gets the next one), round robin in a rotating order, and random assignment across an eligible pool. You can restrict rotation to users marked available, and records skip anyone set to away. It requires paid Sales Hub or Service Hub seats at Professional or above. What it does not do is weighted distribution, so if you want your strongest closer taking 40% of enterprise inbound while two juniors split the rest, native HubSpot will not express that.
Salesforce works differently. Lead assignment rules evaluate criteria in sort order and stop at the first match, sending the lead to a user or a queue. Only one assignment rule can be active at a time, though a single rule holds up to 3,000 entries. There is no native round robin. Teams get there with a custom auto-number field and a modulo formula, or by dropping into Flow, both of which work and both of which become somebody's undocumented side project.
Run your current setup against your actual routing logic on paper first. If criteria-based assignment plus a round robin covers your logic, you are done. The money is better spent on the follow-up sequence that runs after assignment.
Four signatures that justify a dedicated router
Your matching logic is account-based, not lead-based. A new lead from a company that is already an open opportunity should go to the rep who owns that opportunity, not into the general rotation. Matching a person to an existing account record by fuzzy company name, domain, and subsidiary relationships is the core problem LeanData built its business on, and native CRM rules handle it poorly.
Speed to a live conversation is the actual constraint. If your inbound form converts to a booked meeting and the gap between submission and calendar hold is where you lose people, an instant-scheduling router is the right purchase. Chili Piper's position is built here. The company reports show rates above 90% and attributes it to a reminder cadence at 24 hours, one hour, and one minute before the meeting. Treat those as vendor-reported figures with no disclosed sample size rather than an independent benchmark, but the mechanism is sound and you can rebuild it yourself if you would rather not buy it.
You route on data the CRM does not hold. Routing by headcount band, funding stage, or tech stack means enriching the record before the rule evaluates, in the seconds between form submission and assignment. That is an orchestration problem more than a routing problem, and it usually means a router plus an enrichment step wired together.
Rules change monthly and a non-admin needs to own them. Territory reshuffles, new segments, and people joining and leaving all rewrite routing logic. If every change requires a Salesforce admin ticket, a visual routing tool pays for itself in cycle time alone.
If none of those describe you, native CRM routing is very likely enough. Our CRM automation guide covers building the rules properly inside the system you already run, and the broader B2B marketing automation piece covers where routing sits in the wider stack.
Routing does not fix the handoff
Assignment is a moment. What happens in the 30 days after it is where pipeline is actually won or lost, and no routing tool touches that.
Salesforce's State of Sales report, published February 2026 from a survey of 4,050 sales professionals across 22 countries, includes a candid account from Salesforce's own sales organization. Their EVP of Sales describes leads that used to "fall to the floor like sawdust," and reports that after putting automated agents on untouched leads, those agents contacted 130,000 leads and created 3,200 opportunities in four months.
Read that carefully. Salesforce, a company that sells routing and owns the CRM, had 130,000 assigned leads nobody worked. The routing was fine. Every one of those leads had an owner. The follow-up was the leak.
The same survey found the average seller spends 40% of their time selling, with the rest going to administration and research. A rep at 40% capacity who receives a perfectly routed lead on a Thursday afternoon will get to it when they get to it, and the second touch will not happen at all unless something automatic makes it happen.
When I ran marketing for a firm that made the Inc. 5000 four years running, we could route a demo request to the right rep in under a minute. We still lost deals in the gap between the first call and the third, because nothing chased a non-reply and nobody was accountable for a lead that went quiet on day nine. Routing got the lead to a desk. It did not keep it moving.
The fix is sequencing after assignment: a reminder that fires when a new lead has no logged activity in 24 hours, a reassignment rule when it hits 72, a no-show recovery flow, and a nurture path for anyone who goes quiet. That is sales automation work, and it produces more booked conversations per lead than shaving 30 seconds off assignment ever will.
How to pick, in order
Start by measuring the leak instead of shopping. Pull your last 200 inbound leads and record the timestamp at each stage: arrival, assignment, first human contact, then second touch. Count how many never got that second touch at all.
If assignment is slow, a router fixes it. If assignment is fast but first contact lags by hours, you have a capacity or notification problem, and a router will not help. If first contact is quick and second touch is missing on more than a third of leads, your problem is entirely downstream, and buying a routing tool would be the most expensive way to not solve it.
Once you know which gap you are closing, evaluate on how the tool matches leads to existing accounts, whether non-admins can edit rules safely, what happens when a rep is out or at capacity, and how cleanly it hands off to whatever runs your follow-up. Feature grids will not tell you those things. A trial routing 50 real leads will.
The teams that get value here treat routing as one component wired into everything around it, rather than a product purchased to fix a number on a dashboard. Our AI automation playbook covers the sequencing that runs after assignment, and the AI automation service page explains how we build routing and follow-up as one connected system instead of a stack of tools that each own a fragment of the journey.
