Want help applying this guide?Ask the DripTell team
A buyer asks a bakery for a catering price at 10:02. An automatic message confirms receipt at 10:02, the enquiry enters a shared queue at 10:04, and a coordinator answers the actual question at 10:37. Which time is the lead response time?
The useful answer is 35 minutes from the valid enquiry to the first meaningful sales response. The instant acknowledgement is still worth recording, but it should not stop the sales clock. Neither should routing, assignment, an attempted call, or a change of lead stage.
This distinction matters because a dashboard can report impressive speed while buyers are still waiting for help. A fair measurement separates system activity from customer progress and makes the rule easy for salespeople to apply.
Start the clock when a valid enquiry arrives
Choose one arrival event that represents an actionable sales enquiry. It might be a completed website form, a direct message asking about a product, a connected inbound call, or an email with enough information to identify a sales request. Record its original timestamp before enrichment, deduplication, routing, or business hours logic changes the record.
- 1Capture the enquiryPreserve the earliest valid arrival before routing or enrichment changes the record.
- 2Record acknowledgementTrack automatic confirmation as delivery evidence without stopping the response clock.
- 3Accept ownershipStore assignment and explicit acceptance as separate internal operating events.
- 4Deliver useful progressStop the customer clock only when the buyer receives an answer or credible next step.
- 5Audit the evidenceConnect the metric to the original conversation and retain every exclusion reason.
Do not start from CRM creation if the CRM receives the lead later. Do not restart after reassignment. If two channels belong to the same person and request, preserve the earliest valid event and link the later events to it. A reliable sales operating model needs one customer clock even when several systems touch the enquiry.
Define exclusions narrowly. Spam, test submissions, duplicate delivery of the same event, and messages with no sales intent can be excluded with a reason. Missing fields should not automatically make a genuine request disappear from the denominator.
Stop the clock at the first meaningful response
A meaningful response moves the buyer toward an answer or a next step. It may answer the question, ask one necessary clarifying question, offer a relevant appointment, confirm availability, or explain who has accepted ownership and when a substantive answer will arrive.
An automatic acknowledgement proves the channel worked. It does not prove that the business understood the request. A routing event proves that software selected a destination. Assignment proves that a name was attached. None of those events should end the lead response clock unless the automation can safely complete the requested task and that outcome is recorded.
Microsoft's work assignment overview shows that lead assignment can be automated through segments, sequences, and assignment rules. That makes assignment a useful operating event, but it is not evidence that the buyer received an answer. Keep the end to end measure from enquiry arrival.
Keep the events separate in your data
Store the journey as events rather than one overwritten response field. Each event needs a lead identity, enquiry identity, event type, timestamp, actor, channel, source system, and confidence or validation state. This gives the shared inbox and the customer record the same sequence to inspect.
| Event | What it proves | Stops the customer response clock | Useful separate measure |
|---|---|---|---|
| Valid enquiry received | A buyer made an actionable request | No | Enquiry volume and source quality |
| Automatic acknowledgement sent | The system confirmed receipt | No | Acknowledgement delivery time |
| Lead assigned | A routing rule selected an owner | No | Time to assignment |
| Owner accepted | A person accepted responsibility | No | Time to ownership |
| Contact attempt made | The team tried to connect | Usually no | Time to first attempt |
| Meaningful response delivered | The buyer received useful progress | Yes | Lead response time |
| Lead qualified | Evidence met the qualification rule | No separate clock | Time to qualification |
An unanswered call needs special treatment. It can stop a time to first attempt measure, but it usually should not stop the customer response clock. If the salesperson leaves a useful voicemail or message that addresses the request and gives a clear next step, record that content and apply the same meaningful-response rule.
Measure ownership and qualification on their own clocks
The customer response clock should not carry every sales operating question. Track time to assignment, time to accepted ownership, time to first attempt, time to meaningful response, time to connection, and time to qualification separately. Those intervals reveal different failures.
Microsoft's lead qualification documentation shows that qualification behavior can be configured and that record creation may be controlled by a seller or by automation. That is a good reason not to use qualified status as proof of a first response. Qualification describes a business decision about evidence and fit. Response describes what the buyer received.
Use workflow automation to write explicit events and stop conditions, not to overwrite the original arrival. If ownership changes, retain every assignment and acceptance event. The new owner may need a fresh internal acceptance clock, while the buyer's end to end response time continues from the original enquiry.
Build an auditable response report
Start with eligible enquiries, then show the median, the 90th percentile, the share answered within the agreed threshold, and the oldest still unanswered lead. Break results down by source, channel, staffed hours, team, owner, and enquiry type. Always display the denominator and exclusion reasons.
Audit a sample of conversations each week. Check whether the recorded first response actually addressed the enquiry, whether auto replies were misclassified, whether duplicate leads reset the clock, and whether agents changed timestamps or stages to improve a report. The reporting view in inbox analytics should lead a reviewer back to the underlying conversation.
Agree on business hours before calculating an SLA view. Keep raw elapsed time as well. A lead arriving at night may have a short staffed-hours response and a long human wait; both are true and useful. Protect the event history with appropriate security controls, especially when users can edit owners or stages.
For the bakery enquiry, the final record remains simple. Arrival was 10:02, acknowledgement was 10:02, assignment was 10:04, ownership was accepted at 10:10, and the meaningful reply was 10:37. Report acknowledgement in seconds, assignment in two minutes, ownership in eight minutes, and customer response in 35 minutes. No event has to pretend to be another.
Frequently Asked Questions
Does an automatic reply count as lead response time?
Not when it only confirms receipt or states opening hours. Count it as acknowledgement time. Stop the response clock only when the message answers the request, asks a necessary question, or provides a credible owned next step.
When should the lead response clock start?
Start when the earliest valid sales enquiry reaches a controlled channel. Preserve that timestamp through enrichment, deduplication, routing, assignment, and reassignment.
Does an unanswered call stop the response clock?
Usually no. It stops a first-attempt clock. A useful voicemail or connected-channel message may count if it gives the buyer relevant progress and a clear next step.
Should qualification end the response measurement?
No. Qualification and response answer different questions. A lead can be qualified automatically before anyone helps the buyer, or receive a useful answer before the business has enough evidence to qualify it.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy