How fast should you respond to an inbound lead?

Within one business hour is the standard worth committing to, because it is fast enough to matter and slow enough that a team can actually hold it every day. Five minutes produces better numbers in studies but almost no team sustains it without dedicated coverage, and a standard nobody meets is worse than a slower one everybody does. The important word is business: one hour inside your buyer's working day, not yours.

Does responding faster to leads actually increase conversion?

The direction is well evidenced. An audit of 2,241 US companies found the average first response to a web lead took 42 hours and 23% never replied at all (Harvard Business Review, 2011), and the Lead Response Management study found the odds of qualifying a lead fell sharply within the first 30 minutes (Oldroyd, MIT Sloan and InsideSales.com, 2007). Both are old enough that the exact multiples should be treated as direction rather than as targets, and buyer expectations have only tightened since.

Why is our lead response time slow when we have enough people?

Almost always ownership rather than capacity. A lead nobody is individually responsible for is answered by nobody, whatever the headcount. The three usual causes are unassigned leads sitting in a shared queue, no coverage during the hours the buyer is actually awake, and no measurement, because a team that does not report response time cannot tell you what it is.

Is fast response enough on its own?

No. Speed decides whether you get the conversation, not whether the lead was worth having. For WorkStore, inbound was already arriving from the website, paid media and referral partners, and the constraint was a written standard for which enquiries deserved a salesperson's time. Answering unqualified leads faster just wastes the time sooner.

GrowthStack Advisory / Resources / Speed to lead

Guide

Speed to lead: how fast must you answer an inbound lead?

The short answer

Commit to a first response within one business hour, measured in the buyer’s working day rather than your own. Faster is better in the studies, but one hour is the fastest standard most teams can actually hold every day, and a standard nobody meets is worth less than a slower one everybody does. The reason response time slips is almost never capacity. It is ownership: a lead sitting in a shared queue that nobody is individually responsible for will be answered by nobody, however many people are available. Speed decides whether you get the conversation. It does not decide whether the lead was worth having, which is a separate problem and needs a written qualification standard rather than a faster reply.

One business hour, in the buyer’s time zone, not yours
Assign every lead to a person, because a queue is not an owner
Measure it weekly or you do not know what it is
Fix qualification too, or you are only wasting the time sooner

Most companies believe their inbound response time is fine. Very few measure it, and the ones that start are usually surprised.

By Shobhit Gupta

Founder, GrowthStack Advisory. 10+ years building SDR and GTM systems at Locus, GoComet, and Landmark Group.

Published 12 September 2026 · 6 min read

What the evidence actually says

Two studies get cited in every conversation about this, and both are worth knowing precisely rather than approximately.

An audit of 2,241 US companies found the average first response to a web-generated lead took 42 hours, and 23% never responded at all (Harvard Business Review, 2011). That second number is the more useful one. Nearly a quarter of companies paying to generate demand never replied to the demand they generated.

The Lead Response Management study found the odds of qualifying a lead dropped sharply inside the first thirty minutes, with the steepest fall in the first five (Oldroyd, MIT Sloan School of Management and InsideSales.com, 2007).

Both are old, and that matters. The specific multiples from a 2007 study of phone response should be read as direction rather than as targets, because buying behaviour has changed underneath them. What has not changed is the direction, and the honest reading of the last twenty years is that expectations have tightened rather than relaxed. A buyer who does not hear back now has more alternatives one search away than they did then.

Why one business hour, and not five minutes

If the evidence points at five minutes, why commit to sixty?

Because a standard is only worth setting if it will be met on an ordinary Thursday when two people are on leave. Five minute response requires dedicated coverage, someone whose entire job during a shift is watching the queue. Teams that promise it without that coverage hit it on good days, miss it on busy ones, and end up with a number nobody trusts and nobody is accountable to.

One business hour is different. It survives a meeting running over. It can be held by a team that also has other work. And because it can be held, it can be measured, reported and coached, which is what actually moves the number over a quarter. This is the standard used in GrowthStack’s own outbound readiness scorecard, where it is one of twelve checks.

If you genuinely have the volume and the margin to staff five minute response, do that instead. Most companies asking this question do not, and are better served by a slower promise they keep.

Whose business hour? The part most teams get wrong

The word doing the work in that standard is business. One hour inside the buyer’s working day, not inside yours.

This is the failure mode for any company selling across time zones, and it is invisible on a dashboard that reports average hours to first response. A lead that arrives at 9am in New York and is answered at 9am the next morning in Asia looks like a twenty four hour response in the data and feels like being ignored to the buyer.

For Easyship, this was the whole shape of the engagement. Easyship sells to eCommerce brands across the United States and the United Kingdom, and the team working those inbound leads sits in India. The answer was not to move the team. It was to run the coverage, the monitoring and the coaching inside United States and United Kingdom business hours, so the standard was measured in the hours the buyer was actually awake. GrowthStack worked on site with that team during those shifts rather than reviewing the output afterwards.

If your buyers and your team are in different time zones, decide explicitly which hours the standard applies to, and staff those hours. A standard that is silent on this question is not a standard.

What actually breaks response time

It is rarely a shortage of people. Three causes account for almost all of it.

Nobody owns the lead. A shared inbox or an unassigned queue means every individual can reasonably assume someone else has it. Assignment to a named person, immediately and automatically, fixes more response time than adding headcount does. How that assignment should work is covered in inbound lead routing.
No coverage in the hours that matter. See above. If enquiries arrive while everyone who could answer them is asleep, the constraint is the rota, not the effort.
No measurement. A team that does not report response time cannot tell you what it is, and will estimate it optimistically. This is the cheapest of the three to fix and usually the one missing.

There is a fourth cause that looks like the others and is not: too many leads to answer, because nobody has decided which ones deserve an answer. That is a qualification problem wearing a speed problem’s clothes, and it is the last section of this page.

How to measure it without building anything

You do not need new tooling. Take last month’s inbound leads and, for each one, record the timestamp it arrived and the timestamp of the first genuine human response. An automated acknowledgement is not a response.

Then report three numbers rather than one, because the average will hide the problem:

Median time to first response, which tells you the ordinary experience.
Percentage answered within one business hour, which is the number to coach against.
Percentage never answered at all. Almost nobody measures this and it is frequently the most expensive line in the report. The HBR audit put it at 23% across 2,241 companies, and teams who measure it for the first time rarely find zero.

Break all three down by source. Leads from a referral partner, a paid campaign and an organic demo request tend to have very different response times, usually because they land in different places and only some of those places have an owner.

What speed does not fix

Speed decides whether you get the conversation. It says nothing about whether the conversation was worth having.

For WorkStore, the exclusive India partner for the Dyson Airblade series, inbound was already arriving in volume from the website, from paid media and from referral partners. Nothing was wrong with the quantity or, particularly, with the speed. What was missing was an agreed standard for which enquiries deserved a salesperson’s time at all, applied the same way on every call. Answering unqualified enquiries faster only wastes the time sooner.

So the two have to be built together. A written definition of qualified, covered in choosing a sales qualification framework, and a response standard that gets you to the qualified ones before somebody else does. Either one alone underperforms.

References

Oldroyd, J.B., McElheran, K. and Elkington, D. The Short Life of Online Sales Leads. Harvard Business Review, March 2011. Audit of 2,241 US companies: average first response 42 hours, 23% never responded.
Oldroyd, J.B. Lead Response Management Study. MIT Sloan School of Management and InsideSales.com, 2007. Odds of qualifying a lead fall sharply within the first 30 minutes.

Speed is one of four things that decide whether inbound converts. The others are routing, a written qualification standard, and whether the team working the leads is coached against that standard. The measurement side sits in improving MQL to SQL conversion.

If the buyers are marketing-sourced, GTM for marketing leaders is the argument for why acceptance rate rather than lead volume is the number worth reporting.