Every business says it. "Thanks for your message, we'll get back to you." It sounds polite and commits to nothing. From the customer's side, it is a receipt, not a response: they know the message arrived and nothing else. It could mean twenty minutes, Thursday or never, and they have no way to tell.
The trouble with vague promises is that each customer fills the gap with their own expectation, and they are rarely generous. Someone who assumed an hour starts chasing at ninety minutes. Someone who assumed the same day writes you off by evening. You did nothing wrong except leave the window undefined.
Getting customer response time expectations right is less about being fast everywhere and more about being specific everywhere. Speed matters, but a clear, kept promise often matters more.
Different enquiries, different clocks
A single "we reply within 24 hours" treats a burst pipe and a brochure request the same. Customers do not. Think in categories instead.
Here is a starting framework for a small service business. These windows are suggestions based on what the enquiry needs, not industry benchmarks. Adjust them to your trade and your capacity.
| Enquiry type | Channel | Acknowledge | Useful first answer | Full reply from a person |
|---|---|---|---|---|
| Safety risk or emergency | Chat, form, email | Instantly | Emergency route, immediately | Your callout time, if you offer one |
| Simple factual question (hours, areas, prices) | Chat | Instantly | Instantly | Only if they want more |
| New job or quote request | Chat or form | Instantly | Price range and next step, instantly | Same or next working day |
| Booking or appointment request | Chat or form | Instantly | Request noted, not yet confirmed | Within a few working hours |
| Problem with a completed job | Any | Instantly | Logged, with a ticket or reference | Same working day |
| Detailed brief or tender | Instantly | Receipt and a date | A named day, possibly days away | |
| Supplier or partnership pitch | Optional | None needed | When convenient |
Two things stand out. First, the acknowledge column is "instantly" nearly everywhere, because it costs nothing when it is automated. Second, the full reply column varies a lot, and that is fine as long as the customer is told which window applies to them.
Why the acknowledgement changes everything
Waiting without information feels longer than waiting with it. Most people have experienced this: a delayed train with an announcement is irritating, one without an announcement is maddening.
The same applies to enquiries. Compare these two exchanges for a physiotherapy clinic.
Visitor: Hi, I've hurt my lower back lifting, can I get seen this week?
Assistant: Thanks for getting in touch.
Versus:
Visitor: Hi, I've hurt my lower back lifting, can I get seen this week?
Assistant: Sorry to hear that. I cannot give medical advice, and if you have numbness, loss of bladder control or severe pain, please contact your GP urgently or call 999. For a new back pain assessment, the clinic usually has appointments within a few days. I can pass a request to reception now: they confirm appointments between 8am and 10am, so you will hear from them by 10am tomorrow. What name and phone number should they use?
The second reply does not get the visitor seen any faster. It does give them the safety information, a realistic expectation of availability, a specific time and something to do now. That customer is far less likely to message three other clinics while they wait.
The words that create chasing
Some phrases practically guarantee a follow-up "just checking you got my message".
- "As soon as possible." Means different things to you and to them. Replace with a time.
- "Shortly." Readers assume minutes. You usually mean hours.
- "Within 24 to 48 hours." A range that wide suggests nobody knows.
- "Someone will be in touch." No time, no person, no channel.
- "During business hours." Tells them nothing if they do not know your hours or it is Friday evening.
The fix is always the same: a clock time, a named day or a specific window, plus how they will be contacted.
A worked example: setting windows you can actually hit
Promise what you deliver on a bad week, not a good one. Here is how to find that number, using made-up figures you can replace.
Say you look back over the last month of new job enquiries and note how long each took to get a real reply from a person. You had 40. Sorted by delay, the fastest 20 got a reply within 3 hours, 32 within 8 working hours, and 38 by the end of the next working day. Two slipped longer.
- Ignore the average. The average hides the slow ones, which are the ones customers remember.
- Pick the point that covers most of them. Here, "by the end of the next working day" covered 38 of 40. That is a promise you can keep.
- Publish that, not the best case. "We reply to every new enquiry by the end of the next working day, usually much sooner" is honest and still sounds good.
- Close the gap with the instant layer. Answer the factual part immediately so the wait is only for the parts needing you.
- Measure monthly. If you are hitting it comfortably, tighten the promise. If not, fix the capacity before changing the words.
Response time is also tracked in SpideyChat's analytics alongside conversations and leads, which makes the monthly check less of a spreadsheet job. Reducing lead response time from hours to seconds goes further on the lead side.
Keep the promise consistent across channels
The window in your chat reply, your form confirmation, your auto reply and your contact page should match. If the website says "same day" and the email says "within 2 working days", customers believe the faster one and feel let down by the slower. Your out-of-office reply is often where the mismatch hides.
What to change first
Take the table above and fill in your own version, one row per enquiry type you actually receive. Be conservative in the last column.
Then find every place a customer receives an acknowledgement: website chat, form confirmation page, email auto reply, voicemail. Replace every "we'll get back to you" with a real time from your table. If you want to see how quickly a visitor gets any answer on your site today, run the website response time checker before and after.