Lead Response Time: How to Measure It and What to Hit
Key takeaways
- Lead response time is the elapsed time between an inbound lead arriving and your first human reply that answers what the buyer actually asked.
- Autoresponders, internal notes, and unsent drafts do not stop the response clock; only a reply the customer can see counts.
- A realistic benchmark is a first reply inside 5 minutes during your shift, inside 15 minutes for after-hours leads you catch, and a second touch within 24 hours on every lead.
- HubSpot reports the median time between contact creation and first reply, broken out by rep, but the clock keeps running through nights and weekends.
- A draft-first workflow where AI drafts and a human checks the price before pressing Send delivers speed without risking a wrong price in writing.
Lead response time is the elapsed time between a lead arriving in your inbox and your first real reply reaching that customer. It's the single number your manager checks when a Messenger thread goes cold, and this guide shows how to measure it, what counts as a first touch, and how to set a standard you can actually hit after hours.
What is lead response time, exactly?
Lead response time is the gap between a lead arriving and a human sending the first real reply. Not an autoresponder, not a "thanks, we'll be in touch" template: an answer that addresses what the buyer actually asked, with a price or a next step.
Lead response time vs speed to lead
Speed to lead is the same clock, usually measured in minutes, with the same weight given to automated touches. First-touch time is broader: it counts any contact, including a bot. The distinction matters because the original Lead Response Management study measured qualification rates against delay in minutes, and only genuine replies move a Marketplace or Messenger thread forward. A checked reply desk like Hold the Send optimizes for that second clock: draft fast, verify, send.
How do you measure lead response time (and what counts as a 'response')?
Lead response time is the gap between the timestamp on the inbound lead and the timestamp on your first human reply. Measure it per lead, then average across a week. Two rules keep the number honest: the clock starts at the customer's message, not when you opened the thread, and only a reply the customer can see stops it. An internal note, a task, or a draft sitting in your queue does not count.
Worked example: one Messenger lead, timestamps included
| Event | Timestamp | Clock |
|---|---|---|
| Lead asks "out-the-door price on the 2023 Camry?" | Tue 6:52pm | 0:00 |
| Autoresponder: "Thanks, we'll be in touch" | Tue 6:53pm | 0:01 (doesn't stop the clock) |
| You open the thread | Tue 9:40pm | 2:48 (doesn't stop it either) |
| You send a real reply with price and next step | Tue 9:58pm | 3:06 |
Your response time for that lead is 3 hours 6 minutes, not 5 minutes. The autoresponder muddies it but doesn't answer it.
Edge cases: autoresponders, voicemail, and the 7:14pm lead
An automated confirmation is not a response, because it answers nothing the buyer asked. A voicemail you leave on an inbound call counts only when the customer can hear it; the timestamp that matters is when they listen, which you usually can't verify, so log the call time and flag it. The harder case is the 7:14pm lead: if your standard is "one hour during business hours," you're measuring 9:14am tomorrow. That's a policy choice, not a measurement choice. If after-hours speed matters to you, the standard has to say so explicitly, and the reply has to start from a checked draft so a wrong price never goes out in writing at 9pm. That's the workflow behind the price-and-promise reply desk: AI drafts, a human checks the number, then presses Send.
Why does inbound lead response time decay so fast?
A lead is hottest the moment they hit send. They are sitting in Messenger or Marketplace with their phone in hand, comparing two or three dealerships, and the first rep who answers shapes the whole conversation. Every minute after that, intent cools and the buyer drifts back to browsing.
HubSpot's own reporting treats reply time as a core service metric for exactly this reason (HubSpot docs). The practical decay curve is simple: minutes win conversations, hours win replies to your reply, and next-morning responses mostly win silence, because the buyer has already booked a test drive elsewhere.
This is why after-hours coverage matters more than most reps assume. Leads do not arrive on a 9-to-5 schedule, and a draft waiting at 7pm beats a fresh reply at 9am. Tools like Hold the Send exist to close that gap without letting an AI press Send on a wrong price.
What's a realistic B2B lead response time benchmark?
Published benchmarks are mostly averages, and averages hide the reps who win. A realistic benchmark for a dealership internet-sales rep is one you can hit on your worst day, not your best: first reply inside 5 minutes during your shift, inside 15 minutes for after-hours leads you catch, and a second touch within 24 hours on every lead without exception. Anything under 5 minutes puts you ahead of most B2B teams; anything over an hour means the lead has already shopped two other lots. The reason the worst-day framing matters is simple: a standard you miss twice a week trains your team to treat the standard as optional, and once it's optional, it stops measuring anything.
A number you always meet, even a slower one, gives you a real baseline to improve against next month. It also gives your manager something defensible to report upward, because a benchmark backed by a CRM export survives scrutiny in a way a stretch goal does not. Set the number from data, hit it for a full month, then tighten it by a third and repeat.
The honest caveat: a 5-minute benchmark only works if the reply is ready before the lead arrives. That is the whole argument for a draft-first workflow. AI drafts the reply the moment the lead lands, you check the price and the promise, and you press Send, so your speed comes from the head start, not from skipping the check. The failure mode is the opposite: a fast auto-send with a wrong price in writing, held for a manager after the customer already saw it. If you want the checked-reply setup on a single seat, the Solo license details are at the Hold the Send buy page.
Fill-in worksheet: set your own benchmark from a CRM export
Pull 30 days of inbound leads from your CRM. For each, note time-in, first-reply time, and whether the lead closed. Fill in: median first-reply time today (that is your baseline); your 5 fastest replies (that is your ceiling); the hour of day most slow replies happen (that is your staffing gap). Then set next month's standard at your current median minus 30%, and recheck.
How does HubSpot track lead response time?
HubSpot calculates lead response time as the median time between when a contact is created and when a rep sends the first reply, logged through the connected inbox or the conversations tool. You'll find it under Reports in the CRM, broken out by rep, so a manager can see who's hitting a five-minute standard and who's answering at lunch. Two things trip teams up: autoresponders and bulk emails don't count as responses, and the clock keeps running through nights and weekends, which is exactly when Marketplace leads arrive.
That after-hours gap is why the benchmark hurts. The Harvard Business Review lead-response study found firms took an average of 47 hours to respond, and firms that contacted leads within an hour were nearly seven times more likely to qualify them (the HBR lead-response study). If your CRM shows a median you can't hit at 7pm, a draft-first workflow like Hold the Send's checked reply desk closes it: AI drafts, you check the price and press Send. We track our own benchmarking notes at the Hold the Send research page.
Do autoresponders count toward your response time?
By most CRM definitions, yes: an automated acknowledgement counts as a first response the moment it fires, which is exactly why it's a misleading number. A "thanks, we got your message" reply at 6:02pm makes your dashboard look fast while the buyer is still waiting on a price, a trade figure, or a test-drive slot.
Treat the autoresponse as a receipt, not a response. Track two clocks: time to acknowledgement and time to a human answer that moves the deal. If you report only the first, you'll hit your standard while losing leads.
The same logic applies to AI drafts. A draft sitting in your queue isn't a reply until you press Send. That's the draft-only rule: the AI reads the inbound message, classifies intent, and writes the answer, but a human checks the price and promise before it goes out. Speed to lead gets measured honestly, and nothing client-facing goes wrong in writing.
How do you set a response-time SLA your team will actually hit?
Pick a standard you can defend on your worst day, not your best. A workable starting point for a solo rep: reply to every new internet lead within 15 minutes during posted hours, and within 30 minutes after hours while you're awake. Anything you can't hit consistently is a promise you'll break in writing to a customer, which is worse than a slower number you always meet.
Write the SLA around behavior, not tools: who owns the thread, what counts as a real reply (an answer with a next step, not an acknowledgment), and what happens when a lead arrives while you're with a customer on the lot.
After hours: the gap most standards ignore
Most response-time standards quietly assume someone is at a desk. Internet leads aren't. Messenger also constrains you: Meta's documentation on messaging windows and response badges shows that after 24 hours, your ability to message a lead freely is restricted, so a reply that waits a day may cost you the thread entirely.
The honest fix is a draft waiting when you check your phone, not an unattended sender. That's the tradeoff behind draft-only tools like Hold the Send: you press Send, so the SLA is only as good as your habit of checking, which is exactly why the standard has to be one you'll actually hit.
Where does AI fit in a checked reply desk?
Draft-only AI shortens lead response time by doing the slow part before you touch the keyboard: it reads the inbound message, classifies intent, and writes a reply you review and press Send on. You skip blank-page drafting, so a 7pm Messenger lead gets a checked answer in minutes instead of tomorrow morning. The human still catches a wrong price in writing or an off-tone promise before the customer sees it.
That's where Hold the Send sits: AI drafts, humans send. Competitors take different positions. Matador AI, Numa, Relay, and Podium offer dealership communication automation directly; Mika is adjacent. Some send without a human approval step, which trades speed for the risk of a model misreading intent.
Honest scoring: how Hold the Send does and doesn't cut response time
Hold the Send cuts first-draft time hard and works after hours from a $149/mo Solo seat (founding $74). Where it falls short: it never sends for you, so a reply waits until a human presses Send, and it covers Messenger, Marketplace, and CRM threads rather than phone or text. If you want maximum hands-off automation, a draft-only desk is the wrong fit. If trust matters more than hands-off, it's the right one.
FAQ
What is a good lead response time for internet sales leads at a dealership?
Aim for a first reply inside 5 minutes during your shift and inside 15 minutes for after-hours leads you catch, with a second touch within 24 hours on every lead. Anything over an hour usually means the buyer has already contacted two other lots. Set the number you can hit on your worst day, not your best.
Does an out-of-office or auto-reply count as my first response?
Most CRM dashboards count it, which is why the reported number misleads. An automated acknowledgement answers nothing the buyer asked, so treat it as a receipt, not a reply. Track two clocks separately: time to acknowledgement and time to a human answer with a price or next step. Reporting only the first lets you hit your standard while losing deals.
How do I calculate average lead response time in HubSpot?
HubSpot reports the median time between contact creation and the first reply sent through the connected inbox or conversations tool, broken out by rep under Reports. Autoresponders and bulk emails don't count as responses, but the clock runs through nights and weekends. Pull a per-lead view if you want to audit the median yourself.
What's the difference between speed to lead and lead response time?
Speed to lead is the same clock measured in minutes, and it typically credits automated touches as responses. Lead response time is stricter: only a genuine human reply that addresses the buyer's question stops it. The distinction matters because qualification rates were measured against minute-level delays, and only real replies move a Messenger thread forward.
How fast should I reply to a Facebook Marketplace lead after hours?
Within 15 minutes if you're awake and checking, using a pre-checked draft so no wrong price goes out in writing at 9pm. Waiting until morning risks more than a cold lead: after 24 hours, Meta restricts your ability to message freely, so a delayed reply can cost you the thread entirely. Build the draft-first habit.