Lead Routing: Who Answers When the Call Comes In?

Everyone sells you the timing problem. Respond faster. Beat the clock. Almost nobody sells you the reason the clock runs out, which is that when a lead lands, no single human is on the hook for it. A form fill drops into an inbox three people can see, all three assume one of the others has it, and ninety minutes later the homeowner has already booked your competitor.

That is a routing failure wearing a timing costume. Fix routing and the response time fixes itself. This is the routing half of the problem — the timing half lives in our speed-to-lead playbook.

Who owns a lead the moment it lands?

Exactly one named human, assigned automatically within 60 seconds of submission, with a timestamp recorded on the record. Not a team. Not an inbox. Not 'whoever sees it first' as an unwritten understanding. A person, a time, a record.

Ownership is the only thing that makes a service-level agreement enforceable. If you cannot answer 'who had this lead at 2:14pm and what did they do about it' in under 30 seconds, you do not have a routing system — you have a hope. Every model below is just a different rule for picking that one name.

• Owner: one named person, not a team alias and not a role
• Assigned at: the timestamp the lead was routed to them
• First touch at: the timestamp of the first outbound call, text, or email
• Escalated at: the timestamp it was taken off them and given to someone else

Those four fields are the entire audit trail. If your CRM records them, you can measure routing. If it does not, you are guessing.

Why does a shared inbox guarantee a slow response?

Because a lead visible to three people is owned by zero people, and the cost of that is measured in multiples, not percentage points. Harvard Business Review's 2011 article 'The Short Life of Online Sales Leads' audited 2,241 US companies with a web-generated test lead: 23% never responded at all, and among those that did respond within 30 days, the average response time was 42 hours. A separate study reported in the same article — 1.25 million leads received by 29 B2C and 13 B2B US companies — found that firms contacting a lead within an hour of the query were nearly seven times as likely to qualify it, meaning a real conversation with a key decision maker, as firms that waited just one hour longer, and more than 60 times as likely as firms that waited 24 hours or longer.

Note the number: one hour. Not five minutes. The '5-minute rule' everyone quotes traces back to a study whose original source no longer exists at a citable URL, and it gets falsely pinned on HBR. One hour is the defensible threshold. Being faster than an hour is still better — you just cannot cite a number for it.

The shared inbox fails for a boring psychological reason. Diffusion of responsibility is real, and it scales with headcount: two people on the inbox is a coin flip, five people is a guarantee that the lead sits. Adding staff to a shared inbox makes response time worse, not better.

Which of the four routing models fits your business?

There are only four, and the right one is decided by how many people can genuinely close, not by how sophisticated you want to look. Here is the honest matrix.

The verdict, if you want one: round robin with an availability check wins for most teams of three or more, and single owner wins under three. First-to-claim is the best model on paper and the worst in practice, because it only works if you actively police cherry-picking — and nobody does. Skill-based routing earns its complexity only when the wrong person calling back is genuinely damaging: a family-law lead routed to a personal-injury attorney, or a commercial HVAC job routed to a residential tech.

The tool matters less than the rule. If you are choosing a system to hold the rule, our CRM comparison for service businesses covers what each one actually does at each tier.

How do you route leads when you have no sales team, just a dispatcher?

You route to the dispatcher as the single owner, and you give the dispatcher a hard 10-minute rule and one escalation target. That is the whole system for a two-truck shop, and it beats a paid CRM tier with a broken workflow every day of the week.

Most service businesses do not have SDRs, territories, or a revenue-operations hire. The entire enterprise routing category — the tools that dominate every search result for this topic — is built for B2B software companies with 12 reps and a territory map. You are not that. Your routing stack is a form, a text message, and one person who is accountable.

• Form submits to the CRM (or a spreadsheet, honestly) and fires an SMS with the name, phone number, and requested service
• The SMS goes to one phone, not a group thread — group threads are shared inboxes with extra steps
• The dispatcher calls back and logs first touch; if it goes to voicemail, they text immediately, because a text gets read
• If the dispatcher does not log first touch in 10 minutes, the alert re-fires to the owner

One caveat worth knowing before you buy: in HubSpot, the 'Rotate record to owner' workflow action that gives you true round robin is documented as Sales Hub and Service Hub Professional and Enterprise only, and it is 'only compatible with activated, paid users.' Round robin is a paid-tier feature almost everywhere. If you have two closers, do not buy a tier to get it — you do not need it.

What should happen when the first assignee does not respond in 10 minutes?

The lead gets taken away from them and given to someone else, automatically, and the clock keeps running. This single rule is the difference between a routing system and a routing diagram. Without escalation, all four models fail identically: the lead is assigned, the assignee is on a job site, and the lead sits with a name on it — which is arguably worse than the shared inbox, because now everyone else thinks it is handled.

A three-rung ladder is enough. Keep the intervals short and the final rung human.

Two rules make the ladder work. First, escalation is triggered by a logged first touch, not by someone opening the record — an opened email is not a phone call. Second, reassignment is silent to the prospect and loud internally. Nobody outside the business ever learns that the lead bounced.

After the first touch, routing hands off to cadence — how many attempts, on which channels, over how many days. That is a separate discipline, covered in lead follow-up cadence.

How do you route by service area or practice area without a CRM build?

One required dropdown on the form, and one branching rule on the alert. That is it — no data enrichment, no territory map, no six-week implementation. The form field does the routing work that enterprise tools do with a rules engine.

For geography: a required ZIP code field, and a rule that sends ZIPs in list A to Tech A's phone and list B to Tech B's. Build the lists once from your actual service map. For practice or service type: a required 'what do you need' dropdown with five to seven options — not free text — and route each option to the person who handles it.

Then add the rule everyone forgets: a default bucket for anything that matches no rule. Out-of-area ZIP codes, blank fields, an option you removed from the dropdown last year. Unroutable leads are the leads that vanish, and they are usually the ones from a page you paid to rank. If your form is not capturing the one field your routing depends on, that is a conversion-focused website problem before it is a CRM problem.

How do you audit your routing in one afternoon?

Pull your last 30 inbound leads, put four columns next to them, and fill in the timestamps by hand. Two hours of work, and it tells you more than any dashboard you will buy this year.

• Column 1: submitted at — from the form notification, not from memory
• Column 2: assigned at — and to whom, by name; write 'nobody' where that is the truth
• Column 3: first touch at — the first real outbound attempt, not an email being opened
• Column 4: outcome — contacted, voicemail only, or never touched

Then read three numbers. Your median assignment lag tells you whether routing exists at all. Your median first-touch lag tells you whether the assigned person is actually reachable. And the count of leads with 'nobody' in column 2 is the number you already paid for and threw away.

The pattern is almost always the same: the leads that convert were assigned fast and touched fast, and the dead ones sat unowned. That is not a sales-talent problem. It is a rule you have not written down yet. Anyone selling you a routing tool before you have run this audit is selling you a tool for a problem you have not measured.

If the audit shows leads dying between the form and the phone, that is a fixable, cheap, one-week problem — and it is the first thing we look at before touching rankings or ad spend, because more traffic into a broken routing system just makes the leak bigger. Get my free audit and we will tell you where your leads are going, honestly, whether or not you hire us.