Lead response time is useful only when the team agrees on what starts and stops the clock. A form submission, CRM creation, automatic email and meaningful human reply are different events. Measuring whichever timestamps happen to be easiest can make a slow handoff look fast.
The following is an operational measurement framework, not a claim that one universal response target fits every business. A small consultancy, an enterprise sales team and a local service company have different coverage and enquiry types. Use a definition your team can maintain before adding a target.
Define the four timestamps
- Received: when the enquiry first reaches your controlled form or inbox.
- Assigned: when someone becomes responsible for it.
- Acknowledged: when the sender receives an automatic receipt, if you use one.
- Human response: when a team member makes the first relevant reply or documented contact attempt.
Keep acknowledgement separate from human response. A receipt saying “we got your message” helps the visitor, but it does not prove anyone has understood the enquiry. If your team counts a phone attempt as a response, document that choice so email-led and phone-led teams are compared consistently.
Use elapsed time and staffed time together
Elapsed time describes the customer's wait. Staffed time describes the portion of that wait within your defined coverage hours. Both can be useful, but neither should silently replace the other.
Consider a fictional enquiry received Friday at 16:50 and answered Monday at 09:10. With coverage Monday to Friday, 09:00–17:00, and no intervening holidays, elapsed time is 64 hours 20 minutes. Staffed time is 20 minutes. Reporting only one number hides a different part of the story. Keep timezone and holiday rules explicit, especially when teams work across regions.
Start with a small report
| Field | Purpose |
|---|---|
| Enquiry identifier | Trace the record without putting personal details in shared screenshots |
| Received and assigned times | Separate routing delay from response delay |
| Owner and queue | Identify where an unanswered enquiry is waiting |
| First human response | End the response clock consistently |
| Elapsed and staffed minutes | Show customer wait alongside coverage |
| Still unanswered | Prevent open enquiries from disappearing from the report |
Do not average away the unanswered enquiries
A report containing only answered leads can look excellent while the hardest enquiries remain untouched. Display the unanswered count and the age of the oldest open enquiry next to response-time summaries. Split by enquiry type only when each group has enough records to be meaningful.
Use the median to describe a typical answered enquiry, then inspect the slow end of the distribution and its actual records. A single average cannot tell you whether everyone waits moderately or a small group waits far too long.
Turn the report into one operational change
Review a few slow records with the people who handled them. If received-to-assigned time dominates, work on routing and backup ownership. If assigned-to-response time dominates, examine coverage, workload and the information needed to answer. Avoid demanding faster replies before finding where the delay occurs.
For each change, name an owner, a review date and a visible outcome. For example: “Unassigned enquiries appear in a shared queue checked at the start and end of each staffed day.” This is a proposed workflow, not a performance guarantee.
Check data quality before judging people
Duplicate submissions, imported historical contacts and reopened conversations can distort the clock. Preserve the original event and document any exclusion rather than overwriting timestamps. The duplicate-lead review guide covers why records should be checked before merging. If enquiries vanish before assignment, begin with the form-to-CRM handoff.
