Lead routing without a person in the middle: AI on acquisition

Why does speed matter this much?

The strongest evidence on lead response is nearly twenty years old and nobody has replaced it. In a study of more than 15,000 leads and 100,000 call attempts across six companies over three years, the odds of making contact fell by 100 times between a five-minute response and a thirty-minute one, and the odds of qualifying the lead fell by 21 times. Within the first hour, contact odds dropped more than tenfold. After twenty hours, further dials actively reduced the chance of a qualified conversation (Lead Response Management Study, James Oldroyd, MIT Sloan, with InsideSales.com, 2007).

Read those as odds ratios from phone-based selling in 2007, not as a forecast for your conversion rate. The direction and the size of the effect are what matter, and in my experience the direction has held through every channel since.

What that means practically: the gap between a good funnel and a bad one is often not the ads. It is the fourteen hours a form fill spends in an inbox. And the fix is a week of plumbing rather than a quarter of hiring, which makes it the cheapest work in the stage.

Step 1: set the clock before you build anything

Two numbers, written down and agreed with whoever does the calling.

Routed to a named owner in under 60 seconds. First human contact in under 5 minutes during working hours.

What goes wrong: the SLA is set on routing only, so the automation hits its number, nobody calls for a day, and the dashboard says the system works. Measure the human leg too, as the median and the 90th percentile, because the median hides the leads that waited.

Step 2: capture once, in one shape

One form schema across every page, with the hidden fields already discussed: UTMs, click IDs, the first-visit page and timestamp, the page the form sat on, and one open question in the person's own words. Every entry point writes to the same object with the same field names.

What goes wrong: four forms built by three people over two years, with different field names, so the routing rules have to branch and every new campaign breaks one branch. Consolidate the forms before you automate anything downstream.

Step 3: dedupe before you do anything else

Check the email domain and the company name against existing records first. A lead from a company that is already a customer, already in an open deal, or already owned by someone goes straight to that owner and skips scoring entirely.

What goes wrong: this step is put last, so an existing customer gets a cold outreach email from an SDR who has never heard of them. It is the single most visible failure of an automated funnel and it costs trust inside the company faster than it costs revenue.

Step 4: enrich, but never let enrichment block the route

Enrichment adds what the form did not ask: company size, industry, funding, the technologies on their site. Tools like Clay do this well. The rule is that enrichment runs on a timer, and if it has not returned in a few seconds, the lead routes anyway with whatever you have.

What goes wrong: a synchronous enrichment call sits in the path, the provider has a slow afternoon, and the 60-second SLA becomes nine minutes without anybody noticing until a month later. Make the route the primary path and enrichment a decoration that arrives when it arrives.

Step 5: score, and write the reason next to the score

The score is the four fields from your definition of qualified, applied automatically where they can be: fit from enrichment and the email domain, timing and need from the person's own answers. This is where a language model earns its place, because the useful parts of a lead are free text.

What AI does well here, today:

• Classify the open answer. The sentence a person wrote about their problem, mapped to one of your known problem categories, with the original sentence kept.

• Summarize the company. Two lines from their website about what they sell and to whom, which saves the person taking the call five minutes and makes the first question better.

• Match to an existing account. Fuzzy name matching that a rule cannot do: the same company under a trading name, a subsidiary, a misspelling.

• Draft the first reply for a human to read and send, using the person's own words back to them.

What it must not do: disqualify a lead on its own. Route low scores to a slower lane, a nurture sequence, or a weekly human review, and never to a bin. Every automated decision writes its reason as text on the record, so that any person can see why a lead was scored as it was. A score without a reason gets ignored within a month, because the first time it is wrong nobody can tell why.

What goes wrong: a scoring model built on nothing, assigning points by intuition, calibrated against no outcome. Until you have a few dozen closed-won deals to learn from, keep the scoring to the four checkable fields and let the humans do the judging.

Step 6: route to a person who is available

Round robin inside the right segment, filtered by who is actually working. Honor working hours, time zones and out-of-office, and set a fallback owner for every segment.

Outside hours, do two things immediately: send the lead a short acknowledgment that says when they will hear from a person, with a link to book a time if they would rather choose, and put the lead at the top of the next working session's queue, flagged with how long it has waited.

What goes wrong: routing by territory to someone on two weeks of leave, with no reassignment rule. Add a rule that a lead with no human contact after the SLA passes reroutes to the fallback owner, and that the reroute is visible.

Step 7: notify where the person already is

The notification goes to the channel they have open, usually a chat tool, and carries the four things they need to act without opening anything else: who it is, what they said in their own words, the score and its reason, and a one-tap link to the record.

What goes wrong: an email notification into an inbox that is checked twice a day, which rebuilds the delay the whole system was built to remove.

Step 8: log everything, and read the rejects every week

Every step writes a timestamped line to the record: captured, deduped, enriched, scored with reason, routed to whom, notified, first human contact. That log is the only way to find out which step is slow.

Then one standing half hour a week: somebody reads the leads the system scored low. Not all of them, twenty. This is the step that keeps the automation honest, and it is the first one to be dropped. Within a quarter of dropping it, the rules describe a business you no longer have.

What goes wrong: logs that only record the final state, so when a lead takes nine minutes to route, there is no way to tell which step took the eight.

What does this cost to build?

A workable version is a week of one capable person's time on tools most companies already pay for: the CRM's own workflows for routing and notification, an enrichment provider, and a workflow tool like n8n or Zapier for the parts the CRM cannot do. Spend the week on the order above rather than on the sophistication of the scoring. Routing in under a minute with a crude score beats routing in a day with a clever one, by the margin in that 2007 study.