Lead Response Time: How Fast Is Fast Enough?

Fast enough is five minutes for a hot inbound lead, and under an hour at the absolute outside. Past that window, the research consistently shows contact rates and conversion odds collapsing — not gradually, but in a steep early drop-off that most sales teams underestimate.

The two studies that anchor every lead response time claim

Almost every statistic you'll see cited about lead response time traces back to one of two sources, and it's worth understanding both because they measure slightly different things and are often mashed together incorrectly.

The MIT / InsideSales Lead Response Management Study (2007)

This is the origin of the "5-minute rule." Researchers from MIT and Kellogg School of Management, working with InsideSales.com, analyzed three years of data: over 15,000 leads and more than 100,000 call attempts across six companies. The headline finding is that a rep who contacts a web lead within 5 minutes is roughly 100 times more likely to actually reach that person, and 21 times more likely to qualify them, than a rep who waits 30 minutes. The decay isn't linear — the study found contact odds fall by roughly 5x just between the 5-minute and 10-minute marks, meaning most of the damage happens in the first ten minutes, not gradually across the first hour.

The Harvard Business Review audit (2011)

"The Short Life of Online Sales Leads," by James Oldroyd, Kristina McElheran, and David Elkington, audited 2,241 U.S. companies directly rather than relying on self-reported data. It found that companies responding to a lead within an hour were 7 times more likely to have a meaningful conversation with a decision-maker than companies responding just one hour later. It also quantified how bad the baseline was at the time: the average company took 42 hours to respond, 23% never responded at all, and only 37% of companies managed a response within an hour.

Read together, the two studies say the same thing from different angles: the MIT data shows the shape of the decay curve inside the first 30 minutes, and the HBR data shows how far behind that curve most real companies actually are.

How to respond to leads faster — the actual mechanics

Faster response time isn't a motivation problem, it's a visibility and routing problem. A rep can't respond to a lead they don't know exists yet. The fastest-responding teams share four traits:

• Leads land in the pipeline in real time from the source they actually come from — an ad platform webhook, a form submission, a CSV import — instead of sitting in an inbox waiting to be manually entered.
• Notifications go to a channel a rep is already watching (Slack, WhatsApp, or a mobile push), not a daily or hourly email digest.
• A specific rep, not a shared queue, owns each lead the moment it arrives, decided automatically by routing rules rather than whoever happens to check the CRM first.
• Response time against a target is visible on the lead itself, not just in a monthly report a manager reads after the leads are already cold.

What a fastest-response CRM setup actually requires

A CRM built to hit these windows needs real-time capture (not batch imports), alerting on channels reps monitor live, and SLA timers baked into the pipeline stages themselves. Loomstrat's pipeline board shows per-stage SLA timers directly on the drag-and-drop board, instant new-lead alerts go out over Slack, Discord, WhatsApp, or email the moment a lead arrives — including leads captured through the Meta Lead Ads webhook — and a scheduled SLA breach check surfaces anything that's slipped past its target without a manager having to go looking for it.

What good response time looks like by source

Not every lead source deserves the same target. A Meta lead ad or a live-chat form fill represents active, right-now intent — treat those as five-minute leads. A CSV import from a trade show list or a referral from an existing customer has lower urgency and more patience — a same-day response is usually adequate. The mistake most teams make is applying one blanket SLA to every source instead of setting the target by how hot the intent actually is.