Lead response time: what it is, how to measure it, and why enquiries go cold

Lead response time is the elapsed time from the moment an enquiry reaches your business to the moment someone takes the first action on it. Written out:

lead response time equals the time of first action minus the time the enquiry arrived

Two parts of that definition do most of the work: where the clock starts and stops, and the difference between opened and actioned. A note on two neighbouring terms follows.

Where the clock starts and where it stops

The clock starts when the enquiry arrives: the form submits, the email lands, the phone rings out, the message comes in. It does not start when you first look at it. That distinction is the whole point: an enquiry that sat unopened in an inbox from Friday afternoon to Monday morning had a response time measured in days, however quickly you acted once you saw it.

The clock stops at the first action taken on the enquiry: the call you placed, the text or email you sent, or the moment you moved it out of "new". It does not stop when the person picks up, replies, accepts a quote or books the job. Those are outcomes, and they are worth recording too, but they are a different measurement.

Opened is not the same as actioned

It is easy to think of response time as one gap: arrival to reply. In practice there are two. The first is how long an enquiry waits before anyone opens it. The second is how long it waits after that before anyone does anything. A tradie who reads a form notification on site at 10:40, means to call back, and finally does at 3:15 has a first gap of a few minutes and a second gap of four and a half hours. The second gap is the one an inbox does not show you, which is why opened and actioned are worth recording separately.

Not the same as first response time, and not quite the same as speed to lead

You will see two neighbouring terms. First response time is a customer-support metric (how long a support desk takes to answer a ticket), and the advice built around it is written for help desks, not for enquiries. Speed to lead is sales-team jargon for the same idea as lead response time, and you will see it attached to pitches for automated call-backs. This article uses lead response time because it describes the thing a small business can actually measure: the wait between an enquiry arriving and a person acting on it.

You cannot manage a number you estimate. "We usually get back to people the same day" is a belief, not a measurement, and an easy one to hold. Measuring lead response time honestly means recording moments, per enquiry, as they happen, not typing a status in afterwards.

Three timestamps, not one

The minimum that makes the two gaps visible is three timestamps on every enquiry. They are three fields of the wider per-enquiry record that lead tracking keeps from arrival to outcome; response time is the part of that record this article is about.

• Received — when the enquiry landed. For a website form that is the submission; for an email, the delivery; for a missed call, the call.
• First Seen — when a person first opened it. In LC Flow this is recorded when the lead is opened inside LC Flow — not when an ad was viewed, and not when the customer looked at your website.
• First Action — when a person first did something about it. In LC Flow this is the first tracked contact action taken inside LC Flow: a click on Call, SMS, WhatsApp or Email on the lead, or the lead being moved out of New. It shows that someone acted. It does not prove the person was reached, that they replied, or that a conversation happened.

Received to First Seen is your "nobody has looked yet" gap. First Seen to First Action is your "seen but not actioned" gap. Their sum is your lead response time. That is the method behind LC Flow's website lead tracking for small service businesses: every enquiry carries Received, First Seen and First Action, recorded by the system as they happen rather than written in later.

Record it per enquiry — don't average it

An average hides the enquiry that waited two days behind the ten that were answered in minutes. Keep the timestamps on each enquiry and look at the spread: the longest wait this week tells you more about where enquiries are being lost than the mean does. When you do want one figure, use the share of enquiries that passed your target, not the average.

Why a status set on Friday is not a measurement

A "Contacted" status that a person sets is a claim about the past. It can be set late, set in a batch at the end of the week, or set because someone meant to call and is confident they did. A timestamp written by the system at the moment the action happened is evidence. If your response time comes from statuses people set by hand, you have a record of what people remember, not of what happened.

Business hours, after hours and what to count

Decide in advance how you treat enquiries that arrive outside the hours you actually work. Two honest options: count the clock from arrival regardless (so an 8pm enquiry answered at 7:30am reads as eleven and a half hours, which is the customer's experience), or record arrival time as it is and set a separate target for out-of-hours enquiries ("by 9am the next working day"). Either is fine. What is not fine is quietly excluding them, because an out-of-hours enquiry can wait until the next working day before anyone sees it, and that is the wait you would be hiding.

A worked example (hypothetical)

The times below are invented to show the arithmetic; they are not a real customer and not a claim about any business.

• Received: Tuesday 4:40pm (website form)
• First Seen: Wednesday 7:50am (opened on the phone before the first job)
• First Action: Wednesday 8:05am (called the customer)

• Received to First Seen: 15 hours 10 minutes
• First Seen to First Action: 15 minutes
• Lead response time: 15 hours 25 minutes

Read like that, the fix is obvious and it is not "call faster": the 15-minute gap after opening is fine, and the 15-hour gap before opening is the problem. Either someone checks the inbox at the end of the day, or out-of-hours enquiries get a rule of their own, which is covered further down.

Search for lead response time and you will be told, within seconds, that you must respond within five minutes, that you are 21 times more likely to qualify a lead if you do, that the average business takes 42 or 47 hours, and that 78% of customers buy from whoever replies first. Some of those numbers have a real study behind them. Others have no source we could find. It is worth knowing which, because the ones with a study behind them measured something narrower than the way they are quoted.

The 2007 study behind the number

The "5-minute rule" traces back to a 2007 study of web-lead call-backs by Dr James Oldroyd, then a faculty fellow at MIT, using data from the sales-software company InsideSales.com. It was presented at a MarketingSherpa summit in October 2007 by Oldroyd and InsideSales.com's chief executive. The executive summary (PDF) (the only part we could retrieve, hosted by a third party) describes three years of data across six companies: over fifteen thousand web-form leads and over one hundred thousand call attempts. It does not say where those companies were based.

Its headline finding: the odds of contacting a lead when the call-back happened within 5 minutes rather than 30 were around 100 times higher, and the odds of qualifying the lead were around 21 times higher. The odds of reaching someone also fell more than tenfold across the first hour.

Three things the summary itself makes plain. It measured whether a call-back reached the person (contact) and whether the lead was then counted as qualified, and it does not say how "qualified" was judged. It says, in its own words, that the study "did not address close ratios", so it says nothing about winning the job. The data came from one software vendor's own call-back system, and that vendor sells call-back software. And it is from 2007, and from a sales floor calling back web-form leads, not from an owner reading an enquiry on a phone between jobs.

The 2011 Harvard Business Review audit and the 42-hour figure

In March 2011 Oldroyd, with Kristina McElheran and David Elkington, published "The Short Life of Online Sales Leads" in Harvard Business Review. They audited 2,241 US companies by sending each one a test enquiry through its website and timing the response: 37% responded within an hour, 16% within one to 24 hours, 24% took more than 24 hours, and 23% never responded at all. The average response time, counting only the companies that replied within 30 days, was 42 hours.

The same article reported a separate dataset of 1.25 million enquiries received by 29 consumer and 13 business-to-business companies in the US. Firms that tried to make contact within an hour of the enquiry were nearly seven times as likely to qualify the lead (which the authors defined as having a meaningful conversation with a key decision maker) as firms that tried even an hour later, and more than 60 times as likely as firms that waited a day or more. Again: reaching a conversation, not winning the work.

The numbers you will see quoted that we could not trace to a source

• "78% of customers buy from the first business that responds." Each citation chain we followed ended at another blog post attributing it to a survey we could not retrieve. No study we could retrieve measured purchases at all. Until someone produces the primary source, treat it as unsourced.
• "The average response time is 47 hours." The figure we could trace is 42 hours, from the 2011 audit above, among the US companies that responded within 30 days. For 47 we could find no primary source; it may be a drift from 42 rather than a second study.
• "21 times more likely to convert." The 2007 study reported qualification odds, said in its own words that it "did not address close ratios", and its executive summary does not define "qualified" as a sale. "Convert" is a rewrite.

So is the 5-minute rule real?

It is real as a pattern in one vendor's phone-call data from 2007, from six companies calling back web-form leads. It is not a benchmark for an Australian plumber, and we could not find one: our search turned up no trades-specific Australian study of enquiry response times with a primary source behind it. What survives from the research, once you strip the rewrites, is modest and useful: the first hour is where the odds of a conversation move the most, sooner beats later, and "contacted" and "won" are different things.

What the evidence supports — and what it doesn't

The evidence we could trace supports responding in minutes and hours, not days, and it supports the first hour as the window that matters most. It does not support any particular number of minutes as a rule for a small business, and it does not support the idea that a slower reply loses the job every time. The stronger argument is not a statistic but the customer's situation: the person who filled in your form can ask another business at any moment, so the wait is a wait against your competitors, not against a clock.

What Australian consumers say they expect from service in other industries

The closest Australian evidence we could find is about service expectations rather than trade enquiries. PwC Australia's Customer Sentiment Survey 2025, which asked 1,600 Australian consumers about eight industries (banking, superannuation, general and health insurance, telecommunications, utilities, retail and grocery), found that 75% believe it takes too long to get a service response, and that 58% expect a reply to an online message within five minutes. Read it as evidence that many Australian consumers bring fast-response expectations to digital service interactions. It is not a trades benchmark, the survey did not ask about trade enquiries, and it is not evidence of how quickly Australian tradies respond to them.

Set a target you can keep, then tighten it

A target is a promise to yourself, and a broken one teaches everyone to ignore it. Start with one you can meet on a normal working day, which for a one-person or small-crew business might be "within the hour during working hours", and tighten it once your own timestamps show you are meeting it. An honest target you hit beats an aspirational one you miss, because the point of the target is to make the misses visible.

Enquiries that arrive out of hours

Give them their own rule rather than pretending they don't happen. "Acknowledged the same evening if it arrives before 8pm, called by 9am the next working day" is a target a customer can respect and you can keep. The enquiry that arrives at 9:30pm is easy to forget by morning, and a rule for it is worth more than a faster rule for the ones that arrive at 10am.

Acknowledging is not the same as answering

You do not need the quote ready to respond. A short, human message, "Got your enquiry about the hot water system, I'll call you at eight tomorrow", sent in minutes does more than a full quote sent tomorrow afternoon, because it tells the customer they have been heard before they ask the next business. It also stops the clock on your first action honestly: you did act, and the record will show it.

Advice written for sales teams blames slow routing, data enrichment and rep queues. None of that exists in a business where the owner answers the phone. The delays in a service business are simpler: an enquiry lands somewhere nobody is looking, or it is seen and nobody owns the next step.

Enquiries land in more than one place

The website form emails one inbox. A directory listing texts a mobile. A social page holds messages that can go unchecked all week. A missed call sits in a call log. Each place is checked on its own rhythm, and the enquiry that landed in the least-checked one waits longest. Response time is slow because the enquiry was somewhere nobody was looking, not because anyone chose to be slow.

Nobody owns the first reply

When two people can see the inbox, each can reasonably assume the other has it. When one person can see it and is on the tools, the enquiry waits for the next break. Deciding who owns the first reply — and what "the first reply" means (an acknowledgement, not the quote) — removes this delay. A tool can show the wait; the decision is yours.

On the tools, after hours and on Friday afternoon

The working day of a trade is not a sales floor: an enquiry can arrive while hands are busy. Enquiries can arrive at lunchtime, late in the afternoon or in the evening, and Friday afternoon's enquiry has a whole weekend in which to go cold. Trying harder does not fix this. Knowing, at the end of the day, which enquiries are still waiting does.

Seen but not actioned: the gap inside the gap

One delay that is easy to miss is the one that feels like it has been handled. The enquiry was opened, read, and mentally filed as "call them later". It has been seen, so it no longer looks urgent, and it waits. That is the second gap from the definition above, and it is why First Seen and First Action are recorded separately: an enquiry opened within minutes and still unactioned hours later looks handled in an inbox. In a list it looks like what it is: First Seen recorded, no First Action yet, and the clock from arrival still running against your target.

A common fix sold for lead response time is software that replies for you: a text fired the instant the form submits, or a bot that answers on your behalf. That may suit a sales floor. For a service business it replaces the thing the customer actually wanted — a person who will do the work — with a message that proves nobody has read the enquiry yet. Closing the gap is about making the wait visible and shortening it, not about replying without reading. This is how LC Flow approaches it; the principles hold whatever you use.

One place for every enquiry, new and overdue first

The first move is to stop checking places and start checking a list. Enquiries from your website forms land in one workspace once your site is connected and your domain is verified, alongside your other supported sources, each stamped Received on arrival. New enquiries and overdue ones sit at the top, so the next action is obvious without reading everything.

A target, and a visible "overdue"

You set a response target for the workspace. An enquiry that passes it is shown as late or overdue in the list — not hidden, not averaged away. That is the target from the previous section made real: the miss is visible the moment it happens, shows as overdue until someone acts, and settles as late once they have.

Alerts and reminders that stop when you act

LC Flow emails you when an enquiry arrives, and sends up to five follow-up reminders while it is still sitting there unactioned. The reminders stop as soon as the lead is actioned, so there is no noise for work already done. Alerts are email only; there are no SMS or chat alerts. And LC Flow does not message your customer for you: it reminds you, and the reply is yours.

Reply yourself, from the enquiry, on your own phone

Each lead carries Call, SMS, WhatsApp and Email links that open your own phone and apps, addressed to the customer's number or email address. If it is the first tracked action on that lead, clicking one records First Action. That timestamp says you acted on the enquiry at that moment; it does not say the message was sent or the call connected. What the enquiry became is a stage you set, recorded separately. No call is placed and no message is sent to the customer from inside LC Flow.

Record what it became

The last timestamp worth keeping is the outcome. Each lead moves through New, Contacted, Quoted and Won or Lost, and you can record the value of the work you won. "Contacted" here is a stage you set, not proof that a conversation happened — First Action is the recorded fact, Contacted is your judgement — and keeping both is what lets you see, a month later, whether the enquiries you answered fastest were the ones that became jobs.

If you would rather look at your numbers than someone else's, you can see your timestamps in a 14-day free trial, no credit card required.

Once the timestamps exist, four readings from this week's enquiries tell you most of what you need, and none of them needs a spreadsheet. Each is a longest wait or a count, never an average, and an enquiry that is still waiting counts as waiting, not as zero: its wait runs up to the moment you take the reading.

• Received to First Seen. For each enquiry, how long it waited before anyone opened it. Read the longest wait this week, and count the enquiries that were still unopened at the end of it. If this is the long gap, the problem is where enquiries land and who checks it.
• First Seen to First Action. For each opened enquiry, how long it waited after being opened before anyone acted. Read the longest this week, and count the enquiries that were opened and still have no First Action. If this is the long gap, the problem is "call them later". Add the two gaps together and you have each enquiry's lead response time: Received to First Action.
• How many passed your target. Of all this week's enquiries, the number and share that went past your response target before their first action, including the ones still waiting past it, and which ones they were. A single figure that is honest in a way an average is not.
• How many arrived out of hours. Of all this week's enquiries, the number that arrived outside your working hours. If a third of them arrive after 6pm, your out-of-hours rule matters more than your 10am one.

Read them against the target you set, not against a benchmark from a 2007 sales floor. The aim is fewer enquiries waiting in places nobody is looking, and a record that tells you the truth about how fast you are, not a number that looks good in someone else's chart.

• The Short Life of Online Sales Leads — James B. Oldroyd, Kristina McElheran and David Elkington, Harvard Business Review, March 2011. Audit of 2,241 US companies' response to a test web enquiry, plus a 1.25-million-lead dataset from 29 consumer and 13 business-to-business US companies. Measured time to first response and the odds of qualifying a lead (a meaningful conversation with a decision maker); not purchases. Subscription required to read the full article.
• Lead Response Management Study — executive summary (PDF) — Dr James Oldroyd (MIT) and David Elkington (InsideSales.com), presented at MarketingSherpa's B2B Demand Generation Summit, 16 October 2007. Three years of InsideSales.com call data across six companies, over 15,000 web leads and over 100,000 call attempts. Measured contact and qualification odds by call-back delay; states that it did not address close ratios. The seven-page executive summary of a 35-page study, hosted by a third party; we could not retrieve the full study.
• Australia's Customer Sentiment Survey 2025 — PwC Australia, 2025. Survey of 1,600 Australian consumers across banking, superannuation, general and health insurance, telecommunications, utilities, retail and grocery. Consumer expectations of service response speed; not a measurement of trade businesses.

Figures we could not trace to a primary source that supports them — including "78% buy from the first responder" and a "47-hour" average — and the "times more likely to convert" rewrite of the 2007 qualification odds are deliberately not used in this article.