Measuring lead response time

Separate acknowledgment from substantive response

Define the start and end of the response-time measure. An automated confirmation can reassure the sender but is not the same as a person addressing the enquiry. Record when the request was accepted, when it was assigned and when a meaningful response occurred. Account for the business's stated operating hours when interpreting the result.

Worked example

Illustrative scenario; not a claim of measured client results.

If a form sends an instant receipt but the first relevant reply arrives two working days later, report both facts separately. The receipt confirms delivery; the later reply reflects sales handling. Review whether delays occur during assignment, qualification or individual follow-up. This makes the measure useful for process improvement rather than a flattering automation statistic.

Checks, limitations and next decisions

Check timezones and timestamp consistency before comparing records. Avoid publishing a response promise the team cannot reliably meet. For sparse volumes, inspect individual delayed cases instead of relying only on an average that hides extremes. Improve ownership and escalation where requests stall, and verify that the measurement itself is based on actual accepted enquiries rather than button clicks.

A practical starting point

Work through these checks in order. Use the results to decide what needs to change in your own workflow.

1. Record the accepted enquiry time and first meaningful response.
2. Define working hours and escalation responsibilities.
3. Review slow cases by channel and team workload.

A mistake to avoid

Do not compare teams without accounting for working-hour definitions.

How to check progress

Track median and slow-tail response times alongside lead progression.