
Lead Management
Speed-to-Lead: Respond to New Enquiries Reliably
Respond to new enquiries reliably with explicit ownership, achievable deadlines and reporting that keeps unanswered cases visible.
Short answer
Speed-to-lead describes the time between a new enquiry and the first response. A useful operating process distinguishes an acknowledgement, a substantive reply and an agreed next step. Every enquiry needs an owner, a realistic response deadline and a fallback if that person is unavailable. Sending an automated message alone does not demonstrate that the enquiry has been handled successfully.
Key takeaways
- Acknowledgement, substantive reply and an agreed next step are separate events.
- Assignment alone is not enough: somebody must visibly accept the enquiry.
- Business hours measure internal deadlines; calendar time shows the actual wait.
- Unanswered enquiries must not disappear from the report.
A fast acknowledgement can hide a slow process
A prospect requests a consultation through your website. Seconds later, she receives “Thanks, we will be in touch.” Internally, three people receive the notification. One is in a meeting, another is on holiday and the third assumes somebody has taken over. By the following morning, no conversation has been arranged.
This is a fictional example, but it provides a specific test: would your dashboard call this a fast response? If so, it may be measuring the automation rather than the prospect's experience.
The first message can be automatic. Responsibility for the enquiry cannot be left undecided.
This guide covers the journey to the first useful reply. The subsequent contact sequence belongs in the lead follow-up system guide. Keeping that boundary makes it clear which part of the process you are improving.
Track three separate events
Decide what stops each timer before configuring the technology. The definitions below are our recommended operating model, not a universal industry standard.
Event | What counts as achieved | What is not enough |
|---|---|---|
Enquiry acknowledged | A message confirms the specific request and sets an expectation for the reply | An internal team notification |
Substantive reply sent | A reply addresses the request or asks a necessary, specific follow-up question | Generic thank-you email, unanswered call attempt, internal note |
Next step agreed | An appointment, callback or further action has been agreed with the prospect | A booking link that nobody has used |
A helpful AI response may qualify as the second event. Record whether AI or a person produced it, and assess its accuracy separately. Otherwise a fast but incorrect answer becomes indistinguishable from a useful one in your report.
Zendesk offers a useful reference for defining the metric: its “First reply time” ends with a public agent response and excludes automated actions. That describes Zendesk, not necessarily your CRM's reporting behaviour. Zendesk: How first reply time is calculated
Unanswered enquiries belong in the report
In its 2025 Buyer First Report, Chili Piper reported no response from 16% of the companies reviewed. The vendor study covered 100 large B2B SaaS companies and used alias email addresses for demo requests. The exact observation window is unspecified. This is neither representative of Germany nor evidence for an ideal response deadline.
No response is a separate category
Share of reviewed companies · 25 April 2025 · observation window unspecified
- No response16 %
- Remaining companies84 %
View data table
| Category | Share of reviewed companies |
|---|---|
| No response | 16 % |
| Remaining companies | 84 % |
84%: calculated as 100 − 16, not a deadline-compliance rate.
Source: Chili Piper · Buyer First Report · 25 April 2025 · observation window unspecified. 100 large B2B SaaS firms; vendor research using alias enquiries.
Not representative of Germany; does not measure an intervention's effect.
For your own reporting, ask a practical question: what happens to an enquiry without a reply timestamp? If that row disappears from the calculation, the average can look healthy while work remains unattended. Show open cases and their age alongside response times for completed replies.
Set a response deadline you can keep
This source does not establish a magic minute threshold for your business. Start with what you can reliably promise customers. An immediate consultation is different from responding to a bespoke quote request that requires reviewing documents first.
Business hours and the actual wait
Define a coverage calendar with a time zone, working days, holidays and backup staffing. The internal deadline can run only during staffed hours. Keep total elapsed time visible as well: it represents the customer's wait. Zendesk also documents this distinction as business and calendar hours. Zendesk: Reporting reply time within business hours
A fictional example: your team covers enquiries Monday to Friday, 9 am to 5 pm. A request arrives on Friday at 4:50 pm. With an internally agreed allowance of 60 business minutes, the response would be due on Monday at 9:50 am, provided Monday is not a holiday. Total elapsed time would be 65 hours. Both measurements can be correct; they answer different questions.
A short deadline-planning template
Enquiry | Recommended decision before launch | Escalation |
|---|---|---|
Specific request for a conversation | Who can advise, and when will a personal reply follow? | A named backup takes over before the promise expires |
Bespoke quote request | What information is missing, and when will an initial assessment follow? | Ask for missing details instead of promising an unchecked quote |
Existing customer with a service problem | Which team owns it, and how urgent is it? | Hand over to service rather than treating it as a new sales lead |
Fill in actual owners and achievable times. A table full of ambitious deadlines is not yet a service promise your team can keep.

Set up the process in ONE LOOP
Connect the contact record, conversation, task and workflow. The steps below describe the logic to configure. Check which timestamps and business-hour calculations your particular setup already provides; additional reporting may be required.
From arrival to an agreed next step
Preserve arrival
Store the enquiry ID, original timestamp and channel; recognise technical retries.
Secure ownership
A named person visibly accepts the case; define the deadline and backup in advance.
Reply substantively
Address the actual request or ask for necessary details; delivery failures remain open.
Agree the next step
Arrange a meeting or callback; end first-reply reminders while retaining pending follow-up tasks.
Nobody accepts or the message fails?
Assign the exception; do not reset the original wait or promised deadline.
Recommended operating model: the first reply and subsequent handling remain separate tasks.
1. Preserve the original arrival
Store the enquiry ID, entry channel and original arrival timestamp. If a technical retry delivers the same form twice, it must not start a second first-contact sequence. A genuinely new request from the same contact may need its own case. A contact and an enquiry are not the same thing.
2. Make ownership explicit
Assign the case to a responsible person and require visible acceptance, for example through an agreed task status. “Notification sent” does not mean “somebody is handling it.” A backup must be able to see the original request and the conversation so far.
Define a named substitute or actively managed team queue for deadline escalation. Do not pass the case indefinitely between unavailable people. If nobody can take it, notify the responsible manager and review the commitment made to the customer.
3. Send a substantive reply
A useful first response refers to the request and offers a concrete next option. Example template, not a real customer conversation: “Hello [name], to set up your appointment booking, we should first clarify which services you want people to book online. Would [appointment option] work, or would you prefer to send us your service list first?”
Use a channel whose suitability and permission have been checked for this contact. A form submission should not launch simultaneous emails, texts and calls without review. If the message fails technically, keep an exception open. A send attempt proves neither delivery nor that the message was read.
4. End the first-contact sequence deliberately
A substantive reply ends reminders about the missing first response. It does not erase an unresolved appointment request: that needs its own next action. If the prospect replies or books independently in the meantime, the workflow must recheck the current state before sending further messages.
Exceptions the pilot must cover
Ownership changes: Preserve the original arrival and promised deadline. Reassignment must not reset the customer's wait to zero.
One person uses two channels: Check whether it is the same request. Combine context without blindly merging different matters.
The customer asks for later contact: Record the agreed time and reason. Distinguish this from internal delay in reporting; retain the original arrival.
A message fails: Assign the exception. A technical failure must not produce a successful response timestamp.
Spam or test submission: Exclude it from the sales metric with a documented reason. Keep the excluded count visible.
After-hours arrival: State a realistic next coverage time. Check holidays before a template promises “tomorrow.”
Measure improvement without flattering the numbers
Choose an arrival cohort, such as all valid enquiries received during one calendar week. Record the reporting cutoff. Compare weeks at the same observation age, otherwise the newest week has had less time to receive a reply.
Track at least four values: the share answered within the promise, the number still unanswered, the age of the oldest open enquiry and the time to a substantive reply. With enough cases, add a median and a measure of the slowest responses. For low volumes, a visible case list can be more useful than an impressive chart.
Fictional calculation: all response deadlines have expired for 20 valid enquiries by the reporting cutoff. Fifteen were answered on time, two late and three not at all. Deadline compliance is 15 ÷ 20 = 75%, not 15 ÷ 17. You can additionally calculate response times for the 17 answered cases; show the three open cases and their age beside that result. Enquiries whose deadline has not yet expired belong in a separately identifiable group.
An increase in booked conversations does not prove that faster responses caused it alone. Also examine changes in channels, campaigns, enquiry types and staffing capacity.
Start with one entry channel
Begin with a clearly defined form or managed inbox. Rehearse a normal arrival, absence, weekend, duplicate event, failed message and an intervening booking. These are proposed tests, not claimed ONE LOOP test results.
Release the workflow only when every test enquiry has traceable ownership, a deadline and a follow-up action. Keep reviewing open exceptions daily. Once the first response is reliable, connect the lead follow-up system or discuss your enquiry process with us.
FAQ