Lead Response Time

Lead response time is the time between a lead arriving and your team's first qualifying response. For an inbound sales report, a useful starting definition is the interval from the original request to the first human outreach attempt. Keep the time to an actual conversation separate: a call that rings out is an attempt, not a connection.

“Speed to lead” is often used for the same idea. The name matters less than the two events your report subtracts. A fast response measured from assignment can hide a long wait before anyone received the lead.

Choose the clock before comparing the numbers

Write down what starts your clock. For a demo request, use the original form submission time, not a later CRM import or assignment. For a new inquiry from an existing contact, keep the inquiry's timestamp; the contact's creation date could be years earlier.

Then decide what stops it. This guide uses a human rep's first call attempt or personal email or chat response. Keep automatic acknowledgments in a separate measure. “We received your request” can be helpful without meaning a salesperson has followed up.

Check your CRM's definition before borrowing a report. HubSpot's Lead response time report, for example, measures from assignment to the current owner's first qualifying engagement. Its listed engagements include task progress or completion, and reassignment resets the time. That's a different question from how long a buyer waited after submitting a request.

Split the wait into useful parts

Keep these four timestamps for each inquiry:

1. Received: the request entered the business.
2. Assigned: a rep or team became responsible for it.
3. First human attempt: a rep made the first qualifying outreach attempt.
4. First connection: the team reached the intended person in a two-way exchange.

End-to-end response time = first human attempt − received time. Assignment delay is assigned time minus received time. The rep's wait is first attempt minus assigned time. Together, those two intervals explain the end-to-end wait when assignment happens before outreach.

Don't overwrite the original receipt or first assignment when a lead changes owners. Keep those events and add the reassignment. Otherwise, moving an old lead to a new rep can make a slow process look quick. Flag attempts recorded before receipt or assignment for review instead of silently converting negative intervals to zero.

A four-lead example

Imagine four inbound requests arrive at 10:00 a.m. on a staffed weekday. You review them at 11:00 a.m. These are illustrative records, not Trellus customer data.

• Lead A: assigned at 10:01, first call at 10:04, connected at 10:12. Response time: 4 minutes. Time to connection: 12 minutes.
• Lead B: assigned at 10:12, first call at 10:15, no connection by 11:00. Response time: 15 minutes; connection time is still unknown.
• Lead C: assigned at 10:03, first personal email at 10:31, replied at 10:33. Response time: 31 minutes. Time to connection: 33 minutes.
• Lead D: assigned at 10:02, no human attempt recorded by 11:00. Response time is incomplete; the lead has been waiting for 60 minutes.

Among the three attempted leads, the median response time is 15 minutes. But the assignment-to-attempt median is only 3 minutes: the individual waits are 3, 3 and 28 minutes. Neither median shows Lead D, and the shorter one hides Lead B's assignment delay.

A useful report would therefore show 3 of 4 leads attempted, or 75% coverage, beside the median. It would also show one unattempted lead aged 60 minutes. If the team's own example target were an attempt within 15 minutes, 2 of 4 eligible inquiries met it: 50%. That target is an illustration, not an industry benchmark.

The two recorded connections are a separate outcome. For phone outreach, contact rate helps describe whether attempts reach people; it doesn't replace the response-time clock.

Elapsed time and business-hours time tell different stories

Suppose a request arrives Monday at 4:55 p.m. and receives its first attempt Tuesday at 9:10 a.m. If the team's stated coverage is 9 a.m.–5 p.m., Monday through Friday, with no holiday involved:

• Elapsed response time: 16 hours, 15 minutes.
• Business-hours response time: 15 minutes—five on Monday and ten on Tuesday.

Both are valid when labeled. Elapsed time captures the buyer's total wait. Business-hours time evaluates response within the team's staffed window. Publish the calendar and time zone, including holidays, and use the same rules each period. Don't quietly discard overnight leads to make the report look faster.

Build a report that keeps missing responses visible

Start with inquiries received during a stated period, not just the leads someone contacted. Deduplicate repeated records of the same inquiry while keeping genuinely new requests separate. Document any excluded spam, test entries or requests outside your sales team's scope, and show how many you excluded.

For that group, report the median response time among attempted leads, attempt coverage, and the number and age of leads still waiting. Keep missing activity data separate from a confirmed absence of outreach. A blank timestamp may mean nobody called—or that the call never reached the report.

When comparing days or teams, give each group the same observation window. Today's newest leads haven't had as long to receive a response as yesterday's. An open queue needs a live view; a performance comparison needs a stated cutoff.

Review a few slow records before changing the target. A long received-to-assigned interval points toward assignment or staffing. A long assigned-to-attempt interval calls for a look at the rep's queue and availability. Quick attempts with few conversations require a different investigation.

If calls are part of that workflow, compare the recorded attempt with the CRM activity before trusting the total. Our guide to reconciling dialer and CRM call counts walks through that check. For teams already calling from HubSpot, the Trellus HubSpot walkthrough shows the list-to-call-to-saved-activity workflow. Use your lead-source and CRM records to establish when an inquiry arrived and who owned it.

Method: original measurement framework and fictional examples from Trellus. HubSpot's report definition was checked on October 5, 2026. No customer dataset or inbound-routing product test is presented.