Response time in customer service: what customers expect, what is realistic
Published on October 11, 2026

A customer writes on Tuesday at 9:12: “Hi, I ordered yesterday and the address is wrong, number 14 instead of 41. Can you still change it?” You see the email on Wednesday evening. The parcel went out on Wednesday at noon. Now you have a return, a reshipment, two lots of shipping costs and a customer who can't blame you, because you did reply, just too late.
Response time is the one support metric the customer measures themselves. They don't see how many emails you have. They see how long theirs went unanswered. And they don't compare that with other small shops, but with the fastest company they dealt with this week.
This article shows what customers expect from email requests, what companies actually deliver, and how a shop with one or two people in support closes the gap without living in the inbox around the clock.
What customers expect
The expectation is high, and it is rising. In a survey by Toister Performance Solutions (2018) of more than 1,200 consumers, 89 percent said a reply within one hour would meet their expectations. A reply within one day satisfied only a part of the respondents. The study's recommendation: one hour as the standard, 15 minutes as world-class.
What matters about this for small shops: the expectation refers to the first reaction, not the solution. Customers know that a warehouse has to check or a carrier has to open an investigation. What they don't accept is silence.
The second insight: the expectation is not the same for every request. Someone who needs an invoice will happily wait two days. Someone who wants to change the address before dispatch has two hours. Someone unpacking a damaged gift has, from their point of view, no time at all. Defining a single response time for everything therefore misses the point.
What companies actually deliver
The gap between expectation and reality is wide. For the SuperOffice Customer Service Benchmark Report, 1,000 companies were sent a support request by email. Result: 62 percent did not reply at all. Among those that did, the average response time was 12 hours and 10 minutes. And only 20 percent answered the question completely the first time.
These figures were collected across industries, not specifically for small online shops. But they show two things. First: the bar is low. If you reliably reply on the same working day, you are already in the better half. Second: response time alone is not enough. A fast reply that doesn't answer the question produces the next email, and then the clock starts again.
What that costs is shown by the Kundenservice Barometer 2024 by Armonia for Germany: 40 percent of respondents had contacted customer service more than once about the same request. Every one of those repeat contacts is a ticket that costs twice the time and makes the customer wait twice.
Why slow replies are more expensive than they look
An email that sits for two days doesn't just cost the customer's patience. It changes the case.
- The address change becomes a return. The example from the start. Window missed, one minute of work turns into two shipments.
- The delivery question becomes a complaint. Someone who asks on Monday where their parcel is and still has no reply on Wednesday no longer writes politely on Wednesday.
- The product question becomes a lost sale. A customer who asks at 2 pm whether the jacket is warm enough for winter has ordered elsewhere by 4 pm.
- The complaint becomes a review. According to Zendesk CX Trends 2025, 63 percent of surveyed consumers are willing to switch to a competitor after a single bad experience. An unanswered complaint is exactly that experience.
Conversely, a fast reply often solves problems that haven't even arisen yet. Someone who hears after ten minutes that the parcel arrives tomorrow doesn't ask again. Someone who gets an apology and a replacement within an hour doesn't write a review, or writes a good one.
Realistic targets for a small shop
With one person, you can't reply to every email in 15 minutes. You don't have to. What you need are targets that fit the request, and a promise you keep.
A suggestion that works well for many small shops:
- Time-critical requests (change address, cancel, “gift has to be there by Friday”): within two hours on working days. These are few emails, and they are recognisable.
- Delivery questions and complaints: the same working day. What counts here is that the customer feels someone is on it.
- Returns, refunds, product questions: within 24 hours.
- Admin (invoice, account, newsletter): within 48 hours.
The outward promise is then: “We reply within 24 hours on working days.” It is honest, it is achievable, and for most customers it is perfectly fine. A broken two-hour promise is worse than a kept 24-hour promise.
What happens at the weekend is a deliberate decision. Either you reply briefly to the urgent things on Saturday, or your auto-reply says clearly that things continue on Monday. Both work. What doesn't work is ambiguity.
Order matters more than speed
The most common mistake in small shops: emails are answered in the order they arrive. Then the 9:12 address change sits behind three invoice requests and a newsletter unsubscribe.
Sort by urgency, not by arrival. You don't need software for that, just a rule you apply on the first pass: what happens if this email sits until tomorrow? If the answer is “nothing”, it sits. If the answer is “the parcel goes out to the wrong address”, it goes to the top.
In practice that means: go through the whole inbox two or three times a day, but reply immediately only to the urgent ones. The rest goes into a block in the afternoon. How to build that pass systematically is in Tidying up the support inbox: categorising, prioritising, triage.
The holding reply: the underrated tool
Not every request can be solved immediately. But every request can be acknowledged immediately, in a way that tells the customer what happens next.
This is not a holding reply: “We have received your request and will get back to you as soon as possible.” That is a receipt. Afterwards the customer knows as little as before.
This is a holding reply: “Hi Ms Berger, I've seen your email about order 4711. I'm checking with the carrier now what's happening with the shipment. You'll have an answer from me by tomorrow noon at the latest. Until then you don't need to do anything.” Three sentences, and the customer stops waiting. She has a date.
The holding reply is one of the few things that can be fully standardised without feeling impersonal. The condition is that it names the order and contains a deadline you keep.
What automation changes about response time
This is where automation is honestly strong, for a simple reason: an agent has no queue. It answers the delivery question at 9:12, the address change at 9:13 and the invoice request at 9:14, and none of them waits for the others.
This is how it works at Humane: the agent reads every incoming email, assigns it to a category and pulls order and shipment data from Shopify and the carrier. For categories the merchant has approved, the reply goes straight out, usually within a few minutes. For everything else, a finished draft sits in the dashboard, so the human reply no longer consists of looking things up and phrasing, but of reading and approving. What the agent cannot assign with confidence, such as a second, annoyed follow-up, is not answered automatically but sorted to the top.
The limit matters: automation shortens response time for the cases where the reply consists of data. It does not replace the decision on a goodwill question or the conversation with a customer writing for the third time. For those cases it wins you the time that used to go into delivery questions. The details on the most common case are in “Where is my order?” – reducing WISMO requests.
Measuring response time without a tool
If your inbox offers no reporting, a month of manual work is enough: for 50 requests, note the arrival time and the time of the first reply. Calculate the median, not the average, otherwise one weekend distorts the number. Also note in how many of the 50 cases a second email on the same topic arrived. That is your repeat-contact rate, and it says more about the quality of your replies than the response time itself.
Benchmarks by channel, meaning what is common for email, chat and social media, are collected in Response time benchmarks 2026: email, chat, social, WhatsApp. For an overview of all support metrics, see the guide Customer service for online shops.
In short
Customers expect a first reaction to emails within hours, not days, and most companies don't deliver that. That is your opportunity, not your problem. Define response times per request type instead of one for everything, sort by urgency instead of arrival, and send a real holding reply with a deadline when you can't solve it immediately. Promise outwardly only what you can keep for sure. And have the requests whose answer consists of order data answered so fast that you have time for the ones where a person makes the difference.
If you want to know how fast your delivery questions would be answered if nobody had to look anything up anymore: try 100 customer requests for free, no credit card, cancel monthly.