How fast do you need to respond to a new lead?
Short answer
Aim to respond within five minutes, and treat one hour as the outer limit. Homeowners requesting a quote usually contact several companies at once, so the first business to reply in a real conversation sets the agenda. After roughly a day, a lead is effectively cold.
Key takeaways
- Five minutes is the working target; an hour is the outer limit before a lead has already talked to someone else.
- Response speed is a process problem, not an effort problem. Anything that depends on someone being free will fail at the exact moment you are busiest.
- An automated first reply only has to hold the conversation open. It does not have to close the job.
- Measure time-to-first-reply as a number you can see, or it will quietly drift.
Why does the first five minutes matter so much?
When someone needs a plumber, a roof inspection, or a flooring quote, they rarely contact one company. They work down a list until somebody responds. That behaviour is what makes response time decisive: you are not competing on price or craftsmanship yet, because the customer has no way to judge either. You are competing on who is present.
The first company to start an actual conversation gets to frame the job. They ask the qualifying questions, they establish what "normal" looks like for scope and timeline, and they often book the appointment before a competitor has listened to their voicemail. Everyone who replies later is responding to a customer who already has an anchor.
The uncomfortable part: the lead you lose this way never tells you. There is no rejection, no lost bid, no feedback. The phone simply rings once and nothing follows.
What counts as a response?
A response is the start of a two-way conversation. That distinction matters because several things that feel like responses are not.
- A voicemail greeting is not a response. It moves the work back onto the customer.
- An auto-reply that says "we have received your enquiry" is not a response. It closes the loop instead of opening one.
- A reply that asks one useful question is a response, even if it is automated.
- A text that offers two concrete appointment windows is a strong response, because it gives the customer something to do next.
This is why texting outperforms calling back for a first touch. A missed call returned forty minutes later interrupts someone who has moved on. A text sent in thirty seconds sits in their hand while they are still thinking about the problem, and it costs them nothing to answer.
Why does response time slip even when everyone agrees it matters?
Because response speed is usually designed as an intention rather than a system. "We always call people back the same day" is a promise that depends on somebody being available, and the times you are least available are exactly the times leads arrive: mid-job, mid-install, mid-appointment.
- 1
The demand and the capacity peak together
Busy weeks generate more enquiries and leave less slack to answer them. The process fails under load, which is when it matters most.
- 2
Nobody owns the first reply
If answering is everyone's job in principle, it is nobody's job in practice. Enquiries sit while each person assumes another has it.
- 3
The delay is invisible
Most businesses cannot say what their median time-to-first-reply was last month. An unmeasured number drifts in one direction.
How do you build a response process that survives a busy week?
The goal is to remove human availability from the critical path for the first touch only. A person still runs the conversation; they just are not the thing standing between the enquiry and the first reply.
- 1
Catch every channel in one place
Calls, web forms, chat, and texts should land in a single inbox tied to the customer record. Leads lost between tools look identical to leads that never existed.
- 2
Automate the first reply, not the relationship
An instant text that acknowledges the request and asks one qualifying question buys you the time your team actually needs.
- 3
Offer a booking option immediately
Give real availability in the first message. Choosing a window is easier than composing a reply.
- 4
Route to a named owner
Assign every conversation to a person so follow-up has an address.
- 5
Watch one number
Median time-to-first-reply, reviewed weekly. It is the only metric here that predicts the others.
A worked example, with the inputs on the table so you can substitute your own: if you take 60 enquiries a month, miss 15 of them, and would normally convert a third of the ones you speak to, then recovering even half of those missed calls into live conversations is roughly two to three extra jobs a month. Whether that is material depends entirely on your average ticket, which is why the arithmetic is worth doing with your real numbers rather than trusting a benchmark.
Frequently asked questions
Same-day is enough to have a conversation, but usually not enough to be first. If a customer contacted three companies in the morning, a 4pm callback reaches someone who has already had two conversations and possibly booked. Same-day protects the relationship; five minutes protects the job.
Not when it reads like a person and asks something useful. Customers react badly to messages that are obviously mass-produced and ask nothing. A short text that names the business and asks what they need is generally received as attentiveness rather than automation.
Keep it to three things: who you are, an apology or acknowledgement, and one question or booking option. For example: "Hi, this is Ryan at Coastline Plumbing, sorry we missed you. What do you need looked at, and would tomorrow morning or afternoon suit you better?"
Measure the gap between when an enquiry arrives and when a human or automated reply goes out, then take the median rather than the average, since one very slow reply will distort a mean. If your enquiries live in several tools, this is difficult to calculate, which is itself the finding.