Measuring lead response time
How to define lead response time consistently
By ByTomorrow · Published
A team can report a faster response time simply by counting automatic acknowledgments as answers. Another can appear slower because it includes overnight hours while the first counts only staffed time.
Define the metric before comparing performance. This specification is an editorial worksheet using fictional arithmetic examples. It provides no industry benchmark or claim about ByTomorrow results.
What to distinguish
Avoid these misleading shortcuts
Different events share one name
Receipt acknowledgment, a useful reply, a callback attempt and a connected conversation are different milestones.
Unanswered inquiries vanish from the average
A report calculated only from answered inquiries can improve while an untouched queue grows. Show unresolved cases separately.
Working worksheet
Make the rule and evidence explicit
Choose the start event
Record inquiry ID, channel, accepted-receipt timestamp, time zone and evidence reference. For a web form, decide whether the start is successful backend acceptance or another documented event. Do not use the time a staff member finally opened it.
Define the qualifying response
Write the exact event that stops the clock. Suggested definition: the first permitted response that addresses the request or asks an action-relevant question. Track automatic acknowledgments separately. If a connected conversation is the goal, use a different metric from an attempted callback.
Keep elapsed and staffed time separate
Elapsed time is qualifying-response timestamp minus start timestamp. Staffed time counts only the agreed coverage intervals intersecting that period. Publish the coverage schedule, time zone and holiday handling alongside the result.
Fictional worked calculation
A request arrives Tuesday at 16:55 and receives a qualifying reply Wednesday at 09:10. With illustrative weekday coverage from 09:00 to 17:00, elapsed time is 16 hours 15 minutes; staffed time is 15 minutes. Neither figure is a target or a measured customer result.
Report unresolved and unmatched cases
Use columns: inquiry ID; start; qualifying response or unresolved; elapsed time; staffed time; evidence; exclusion reason. For a period report show the total eligible inquiries, answered count, unresolved count and unmatched records. Do not turn an absent response into zero minutes.
Preserve the original inquiry start
Link repeated messages about the same unresolved request rather than resetting the clock to the latest message. Record a genuinely new request separately under an agreed rule. Keep the evidence that supports the linkage.
Use and verify
Check the result in the actual workflow
Approve the definition
Have the operations and reporting owners agree the event rules and coverage schedule.
Reconcile sample traces
Use original receipt and response records. HighLevel workflow logs can help trace actions but do not define business success by themselves.
Calculate both time measures
Use the same records and label the measures clearly.
Inspect unanswered cases
Treat unresolved work as operational information, not an inconvenient omission.
Freeze definitions for comparison
Record any change in counting before comparing periods so improved numbers do not hide a new definition.
Questions
Straight answers.
Only for an explicitly named acknowledgment-time metric. Keep that separate from a useful-response or connected-conversation measure.
This worksheet measures time. It does not establish response quality, correct advice or customer satisfaction. Review those independently.
A funnel counts outcomes at successive stages. This definition measures the interval between two specific events and makes unanswered work visible.
Sources and further reading
- HighLevel workflow execution logs
HighLevel documents workflow execution and enrollment history for tracing actions. A reporting definition still needs to identify which observed event counts as a response.
Checked .
Bring one process to review
Use the worksheet with your existing records and tools. Agree on the expected behavior, owner and verification before making a change.
Discuss your workflow