Lead Response Time: Definition, Formula & Benchmarks
Lead response time is the elapsed time between an inbound inquiry and the first human sales response attempt. It measures responsiveness, not whether the buyer answered or became qualified. Define the start and end events before comparing teams or tools.
Formula: first human response attempt timestamp − inquiry received timestamp. An automated acknowledgment is useful communication, but report it separately from a human response.
Response time, contact time, and qualification time
Consider an illustrative request received at 10:00 a.m. A rep attempts a call at 10:07, reaches the buyer at 10:20, and completes qualification at 10:35. First-attempt response time is seven minutes; time to live contact is 20 minutes; time to qualification is 35 minutes. Combining these measures makes a report difficult to interpret.
A call attempt and a personalized email may both count under your policy. State which channels qualify and apply the definition consistently. Do not reset the start timestamp when the request is reassigned, imported, or duplicated.
Report the median, tail, and unanswered requests
An average can hide a small group of severely delayed requests. Report the median, a tail measure such as the 90th percentile, and the number of requests with no human attempt.
Illustrative completed response times of 1, 3, 7, 20, and 60 minutes have a median of seven minutes. Using the nearest-rank method, the 90th percentile is 60 minutes in this tiny example. Other percentile methods can yield different values, so document the method and avoid comparing incompatible reports.
Unanswered requests do not have a completed response time. Do not record them as zero or silently exclude them from the operational report. Show their count and current age alongside the completed-time distribution.
Elapsed time versus staffed-hours time
Suppose staffed hours are Monday–Friday, 9 a.m.–6 p.m. in the relevant team time zone. A request arrives Friday at 5:55 p.m. and receives a response Monday at 9:05 a.m. Elapsed response time is 63 hours and 10 minutes; staffed-hours response time is 10 minutes. This is an illustrative calculation, not a recommendation to wait through the weekend.
Both measures answer useful questions. Elapsed time describes the buyer’s wait; staffed-hours time helps assess execution against your coverage policy. Publish both when out-of-hours requests are material, and explain holidays, time zones, and coverage gaps.
How to set a lead response target
There is no universal target that is right for every inquiry. Segment explicit demo requests, pricing questions, event inquiries, and content downloads. Consider buyer expectations, staffing, account fit, and the action requested. Agree an owner, fallback route, and escalation rule for high-intent inquiries.
Treat a proposed target as an operating policy to test. Review meetings held and qualified evaluations alongside response speed. A fast generic response can satisfy a timer while failing to help the buyer.
A practical response-time audit
- Confirm that the original inquiry timestamp is captured accurately.
- Inspect assignment delays separately from rep action delays.
- Check requests with missing owners and unavailable reps.
- Test a duplicate inquiry and an ownership change.
- Separate automated acknowledgments from human attempts.
- Review the oldest unworked requests, not only the average.
- Compare outcomes within similar inquiry types and coverage windows.
A useful weekly review asks where requests waited, who owned the gap, and what process change would prevent recurrence. Avoid attributing every delay to the rep when routing or notification failed.
Make the next response useful
Give the rep the requested topic, source, account context, previous interactions, and a clear next action. The buyer should not have to explain their request again. Use the filled inbound sales playbook to define the handoff and lead qualification distinctions to avoid treating every inquiry as an opportunity.
Cold outbound outreach is a separate motion. Use the outbound sales definition to keep those reports distinct.
If you are implementing this process in Salesforce, explore Revenue.io’s lead response workflow. Request an inbound lead response demo to review ownership, routing, and handoff, then compare the platform plans against those requirements.