Lead response time is the time between a new customer inquiry and your business’s first meaningful response. For a contractor, that inquiry might be a phone call, web form, text, Google Local Services lead, or message from another platform.
The useful question is not whether every lead gets a reply in five minutes. It is whether each inquiry reaches the right owner, with enough context, inside a response window your business has chosen and can keep.
That distinction matters. A fast automatic confirmation can tell someone the inquiry arrived. It does not answer their question, confirm availability, or mean a person has reviewed the request. Measure those events separately.
What the five-minute research actually found
The phrase “five-minute rule” comes from general sales research, not a study of completed contracting jobs.
A 2007 lead-response study reported that the odds of contacting an internet lead were about 100 times higher at five minutes than at 30 minutes, while the odds of qualifying that lead were about 21 times higher. Those figures describe contact and qualification odds in that study. They do not mean a contractor is 100 times more likely to win a job.
A later InsideSales response study analyzed 55 million sales activities and 5.7 million inbound leads across more than 400 companies. It reported much higher conversion rates for attempts made in the first five minutes than for attempts made later. The study is useful evidence that response speed deserves measurement, but its broad sales sample is not a contractor-specific benchmark.
Harvard Business Review’s overview of online lead response also found large differences in how quickly companies followed up. Again, that supports a disciplined response process. It does not establish one universal deadline for every trade, channel, or hour of the day.
The practical takeaway is simple: measure your own delay, shorten avoidable gaps, and test whether faster meaningful responses improve your business outcomes.
Define the four timestamps before you measure
Use the same definitions across your phone system, inboxes, CRM, and advertising platforms.
| Event | Definition | What it does not prove |
|---|---|---|
| Inquiry received | The platform records a new call, form, text, or message | That anyone saw it |
| Acknowledged | The caller or sender receives confirmation that the inquiry arrived | That the request was understood or accepted |
| Meaningful response | A person or configured call handler addresses the request, gathers useful details, or states the next real step | That the work is booked |
| Next step confirmed | A real callback, estimate visit, appointment, or other approved action is agreed | That the job will close or be completed |
Do not combine these into one number. A form autoresponder can produce a ten-second acknowledgment while the actual review takes six hours. Both timestamps are useful, but they answer different questions.
Audit your last 30 inquiries
Start with the most recent 30 genuine new-business inquiries. Exclude spam, vendors, job applicants, and existing-customer service messages unless those are part of the workflow you want to study.
Create one row per inquiry with:
- Date and time received
- Channel
- Inside or outside staffed hours
- Caller or customer need
- Acknowledgment time
- First meaningful-response time
- Assigned owner
- Next step
- Outcome, if known
- Reason for any delay or failure
Use platform timestamps when available. If a timestamp is missing, mark it unknown instead of estimating it.
Calculate metrics that expose the real gap
For each channel, calculate:
Acknowledgment time = acknowledgment timestamp minus inquiry timestamp
Meaningful response time = meaningful-response timestamp minus inquiry timestamp
Target attainment = inquiries answered within your chosen target divided by eligible inquiries
Report the median and 90th percentile, not only the average. The median describes the typical inquiry. The 90th percentile shows the slower tail where ownership and routing problems often hide.
Example: if the median phone response is immediate but the 90th percentile is four hours, most calls may be covered while a smaller but important group reaches voicemail or waits for a callback. If form acknowledgments are immediate but meaningful responses take a day, the gap is review ownership, not form delivery.
Break the results out by:
- Calls, forms, texts, and marketplace messages
- Staffed and after-hours periods
- New leads and existing customers
- Routine requests and calls that follow an approved escalation rule
- Weekday and weekend, if volume allows
Set targets from the workflow, not a slogan
Choose targets that match the channel and the promise you are prepared to keep.
| Inquiry type | Example operating target | Owner to name |
|---|---|---|
| Routed inbound call | Answer live or follow the documented no-answer route | Primary phone owner and backup |
| Missed call | Send an honest acknowledgment, then complete a meaningful callback inside the stated window | Callback owner |
| Web form | Confirm receipt, then review during a defined staffed period | Estimating or office owner |
| Text or marketplace lead | Reply in the same channel or move it to a tracked conversation | Named inbox owner |
| Caller reporting an urgent situation | Follow the business’s approved escalation and safety boundaries | Primary and backup escalation owners |
These are examples, not universal standards. A one-person roofing company, a 20-technician HVAC business, and a remodeling contractor with long estimate cycles should not pretend to have the same response promise.
Fix ownership before adding automation
Most slow-response problems are handoff problems. For every channel, write down:
- Who owns the first response during staffed hours
- Who owns it when that person is busy
- What happens after hours
- What information must be captured
- What the responder may and may not promise
- When an inquiry is considered handed off
- Who checks failed routes and unanswered messages
If the answer is “everyone,” the lead usually belongs to no one. Name a primary owner and a backup.
For phone coverage, use the overflow call answering guide during staffed hours and the after-hours call handling guide outside them. If callers can report urgent situations, document the route with the emergency call escalation plan.
Use automation without confusing it with follow-up
Automation is useful when it makes delivery, acknowledgment, and ownership more reliable.
For routed inbound calls, Clara can answer, ask the questions you configure, capture the caller’s details, and send a summary for your review. Clara should not diagnose a trade problem or invent a price, appointment, availability, dispatch status, or arrival time.
That call workflow does not automatically cover forms, Google Local Services Ads, social messages, outbound callbacks, dispatch, or calendars and systems that are not connected. Give every channel its own owner and test the full path from inquiry to confirmed next step.
A missed-call text can acknowledge an unanswered call, but it should state what will really happen next. See the missed-call text-back guide for scripts and consent considerations.
Run a seven-day response-time test
After the baseline audit:
- Choose one channel with a clear ownership gap
- Set a realistic target for acknowledgment and meaningful response
- Name the primary and backup owner
- Fix the routing or notification
- Test during staffed, busy, and after-hours conditions
- Record every eligible inquiry for seven days
- Compare median, 90th percentile, target attainment, and next-step rate with the baseline
Change one part of the workflow at a time when possible. That makes the result easier to interpret.
Do not treat a booked estimate as a completed job or revenue. Track later outcomes separately: qualified inquiry, estimate scheduled, estimate completed, job won, and paid work. This keeps a faster acknowledgment from being mistaken for a business result it did not produce.
Copyable lead-response plan
New [channel] inquiries are recorded at [source]. During [coverage window], [primary owner] sends or completes the first meaningful response within [target]. If that owner is unavailable, [backup owner or route] takes over after [trigger]. We capture [required details], state [honest next step], and do not promise [price, appointment, availability, dispatch, or arrival time] unless the approved system confirms it. [Review owner] checks failed and late responses every [cadence]. We report acknowledgment and meaningful response separately using the median, 90th percentile, and percentage within target.
Replace every bracket with a real person, rule, or time. Then test it through each live channel.
Methodology and sources
This guide was rewritten August 22, 2026 after reviewing Clara’s finalized Google Search Console opportunity data, recent X discussion, Perplexity research, Parallel results, Firecrawl source discovery, and the existing page’s claims. Clara had no established lead-response query demand in the reviewed GSC window, so we improved the existing URL instead of creating a competing page.
The 2007 lead-response study is available in this archived study summary. It studied internet leads and reported contact and qualification odds, not contractor job conversion. The InsideSales 2021 study and Harvard Business Review overview cover broader sales response behavior. We use them as context, not as proof of a guaranteed result for contractors or Clara.
Your results will depend on lead source, demand, staffed hours, service area, job type, response quality, price, reputation, and availability. Measure your own funnel before changing customer promises.
