Solution
The leads you already paid for, answered
Nearly a quarter of firms answer nothing at all. This is the system that answers inside a window that still converts.
When researchers sent one ordinary web enquiry to each of 2,241 US firms, 23% of them never answered it — and the average first reply from the rest arrived 42 hours later, long past the window in which a reply still changes the outcome. Neither number is a motivation problem. Both are queueing problems, and both stay invisible because nothing in the business measures the gap between arrival and answer.
Teams running automated routing meet the sub-15-minute standard 62.5% of the time against 39.1% for manual handling. That is the entire mechanism, and it is deliberately unglamorous: not a smarter reply, an earlier one, produced by removing the step where a human first has to notice.
Nothing is installed on a phone and no CRM is replaced. It runs on the number, the form and the inbox you already publish. The first working version covers one funnel and is live inside the first four weeks, and the response-time figure it reports is the same one your audit measured before anything was built.
What it is.
Every inbound — form, call, chat, portal — lands in one queue with a timestamp on it, receives an immediate acknowledgement that names what was asked, and is routed to a named person with a deadline attached. Nothing is marked handled until a reply exists.
Whether you need it.
Observable in your own business, without an audit.
- You cannot say, without checking, how long your last ten enquiries waited for a reply.
- Enquiries arrive in more than one place and only some of them reach the CRM.
- Response is quick during the working day and absent after it, and nobody has decided that on purpose.
- You have paid a portal for leads and cannot tell which of them were ever contacted.
How it gets built.
| Stage | What happens, and why in this order |
|---|---|
| Inventory every path | Web forms, the number on the listing, chat, portal enquiries, the address printed on the invoice. Each one is submitted and timed from the outside. Most businesses find at least one path that arrives nowhere, and finding it is usually worth more than everything built afterwards. |
| Instrument arrival and answer | A timestamp is attached when an enquiry arrives and again when a person first replies. Until that gap is a number the response problem is anecdotal, and anecdote is precisely what has kept it unfixed for years. |
| Route with a deadline | Each path gets an owner, a deadline and a fallback. When the owner is unavailable the fallback fires. When nobody is available the acknowledgement still goes out and states when a person will answer, which is a commitment rather than a holding message. |
| Acknowledge specifically | The immediate reply names what was asked and what happens next. A generic auto-responder is worse than silence: it proves the message arrived and that nobody read it, which is a harder position to recover from than being slow. |
| Report daily, by source | One response-time figure per source, updated daily. It is the number the whole system is judged on, and publishing it internally is what stops the system quietly degrading three months after it was built. |
Lead recovery is not a lead generation product. It works on inventory the business has already bought, which is the reason it can be measured honestly: the number of enquiries is fixed before the work starts, so any change in outcome is attributable to what happened after they arrived rather than to a change in volume.
The reason unanswered leads survive in otherwise well-run businesses is that no single person experiences the problem. The owner sees a slow month. The person on the phone sees a busy morning. The portal invoice arrives regardless. Nobody sees the enquiry that came in at ten past four on a Friday and was never opened, because there is no report in which an unanswered lead appears — it is an absence, and absences do not raise their hand.
That is why the first deliverable is a measurement rather than a build. Every inbound path gets submitted from the outside and timed, which turns an argument about whether the business is responsive into a table with times in it. In most cases the table is enough to change behaviour before any automation exists at all, and that is a legitimate outcome — automation that replaces a habit nobody was going to keep is more durable than automation that replaces a habit that was working.
The build that follows is deliberately small. One queue, one timestamp, one acknowledgement that says something specific, one owner per path and one daily number. The temptation with response systems is to route on complex conditions and score every lead on arrival. That belongs in qualification, and putting it here means the response system fails whenever the scoring is wrong, which is the worst possible failure to introduce into the fastest part of the funnel.
The honest limit is that speed alone converts nothing. A reply inside five minutes to a lead who was never going to buy produces a faster no. The value sits in the leads who were already interested and are, at this moment, being answered by whoever replies first — and in a market where the same enquiry frequently reaches several businesses, that is a contest decided before anyone has said anything persuasive.
What this will not do.
-
will not make a cold lead want to buy
will answer an interested one inside the window where an answer still changes the outcome
-
will not replace your CRM, and in most cases I will argue against replacing it
will make the CRM you already pay for the one place every inbound is recorded
-
will not write a reply that sounds like you without your input
will hold the first response to a template you approved, in your words, with a named path to a person
-
will not survive a phone number that rings nowhere or an inbox nobody owns
will find both in the first week, because the first thing measured is whether each path arrives at all
Questions this raises.
Is this just an auto-responder?
An auto-responder confirms receipt. This routes the enquiry to a person with a deadline, escalates when that deadline passes, and reports the gap between arrival and human reply per source. The acknowledgement is the smallest part of it.
What happens outside working hours?
The acknowledgement goes out and states when a person will answer, and the enquiry is queued at the top of the next morning rather than in arrival order. Promising an immediate human reply at midnight would be a commitment nobody keeps twice.
We already respond quickly. Is there anything here?
Then the measurement will show that, and it is worth having in writing. The common finding in businesses that believe they respond quickly is that one channel is fast and a second one, usually the one attached to paid spend, is not monitored at all.
Where this runs.
- Home servicesWhere home services enquiries are lost before the van is booked
- HealthcareWhere patient enquiries are lost between the search and the chair
- LegalWhere legal enquiries are lost before the consultation
- ManufacturingWhere manufacturing enquiries die inside somebody else's process
- Real estateWhere real estate leads are actually lost
- AI follow-up80% of sales need five or more contacts. 44% of agents stop after one. Follow-up is the gap between those numbers.
- AI operationsThe average first response is 42 hours. Nobody decided that — it is what a queue produces when nothing empties it.
- Lead qualificationContact inside five minutes makes qualification 21× more likely. Most businesses decide who to call by who happens to be free.
- Marketing automationBuyers complete around 60% of the journey before speaking to a vendor, and two-thirds would rather not speak to one at all.
Systems like this are built and operated under a retainer. Which one applies, and whether this is the right system to build first, is what the audit decides.
METHOD
Every figure below carries its source and the date it was verified. Nothing on this page is asserted.
The numbers on this page.
| What | Value | Specific to |
|---|---|---|
| Firms that never responded to a web enquiry at all | 23% | This page |
| Sub-15-minute compliance — automated routing vs manual only | 62.5% vs 39.1% | This page |
| Close rate — response under 5 minutes vs over 24 hours | 32% vs 12% | Category-wide |
| Teams responding to an inbound lead within 5 minutes | 7% | Category-wide |
| Average B2B first-response time | 42 hrs | Category-wide |
Oldroyd, McElheran & Elkington, "The Short Life of Online Sales Leads", Harvard Business Review (March 2011) · hours · 1.25M inbound leads across 2,241 US firms · verified
2026 speed-to-lead benchmark · range ~5% FinTech to ~15% RevOps · verified
Optifai speed-to-lead benchmark · n=939 companies · Q2 2025–Q1 2026 · verified
Start with the measurement.
Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.
$497 · delivered in 5 business days · credited against month one