Speed to Lead: What the Response-Time Data Actually Shows
Quick answer
- Measured from enquiry to first outbound touch — not to first reply.
- The decay is steepest inside the first 30 minutes, before most teams have seen the lead.
- Report the median, not the mean: a few very late leads distort an average.
What the research found
Every figure below is linked to the source it was read on. Where a study is paywalled or its methodology is not published, it is not listed — including the frequently-quoted “7x within an hour” figure, which cannot be verified on the page it is attributed to.
| Finding | Figure | Source | Method |
|---|---|---|---|
| Drop in odds of qualifying a lead, 5 min to 30 min | 21x | Lead Response Management Study | 15,000+ leads, 100,000+ call attempts, with Prof. James Oldroyd |
| Drop in odds of qualifying a lead, 5 min to 10 min | 4x | Lead Response Management Study | Same dataset |
| Drop in contact success within the first hour | 10x+ | Lead Response Management Study | Same dataset |
| Drop in qualification within the first hour | 6x+ | Lead Response Management Study | Same dataset |
| Share of a rep's time spent actually selling | 28% | Salesforce, State of Sales (2022) | Survey of 7,775 sales professionals |
| CRM users saying under half their data is accurate and complete | 76% | Validity, State of CRM Data Management (2025) | Survey of 602 CRM users and admins, US/UK/AU |
| Sales reps using AI tools — more than any other tool category | 37% | HubSpot, State of Sales Report (2025) | Survey of 1,000 global sales professionals |
How speed to lead is measured
Speed to lead is the gap between two timestamps: when the lead record was created, and when the first outbound activity was logged against it. It ends at the first attempt, not at the first successful conversation — a rep who calls in ninety seconds and reaches voicemail has still responded in ninety seconds.
The formula
speed to lead = median(first_outbound_activity_at − lead_created_at)
Why the median, not the mean
Lead response distributions have a long tail. A handful of leads answered three days late will pull a mean into double-digit hours while the typical lead is handled in twenty minutes — so the average describes a problem the team does not have and hides the one it does. Report the median as the headline and the 90th percentile beside it, so the tail stays visible instead of averaged away.
Why the decay is so steep
An inbound enquiry is a moment of intent, not a standing preference. The prospect is at their desk, has the problem in mind, and — in most categories — has just submitted the same form on two or three competitors’ sites. Responding inside five minutes catches the person while all of that is still true. Thirty minutes later they have moved on to another task, and the first vendor who called is already the incumbent in the conversation.
Speed to lead by channel
Buyer expectation differs by the channel they chose. A live-chat visitor is waiting on the page; an email enquirer is not.
| Channel | Buyer expectation | Practical target | Automatable? |
|---|---|---|---|
| Web form | Minutes | Under 5 minutes | Yes — routing + acknowledgement |
| Click-to-WhatsApp ad | Immediate | Under 2 minutes | Yes — templated first reply |
| Live chat | Seconds | Under 30 seconds | Yes — bot handoff |
| Inbound phone call | Immediate | Answer, or call back under 5 minutes | Partly — missed-call callback |
| Email enquiry | Hours | Under 1 hour | Yes — parse to lead + acknowledge |
| Marketplace / portal lead | Minutes | Under 5 minutes | Yes, if the portal pushes to CRM |
| Referral introduction | Same day | Under 4 hours | No — respond personally |
What slows teams down
Slow response is almost never a motivation problem. It is a routing problem, an inbox problem, or a notification problem.
| Cause | Typical delay added | Fix |
|---|---|---|
| Lead lands in a shared inbox, not the CRM | Hours to days | Push every source into the CRM at creation |
| No routing rule, so nobody owns it | Hours | Auto-assign at creation by territory, product or round-robin |
| Owner is on another call | 20–60 minutes | Fallback owner after a short unactioned window |
| Lead arrives outside business hours | Overnight | Automated acknowledgement + queued human touch at open |
| Rep qualifies manually before making contact | 15–90 minutes | Contact first, qualify on the call |
| Form data lands in a spreadsheet first | Hours | Remove the spreadsheet step entirely |
| Notification goes to desktop email only | 30+ minutes | Mobile push on assignment |
The context for all of this: Salesforce’s State of Sales research (2022, 7,775 sales professionals) found reps spend 28% of their time actually selling. The other 72% is where a five-minute response goes to die — and it is the reason routing and logging have to be automatic rather than disciplined.
How to measure and improve it in your CRM
- 1
Timestamp lead creation
Ensure every lead source — web form, click-to-WhatsApp ad, inbound call, chat — writes a created-at timestamp on the lead record. Sources that arrive by email into a shared inbox are the usual gap.
- 2
Timestamp the first outbound touch
Log the first call, email or message against the lead automatically. Manual logging under-reports delay, because reps log the attempt that connected rather than the first one.
- 3
Report the median, not the mean
Calculate the median gap between the two timestamps. Report the 90th percentile alongside it so the tail stays visible.
- 4
Segment by source and by hour
Split the median by lead source and by hour of day. Slow sources and out-of-hours gaps have different fixes, and a single blended number hides both.
- 5
Set a routing rule per source
Assign an owner automatically at creation — round-robin, territory or product. An unassigned lead has no one whose median it damages, which is why unassigned leads are always the slowest.
- 6
Alert on the device the owner actually has
Send the assignment to mobile push, not only to email. The five-minute window closes while a desktop notification sits unread.
- 7
Automate the out-of-hours acknowledgement
Send an immediate acknowledgement outside business hours that sets a specific expectation, then queue a human first touch for the next open hour.
Related metrics
| Metric | Definition | Relationship to speed to lead |
|---|---|---|
| First response time | Time from enquiry to first outbound touch. | The same measurement — the common alias for speed to lead. |
| Time to first touch | Time from lead creation to any logged activity. | Slightly broader; counts internal activity, so it reads faster. |
| Contact rate | Share of leads reached by a human at least once. | Rises as speed to lead falls — the first-order effect. |
| Connect rate | Share of call attempts that reach the prospect. | Improves with speed because intent is still live. |
| Lead-to-opportunity rate | Share of leads that become qualified opportunities. | The downstream metric speed to lead is bought to move. |
| SLA compliance | Share of leads contacted inside the agreed window. | The operational target; report it beside the median. |
Speed to lead — frequently asked questions
Related reading
Cut your first-response time
Lead routing, mobile alerts, sequences and a built-in dialer are included in every paid plan — the mechanics a five-minute median actually needs. Start on the free plan, which never expires.