How quickly should a business respond to an enquiry?
A new enquiry is a brief moment of intent. Somebody has recognised a need, found your business and decided to make contact. Yet in many established service firms, that moment enters a shared inbox and begins to age.
How quickly should the business respond? The practical answer is: acknowledge immediately where appropriate, make meaningful human contact as soon as the operating model allows, and never sacrifice relevance merely to produce an impressive stopwatch figure.
Speed matters because attention moves. It is not the whole answer because customers can recognise a hollow automated response. The goal is not simply to be first. It is to create confidence and momentum.
What the evidence says about response time
One of the most frequently cited studies of online leads was published in Harvard Business Review in 2011. Researchers audited the response practices of more than 2,000 US companies and examined millions of leads. They found that businesses attempting contact within an hour were nearly seven times more likely to qualify a lead than those waiting even one hour longer, and far more likely than those waiting 24 hours or more.
The study is older, US-based and not a promise that every market behaves identically. It remains useful because the underlying behaviour has not disappeared: an active buyer is easier to engage while the need and context are fresh.
Modern expectations have arguably become more demanding. Customers can compare several providers quickly and may submit multiple enquiries in one sitting. A slow response creates room for another business to define the conversation.
For UK service businesses, a sensible target is not a universal number imposed without context. Emergency repairs, legal advice, consultancy and a complex commercial tender have different rhythms. The right service standard should reflect urgency, opening hours, buying cycle, staffing and the promise made on the website.
Separate acknowledgement from human response
Many teams confuse an automatic receipt with a complete response. They are different.
An acknowledgement confirms that the enquiry arrived. It can be immediate and automated. A good one should:
use the person's name if it was supplied accurately;
confirm what was received without exposing sensitive details;
explain when a person will respond;
provide a useful next step, such as booking a suitable call;
offer an urgent route where genuinely necessary; and
sound like the organisation, not generic software.
A human response shows that somebody has understood the enquiry. It refers to the customer's situation, asks an intelligent question or proposes an appropriate next action. If the acknowledgement promises contact by 10am the next working day, the system and team must make that promise visible and achievable.
The dangerous middle ground is an automated email that sounds personal but does nothing useful: “We value your enquiry and will be in touch shortly.” Shortly is not a service level.
The first useful response
For a straightforward enquiry, the first useful response often needs four elements.
Recognition: Show that the business understands the request. A single relevant sentence can distinguish a considered reply from a template.
Expectation: Explain what happens next and when. Uncertainty creates unnecessary follow-up calls and frustration.
Qualification: Ask only for information genuinely needed to determine fit or prepare the next conversation. Do not turn the first interaction into an interrogation.
Action: Give the prospect a clear route: choose a call time, send a document, answer one key question or expect a named person to contact them.
The response should reduce effort for both sides. “Call us when you can” transfers all responsibility back to the prospect. A choice of two next steps is usually more helpful.
Where delays actually happen
Slow response is rarely caused by laziness. It is usually a systems problem.
Enquiries may arrive through website forms, direct email, telephone calls, social messages, webchat and third-party platforms. Each channel has its own notifications. Team members assume somebody else is watching. Important details are missing. Ownership depends on geography, service or availability but the routing rules are unclear.
The result is a queue that nobody can see.
A connected enquiry process should create one shared record, preserve the source, apply simple routing rules and create a visible next action. If the normal owner is absent or the deadline is approaching, an escalation should alert somebody else. The team should not have to search every channel to discover demand.
Design a response standard the team can keep
Begin with real operating conditions. Review several months of enquiries and answer:
Which channels produce worthwhile opportunities?
When do enquiries usually arrive?
What information is needed for a useful first response?
Who is qualified to respond?
What happens outside opening hours?
When should an enquiry be escalated?
What counts as contacted, qualified or closed?
Then define two measures: time to acknowledgement and time to meaningful human response. Median performance can hide neglected enquiries, so also track the proportion handled within the service standard and the oldest open enquiry.
For example, a business might acknowledge web enquiries immediately, commit to meaningful contact within two working hours during published hours, and provide a clear next-working-day expectation outside them. The exact standard matters less than making it honest, visible and consistently owned.
Use automation to protect, not impersonate
Automation is valuable at the predictable edges of the journey. It can acknowledge receipt, notify the right person, create a task, provide a booking link, request missing information and remind the team before a deadline.
It should not invent understanding. Avoid statements such as “I have reviewed your requirements” unless a person has. Do not continue chasing somebody who has replied, booked or opted out. Do not send the same cadence to a distressed customer and a routine prospect.
Under UK data-protection and electronic-marketing rules, organisations must also consider the purpose and lawful basis for communication. A service response to a requested enquiry is different from adding that person to ongoing promotional messages. The ICO recommends planning direct marketing compliance in advance and making opt-out choices clear.
Why relevance sometimes beats immediacy
A rushed response can damage trust. If a complex commercial enquiry arrives at 4.55pm, a useful acknowledgement with a specific promise may be better than an immediate generic sales call from somebody without the right knowledge.
Speed should be judged from the customer's perspective. Did the business confirm receipt? Did it set a dependable expectation? Did the eventual response understand the need? Did each handover retain context?
This is why response time and customer journey design belong together. Faster notification will not fix unclear qualification, weak ownership or poor handovers.
Follow-up is part of the response
Many opportunities do not progress after the first exchange. The prospect becomes busy, needs another decision-maker or is comparing options. A disciplined follow-up process protects value without becoming intrusive.
Every open opportunity should have a next action and date. Follow-up should add value: answer an unresolved question, summarise the decision, share a relevant example or make the next step easier. Repeating “just checking in” five times is activity, not service.
The system should also know when to stop. Respect a clear no, keep marketing permissions separate and record the reason an opportunity closed. Closed-lost information can reveal patterns in price perception, timing, fit or response quality.
A practical improvement plan
For the next two weeks, record every enquiry, source, arrival time, first acknowledgement, first human response, owner, next action and outcome. Do not begin by buying another tool. Observe the actual journey.
Look for missing enquiries, repeated delays and stages where ownership becomes ambiguous. Agree one service standard, one shared view and one escalation rule. Automate only the simple, repeatable steps. Review performance weekly until the process becomes normal work.
The best response process feels calm. Customers receive clarity, staff know what to do and managers can see exceptions before they become lost opportunities.
Frequently asked questions
Should every enquiry receive an immediate phone call?
No. Follow the customer's chosen channel, urgency and context. An immediate acknowledgement plus a scheduled, informed response may be more appropriate.
What if the team cannot respond quickly outside working hours?
Say so clearly. An honest acknowledgement with published hours and a specific next-working-day promise is better than pretending 24-hour availability.
What should we measure besides speed?
Track contact rate, qualification rate, appointments, conversion, reasons for loss and whether every open opportunity has a next action.
