What Response Time Should a Service Business Actually Aim For?
"As fast as possible" is not a target, and average response time hides the failures that cost you work. A practical way to set a response standard you can actually hold.
Most small service businesses know they should respond to enquiries quickly. Very few have a number.
Asked what their target is, owners typically say "as fast as we can", which is not a target — it is an aspiration with no failure condition. You cannot miss it, so you cannot learn from missing it. And because there is nothing to measure against, the enquiries that took three days to answer never surface as a problem; they simply disappear into the general sense that things are busy.
Setting an actual number is not a bureaucratic exercise. It is the difference between knowing your operation works and assuming it does.
In short: Measure three windows separately — acknowledgement, substantive reply, and resolution — and set a target for each. Track the worst 10 per cent rather than the average, because averages hide exactly the failures that lose you work. And measure in-hours and out-of-hours separately, or the second will be invisible inside the first.
The three windows
Lumping everything into a single "response time" figure is the most common mistake, because it merges three things that behave differently and matter differently.
Acknowledgement is the point at which the enquirer knows a human being — or something acting credibly on a business's behalf — has received their message. It answers one question: did this arrive? Its value decays fast. An acknowledgement within minutes is reassuring; one the next morning is barely better than none, because by then the enquirer has already assumed the worst and acted on it.
Substantive reply is the first message that actually addresses what they asked. Is the property available. Do you treat this. What does it cost. Can you come out on Thursday. This is the window that determines whether the enquiry converts, and it is the one most businesses do not measure at all.
Resolution is the point at which the enquirer has what they need — a booking made, a quote issued, a question answered fully. It legitimately varies with complexity, and it is the least useful of the three as a headline number.
Most businesses that improve their response performance do it by separating acknowledgement from substantive reply and realising that they have been doing the first well and the second badly.
Why the average lies to you
Suppose a business handles a hundred enquiries in a month. Ninety are answered within an hour. Ten sit over a weekend and are answered on Monday, roughly sixty hours later.
The mean response time is about seven hours, which sounds poor. The median is under an hour, which sounds excellent. Neither number tells you the truth, which is that ten enquiries were handled in a way that probably lost most of them.
This is why response time should be tracked at the tail rather than the centre. Look at the worst 10 per cent — the ninetieth percentile — and ask what happened to those. In almost every small service business the answer is the same: they arrived when nobody was working. They are not scattered randomly through the month. They cluster in the evenings, at weekends, and around holidays, which is precisely why the average conceals them so effectively.
If you only ever look at one number, look at that one. It is where the cost of missed enquiries actually accumulates.
Setting a target you can hold
A useful target has three properties: it is specific, it is separated by window, and it distinguishes hours you staff from hours you do not.
A reasonable starting framework for a small service business looks something like this:
- Acknowledgement, in hours: within 15 minutes. Achievable by most businesses without changing anything except intent.
- Acknowledgement, out of hours: within 15 minutes, or explicitly not at all. The important word is *explicitly*. A business that decides not to cover evenings has made a legitimate commercial choice. A business that has not decided, and therefore covers them inconsistently, gets the worst of both — no reliability and no saved effort.
- Substantive reply, in hours: within 2 hours. Long enough to allow for being with a client; short enough to arrive while the enquirer is still deciding.
- Substantive reply, out of hours: within 2 hours, or by 9:30am the following working day. Pick one and publish it internally, so that the standard is a standard rather than a hope.
- Resolution: measured, not targeted. Track it to spot cases that stall, but do not set a blanket number, because a complex enquiry legitimately takes longer than a simple one.
The specific numbers matter less than having them. A business with a published 30-minute acknowledgement target that it hits 95 per cent of the time is in a far better position than one aiming vaguely at "immediately" and achieving it two-thirds of the time.
Measuring it without buying anything
This does not require new software. For most small businesses a month of manual sampling produces a more honest picture than a dashboard would.
Take every enquiry for four weeks — every web form, every portal notification, every WhatsApp message, every voicemail. For each, record the time it arrived, the time of first acknowledgement, and the time of first substantive reply. A spreadsheet with four columns is sufficient.
Then split the results two ways: by channel and by in-hours versus out-of-hours. Both splits tend to be revealing. Most businesses find one channel performing far worse than the rest — often the one nobody owns, such as a shared inbox or a messaging app that lives on someone's personal phone — and nearly all find the out-of-hours picture markedly worse than they expected.
That exercise usually settles the question of whether there is a problem worth solving, and it costs nothing but attention. It also gives a genuine baseline, so that any change made afterwards can be judged on evidence rather than impression.
What to do about the out-of-hours block
Once the measurement is done, the out-of-hours gap is usually the largest single item, and there are only three honest responses to it.
Accept it. Publish an out-of-hours position, set expectations at the point of enquiry, and make the following morning genuinely reliable. This is a real option and is better than pretending.
Staff it. Rota someone onto evenings and weekends. Sustainable in a business with enough people, expensive and fragile in one without.
Cover it as a managed process. Every enquiry acknowledged and substantively answered within minutes, qualified, scored, and handed over so the team starts the next working day with prioritised leads rather than a backlog. This is what out-of-hours coverage is for, and the case for it rests on the numbers the measurement exercise produces, not on the idea in the abstract.
Frequently asked questions
Is faster always better?
Up to a point, and then it stops mattering. The difference between a two-minute and a twenty-minute acknowledgement is small. The difference between twenty minutes and the following afternoon is large. Speed matters because it catches the enquirer while they are still deciding, not because speed is impressive in itself — and a fast reply containing nothing useful is worth very little.
What counts as "out of hours" for a business with no fixed hours?
Define it deliberately rather than by default. Most small service businesses have a genuine pattern — hours where someone reliably picks things up, and hours where it depends who is around. Write down the first as your covered hours and treat everything else as out of hours, then measure the two separately.
Should the response time target be published to customers?
Generally yes for acknowledgement, more cautiously for substantive reply. A published acknowledgement standard sets expectations and builds confidence. A published resolution time creates an obligation that complex cases will sometimes break, which does more harm than the promise does good.
We are a two-person business. Is this over-engineering?
The opposite. Large businesses have enough volume that patterns are visible without measurement. A two-person business sees each enquiry once, in the middle of doing something else, and has no way of noticing a pattern except by writing it down. Four weeks and a spreadsheet is a proportionate amount of effort for a question this consequential.
Ready to implement AI-managed operations?
Start with one focused workflow.
Apply for a Cognumi pilot — one workflow, real data, and an agreed launch plan.