A8gent
GlossaryBusiness and buying

What is lead response time?

Also called: first response time, response SLA

Lead response time is the measured interval between an enquiry and your reply, tracked as a distribution across channels and hours rather than as a single average.

Written by A8gent
Contents
  1. At a glance
  2. What lead response time measures
  3. Instrumenting it correctly
  4. Why the average lies
  5. Setting a target
  6. What you should know
  7. FAQ
  8. Related terms

At a glance

Category
Business and buying
Two timestamps
Enquiry created at source, first customer-recognisable response sent
Common instrumentation error
Measuring from CRM ingestion, which hides polling delay
Report
Median, 90th percentile, and share answered within target
Segment by
Channel and hour of day - these explain most of the variance
Best single fix
Automatic escalation of unclaimed enquiries after a set interval

What lead response time measures

Lead response time is the metric behind speed to lead. Where speed to lead is the concept - respond fast, win more - response time is the number you instrument, report and set targets against. The two are used interchangeably in marketing copy, and it is worth keeping them separate: one is a strategy, the other is a measurement you can be wrong about.

The measurement is deceptively easy to get wrong, and a business that reports a good average while losing enquiries at 7pm on Friday has instrumented it badly rather than solved it.

Instrumenting it correctly

Two timestamps, both from the customer's side of the boundary. Enquiry created is when the form was submitted or the call was placed, not when your CRM ingested it - a five-minute polling interval silently adds an average of two and a half minutes to every measurement, and it is the source of a great deal of self-congratulation.

First response sent is when a message a customer would recognise as a reply actually left. Store both against the enquiry record, along with the channel and the assigned owner. Everything else is derived from those four fields.

Why the average lies

Response times are heavily skewed. Most enquiries during working hours are answered quickly, and a small number - out of hours, holidays, the person who was off sick - take many hours or days. An average blends these into a number that describes nobody's experience.

Report the median for the typical case, the 90th percentile for the bad case, and the share answered within your target window, which is the number to put on a wall. Then segment by channel and by hour, because those two dimensions explain most of the variance. Phone during business hours is usually fine; web forms at 8pm usually are not.

Setting a target

Different channels deserve different targets, and the honest way to set them is by what the customer expects: a phone call expects an answer now, a text expects minutes, a web form expects minutes to an hour, and an email expects hours. Beyond that, set the target you can actually meet at the 90th percentile rather than the median - a target you hit half the time is not a target.

Then decide what happens when it is missed. An automation that escalates an unclaimed enquiry after fifteen minutes does more for the number than any amount of exhortation, because the failures are almost never people choosing to be slow - they are enquiries nobody saw.

What you should know

Response time is a leading indicator you can act on today, unlike conversion rate which tells you about last month. It is also one of the few metrics where automation produces an immediate, unambiguous improvement, which makes it a good first thing to measure when you are trying to demonstrate that an automation project was worth doing - see ROI and cost per booked job.

Measure it for two weeks before you automate anything. A before number that nobody disputes is worth more than any projection, and it costs nothing but a pair of timestamps.

Lead response time FAQ

What is lead response time?

The measured interval between an enquiry arriving and your reply reaching the customer. It is the number behind the speed-to-lead concept, and the value of separating them is that a measurement can be instrumented wrongly in ways a strategy cannot.

Why should I not use the average response time?

Because the distribution is heavily skewed. Most enquiries in working hours are answered quickly and a few take days, so the average describes nobody's actual experience. Use the median for the typical case and the 90th percentile for the bad case.

When does the clock start?

When the form was submitted or the call was placed, not when your CRM ingested it. Measuring from ingestion hides polling delay - a five-minute sync interval quietly adds an average of two and a half minutes to every enquiry before anyone has done anything wrong.

What response time target should I set?

By channel, based on what the customer expects: phone now, text within minutes, web form within minutes to an hour, email within hours. Set the target at what you can hit at the 90th percentile - a target you meet half the time is a wish.

What causes slow responses in practice?

Almost never people deciding to be slow. It is enquiries nobody saw: arriving out of hours, landing in a shared inbox with no owner, or sitting unclaimed while everyone assumes someone else has it. Automatic escalation after a fixed interval fixes more of this than training does.

Should I measure before automating?

Yes, for at least two weeks. A before number that nobody disputes is far more persuasive than any projection, it costs nothing but two timestamps, and it is the only way to prove afterwards that the automation was worth what it cost.

Primary source

Harvard Business Review - The Short Life of Online Sales Leads

Checked August 2026. Anything priced or rate-limited moves, so verify against the source before you budget.

Want this built rather than explained?

Knowing what lead response time means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.