Have you ever requested a service, heard nothing for a while and then received a call after you had already spoken to somebody else? From the business’s side, that may look like a poor lead. From the customer’s side, it may simply look like a slow response.
When deciding how quickly to respond to a new sales enquiry, I would think about what the customer needs and what your team can reliably deliver. A useful acknowledgement matters, but the person also needs to know when somebody will actually help. Clear ownership and realistic expectations make that promise workable.
In this guide
Match the response to the request
The right response begins with the type of request. Someone asking about urgent availability needs a different answer from a business arranging a complex proposal for next month. Both deserve clarity, but they do not need the same timetable for every part of the work.
An initial message can confirm receipt and explain the next step. If more time is needed to prepare a quote, say so. The customer is less likely to feel forgotten when they understand what is happening.
I would avoid advertising a response promise that depends on everyone being available all the time. Look at staffed hours, absence cover and the channels your team monitors. Build the expectation around those realities, then improve the process where you can.
For enquiries outside working hours, explain when review resumes. For an enquiry during staffed hours, make sure it reaches an available person. Speed is useful when it leads to relevant assistance; an instant generic message should not hide a delayed human response.
Separate acknowledgement from actual assistance
An automated receipt can confirm that the form worked and state the next step. It does not mean the customer has been helped. Track submission time, acknowledgement time and first meaningful response separately so your dashboard reflects the experience.
The first human response should refer to the service requested and provide a relevant question or answer. Avoid asking the person to repeat everything already submitted. If more information is needed, explain why and make it easy to provide.
Give every enquiry an available owner
Route enquiries to the right team and assign a named person. Create a fallback when someone is off duty or unavailable. Alerts should reach the responsible employee through the work tools they actually use, while preserving appropriate access to customer information.
Check the entire handover with labelled tests. A CRM record without an alert or next action can still be missed. When ownership changes, the new person needs the relevant conversation history, appointments and pending work. See preventing website-to-sales lead loss.
Set targets by staffed and unstaffed periods
Choose an initial-response target your team can meet, then review it against outcomes. For illustration, a company might target 15 minutes during staffed hours and a reply at the start of the next working period overnight. Your target should reflect the service your team can reliably provide.
Make the timetable explicit for customers in different time zones. If offering callbacks, show the date, local time and time-zone label. Ensure confirmations, calendars and reminders refer to the same appointment.
Measure the cases that hide delays
Report median response time and the number of enquiries waiting beyond your target. Averages alone can conceal a small group left waiting for days. Review missed calls, failed notifications and records without owners.
Compare response time with connected conversations and sales outcomes, while recognising that service fit also matters. Improve staffing, routing or expectations where the evidence points. Pair faster handling with useful automated follow-up, rather than sending repeated generic messages.
A response target your team can actually use
Imagine you set a target to respond promptly during staffed hours. The target sounds straightforward until an enquiry lands while the assigned employee is on leave. If there is no fallback, the customer waits even though another person could help.
That is why I would define the process alongside the target. Which queue receives the enquiry? Who owns it? How is absence handled? What should happen if the alert fails? A target without those answers is only a number on a document.
Track the time to the first meaningful response separately from the receipt email. A message saying we received your form does not answer a service question or arrange the conversation. Both events are useful, but they describe different parts of the experience.
At the review, look at the oldest waiting records as well as the average. A few enquiries left unanswered for days can disappear inside a reasonable average. Ask what prevented the response and fix the recurring cause.
Do not make faster contact feel rushed or irrelevant. The employee should see the customer’s original answers and begin with the requested service. A quick call that ignores the enquiry can still lose trust.
Fill out the customer acquisition plan form if you want help connecting response expectations with staffing and lead routing. Tell us when enquiries arrive and what happens when the usual closer is unavailable.
Frequently asked questions
Does an automatic email count as a response?
It counts as acknowledgement. Measure the first useful human response separately so you know when the customer actually receives assistance.
Should we contact customers late at night?
Respect their preferences and appropriate contact hours. Use a receipt and a clear next-working-period expectation when your team is unavailable.
What should happen when the assigned closer is absent?
Route the enquiry to an available backup with its history and next action. Avoid leaving responsibility ambiguous between two people.
Ready to work on this for your business?
If you would like me and the DIL team to help you put this into practice, fill out the customer acquisition plan form. Tell us where you are now and what you want to improve, so we can start with your situation.