Answer new leads while the question is still fresh
Someone asks for a quote while your team is on a job. The first reply should tell them their request reached the right person and what will happen next. This guide shows how to make that response reliable, then measure the time it takes.
Francisco Contreras · Founder, Machina
7 min read
Make the first useful reply easy to send
A homeowner sends a repair request at lunch. The office manager is away, and the technician who could answer is on another job. The form sends an instant receipt, but the homeowner still does not know whether anyone can take the work. By dinner, the question may have gone to another shop.
Speed to lead is the time from an inquiry to a real first response. A form receipt can confirm delivery and set an expectation; a person still needs to answer the customer’s question or say when they will. The goal is a dependable handoff, not a stopwatch stunt.
In a 2021 analysis of 5.7 million leads, InsideSales reported much higher conversion rates when teams tried first contact within five minutes. The summary does not clearly define whether "conversion" means contact, qualification or a sale, so it cannot support a claim about signed jobs. The data came from companies using its sales tools, and quick responders may differ from slow ones in other ways. Test your own process before using the result in a business case.
Read the five-minute research for what it measured
The often-cited five-minute study came from InsideSales.com in 2007, with James Oldroyd, then affiliated with MIT Sloan. It examined leads and call attempts at six companies. A separate 2011 Harvard Business Review article studied response within an hour. Neither study is a trial proving that every small business will close more work by hitting one exact threshold.
The practical finding is narrower and useful: people who asked for help moments ago are easier to reach while the request is fresh. A qualified conversation, which the 2011 study measured, is not a signed job. The reply still needs to answer the question with care.
Leave weak statistics out of the business case
The claim that 78 percent of buyers choose the first company to answer circulates without a primary study that can be checked. It is a poor basis for a staffing or software purchase. The older studies use different samples and outcomes, so their multipliers should not be combined into a promise.
Build the case with your own records. Count the inquiries that received a reply, the ones that did not, and the jobs each source produced. If people regularly wait until the next day or go unanswered, the problem is visible before you attach a borrowed multiplier to it.
Check the gap in your own week
The 2011 HBR audit found that 23 percent of 2,241 companies did not answer a test web lead. A later RevenueHero mystery shop reported no reply from 63.5 percent of 1,000 software firms it contacted in 2024. Those samples cover different businesses and methods, so they do not show a time trend. They do show why it is worth testing a form instead of assuming it works.
Send a test inquiry on a weekday and another outside normal hours. Call the main number from a phone the team does not know. Record what the customer hears, whether a person follows up, and how long that takes. Repeat after changing the routing; the same test will tell you whether the fix held.
Cover the hours when you buy leads
Google says a consistently fast response can improve Local Services Ads ranking and the chance of receiving leads. It also lets advertisers pause or schedule ads for hours they can cover. This is about the Local Services product, not a claim about ordinary search rankings.
Put your ad schedule beside the actual office and on-call schedule. If a lead arrives when no one can answer, either arrange coverage, offer a clear next business-hour expectation, or stop buying that hour. Do not promise an immediate call when a technician cannot make one.
Give every new inquiry an owner and a backup
Start with the path the customer uses most: phone, form, or message. Make it create one record with arrival time, source, contact details, job type, and the person assigned to answer. Keep the form short enough that someone will finish it.
- 1
Confirm receipt
Use a short form or email acknowledgment to say the request arrived and when a person will reply. Keep it distinct from the human response in your reports. - 2
Assign a person on shift
Send the inquiry to the person who can act now. If that person does not accept it within the time your team sets, route it to a backup. - 3
Make the first reply useful
Refer to the customer’s requested work, ask one needed question, and state a real next step. If the schedule is full, say so rather than leave the lead in a queue. - 4
Stop unnecessary follow-up
Once a person has replied or booked, stop automated reminders. Keep the thread and the next action in the shared record.
A missed-call text can be helpful when it is lawful and the caller expects a reply by text. Do not turn a number from an inbound call into a marketing-text list. Keep service replies and promotional texts separate, record any required consent, and honor a request to stop.
Use the tools already in the workflow
Before adding software, check whether your phone service, booking tool, or CRM already records missed calls, assigns new forms, and alerts a backup. The useful cost comparison is the total time to set up and maintain the route, plus any message or seat charges. Vendor pricing changes too often to make an old table a buying guide.
Trial the route with real staff coverage. A tool that sends a receipt but alerts an absent owner does not solve the wait. A person and a backup need to accept the handoff, even when an automatic message goes out first.
Record arrival and first human response separately
Store the inquiry arrival time and the first useful human response time on each record. Record automatic receipts in their own field. If no person answered, leave that response field empty and count the lead as unanswered; a dashboard should not hide it by counting an auto-reply.
Each week, report the median time among answered leads, plus the share that received no human reply. Split the results by source and by the hour the lead arrived. A median alone can look good while a few people wait all weekend or never hear back.
A first response check
Keep the reply connected to the work
Our Moniveo case study reports a drop in lead response time from 48 hours to five minutes after intake and routing changed. That result belongs to that project; it is not a guarantee for another team. The useful lesson is to measure a known delay, change its handoff, and measure again.
When the next test inquiry arrives, ask whether a person knows what the customer needs and who acts next. If the answer is visible in one place, the lead has not vanished into a busy afternoon.
FAQ
Frequently asked questions
What is speed to lead?
It is the elapsed time from a new inquiry to the first useful response. Measure an automatic receipt separately from a person answering the customer’s question.
Is five minutes a proven rule for every business?
No. Older vendor data links faster first attempts with better outcomes, but the samples and outcomes vary. Use it as a reason to test your own handoff rather than a promise of a conversion lift.
Does a missed call affect Google ranking?
Google says consistently fast responses can improve ranking in Local Services Ads. That does not establish a ranking effect for ordinary search results.
Is an automatic reply enough?
It can confirm receipt and set an expectation. A person still needs to answer the request or give a useful next step, so track those events separately.
Keep reading
Related guides
Next steps
Let's talk about your project
Tell us what you're working on. We'll tell you if we can help — and exactly what we'd do.