Customer service response time
Promise a time.Then keep it.
A good customer service response time is one you promise per channel, publish, and meet. The common pattern is a reply within minutes on live chat while you show as online, within one working day on email and tickets, and a callback in the window you named. The benchmarks are uneven: one study of 1,000 companies found an average email reply of 12 hours, and 62% never replied at all. Beating that is easy if you promise only what your hours and team allow. This page gives the sourced numbers, how to measure first response time, and a planner that writes your promise.
By the Builderify team
What is a good customer service response time?
The one you said.
There is no official customer service response time standard. What exists are vendor benchmarks, each measured on its own customers, and the expectations a channel sets by itself: a chat window says “now”, an email says “soon”. A customer who was told “within one working day” and hears back in five hours is pleased. One who was told nothing and waits five hours is not.
So set a promise per channel, publish it, and meet it. The ranges most small businesses use, which is common practice rather than measured data: a couple of minutes on live chat while it shows as online, one working day on email, tickets and social messages, and a callback in the window you named. The planner below adjusts those to your hours, team and volume.
Average reply 12 h 10 min. 62% of companies never replied, and 90% didn’t acknowledge the email had arrived.
One request with two questions emailed to 1,000 companies; third annual report, 2018 (page updated March 2023).Source
Live chat
LiveChatAverage first response 35 seconds. Where chats queued, the wait was 4 min 18 s, and 27.4% left before anyone answered.
About 1.67 billion chats on LiveChat’s own platform; data last updated 2024, collection period not stated.Source
Ecommerce help desks
GorgiasFirst response at brands of similar size ran from 1.6 hours (hardware) to 8.8 hours (apparel). After an AI handed a conversation over, the median wait for a human was 10 hours.
Its Ecom Lab data from 1,000+ ecommerce brands; period not stated. Updated 5 October 2026.Source
Social media
Sprout SocialMost consumers want brands to respond within 24 hours or sooner.
Citing the Sprout Social Index, in a June 2024 article; no percentage or sample on that page.Source
Read them as a sense of scale, not a target. Each comes from a different method: a mystery-shopper test, a chat platform’s own traffic, a help desk’s customers, a consumer survey. Gorgias also publishes the targets it suggests, under 24 hours for email (under 12 is excellent), under a minute for live chat and under two hours for social,Gorgias which are a vendor’s goals for ecommerce teams with staff on shift. No source we could verify gives phone or callback figures, so this page doesn’t either.
Customer service response time standards
for your team, not someone else’s.
Tick your channels, then enter your hours, your people and a typical day’s messages. The planner suggests a promise for each channel, the after-hours line, a sentence for your contact page and an automatic reply. It starts with a made-up two-person pottery shop. The rules are our guidance, printed below the tool, not data. Nothing you type leaves your browser.
Every day, 00:00 to 24:00 means around the clock.
All channels together, on a typical day. Minutes each includes reading, looking things up and writing.
6 h of replies a day across 2 people: 38% of 16 h open
Promise per channel
- Live chatWithin 15 minutes while we’re online
- An alert on a phone gets seen between other jobs, not in seconds. Fifteen minutes is a promise you can keep from a van or a counter.
- EmailWithin 1 working day
- Replies take a good share of your open hours. Promise a working day and beat it when you can; beating a promise feels better than a near miss.
- Social messagesWithin 1 working day
- Replies take a good share of your open hours. Promise a working day and beat it when you can; beating a promise feels better than a near miss. Treat it like email. Answer briefly in public, and move order numbers and personal details to email or a ticket.
After-hours line
For the chat’s offline message, your voicemail and the footer.
We’re here Monday to Friday, 9am–5pm UK time. Outside those hours, leave a message and we’ll reply from 9am on the next working day.
For your contact page
Next to the form, the chat and the phone number.
How fast we reply: live chat within 15 minutes while we’re online; email within 1 working day; social messages within 1 working day. We’re here Monday to Friday, 9am–5pm UK time.
Automatic reply
Set it in your email provider or help desk, for every new message.
Thanks for getting in touch with Hollow Oak Ceramics. This is an automatic reply to say your message has reached us. We reply to every message within 1 working day. We’re here Monday to Friday, 9am–5pm UK time. If you wrote outside those hours, we’ll be back in touch from 9am on the next working day. If it’s urgent, use the live chat on our website while we’re online. Thanks, Hollow Oak Ceramics
How the planner decides
It works out the share of your team’s open hours that replies take: messages × minutes each ÷ (people × open hours). Email, tickets and social get “within 4 working hours” when that share is 30% or less with two or more people, “within 1 working day” up to 60%, and two working days above that. Callbacks use 40% and 70%.
Chat depends on who watches
Two minutes while you’re online if someone sits with it (five once replies take over 60% of the day), fifteen minutes if you rely on phone alerts, and no live promise at all if nobody watches: the chat takes a message and gets the email time.
Our judgement, not a study
The thresholds are rules of thumb we chose to leave slack for calls, orders and sick days; no benchmark sets them. A single person never gets the four-hour tier. If your real numbers beat the promise for a month, tighten it.
First response time vs resolution time.
Two clocks.
First response time runs from the customer’s message to the first reply a person writes; resolution time runs until the problem is solved. An automatic “we’ve got your message” doesn’t stop the first clock, though it does stop the customer wondering. You promise the first one publicly. The second depends on the problem, so promise it per case (“the replacement ships Thursday”) rather than on your contact page.
-
01
Take a fortnight of conversations
From each channel, note when the message arrived and when a person first replied. Twenty or thirty is enough to see the pattern.
-
02
Count your open hours only
A Friday-evening email answered at 10:00 on Monday took an hour of working time, not two and a half days. Promise and measure in the same hours.
-
03
Use the median, and look at the slowest
One awkward case drags an average a long way. The median is the typical customer; the slowest few tell you where the promise breaks.
-
04
Check against the promise
What share was answered within the time you published? Below about nine in ten, loosen the promise or change who covers what.
| Arrived | First reply | Clock time | Business hours | |
|---|---|---|---|---|
| Where is my order? | Mon 10:15 | Mon 11:05 | 50 min | 50 min |
| Can I change the colour? | Mon 16:40 | Tue 09:30 | 16 h 50 min | 50 min |
| Do you ship to Ireland? | Tue 14:00 | Tue 15:20 | 1 h 20 min | 1 h 20 min |
| The handle arrived chipped | Fri 18:30 | next Mon 10:00 | 63 h 30 min | 1 h |
| Wholesale prices? | Wed 09:10 | Thu 13:10 | 28 h | 12 h |
| Average | 22 h 6 min | 3 h 12 min | ||
| Median | 16 h 50 min | 1 h | ||
Five made-up emails. In clock time the weekend makes the shop look slow; in business hours the typical reply took 1 h, and the average is pulled up by the wholesale question that waited a day.
The formula: first response time = time of the first human reply − time the message arrived, counted in your open hours. Average response time is the total of those divided by the number of conversations; the median is the middle one when you sort them. A spreadsheet with two time columns does it, and an inbox with statuses makes the second column easy to find.
Customer support response time
by channel.
Each one sets its own clock.
The channel tells the customer how long to expect before you say anything. A chat window with a green dot promises a person now; an email address promises somebody, sometime. Offer only the channels you can staff, and give each its own promise.
| Channel | What the customer assumes | A promise small teams use | What it needs from you |
|---|---|---|---|
| Live chat | Someone is there right now, because the window says so. | Within 2 minutes while shown online; a message, answered by email, while not. | A person watching it, or a chat that honestly shows as offline. |
| A person will read it, today or tomorrow. | Within 1 working day, with an automatic reply that says so. | Someone clearing the inbox at set times, at least twice a day. | |
| Support tickets | It is logged and will be worked through in order. | Within 1 working day, with the reference number in the receipt. | A queue sorted by oldest first, with priorities for the urgent ones. |
| Phone and callbacks | Ringing gets a person; a callback form gets a call in the window they picked. | A callback within 2 working hours, or the same day. | Someone free to ring, and the caller’s timezone in front of them. |
| Social messages | Public and fast, because the platform feels live. | Within 1 working day, or a few hours if social is where your customers are. | Someone checking the inbox on each platform, and a way to move private details to email. |
Common practice for small teams, not measured data; the sourced figures are in chapter 01.
How quickly should you respond to customer emails? Within one working day is the promise most small businesses can keep every day, and anything faster is a bonus you can advertise once you’ve measured it for a month. An automatic acknowledgement that names the time costs nothing: in SuperOffice’s test, 90% of companies didn’t send one.SuperOffice The wording of the replies themselves is in the guide to customer service email templates.
Phone and callbacks follow the window you offered. If the form lets someone choose “afternoon”, the promise is that afternoon, in their timezone. The guide to adding a call me back button has a desk planner that tests a callback promise hour by hour against your queue. Sales enquiries are a separate race: how fast you answer a new lead is covered in why a website isn’t generating leads.
Do you need 24/7 support?
An honest “back at 9” beats a slow “24/7”.
Most small businesses don’t need 24/7 support; they need their hours stated where the customer is waiting. A week has 168 hours. At 40 hours a person, one seat filled around the clock takes more than four people before anyone takes a holiday. A “24/7” badge that really means “someone looks at it in the morning” is a broken promise every night.
Promise in working hours, and say which ones. “Within one working day, Monday to Friday, 9am–5pm UK time” makes a Friday-night message on time when you answer it on Monday morning. Then make every channel say the same thing after hours: the chat shows as offline and takes a message, the auto-reply names the time you’re back, and the voicemail matches. For closures longer than a weekend, the holiday closure message generator writes the banner, the email reply and the voicemail from one set of dates.
Monday to Friday, 9 to 5
00 – 2440 hours a week. One person, with a promise in working hours.
Every day, 8am to 8pm
00 – 2484 hours a week: at least two people on a rota, or a promise that skips the weekend.
Around the clock
00 – 24168 hours a week: four or five people for one seat, or answers that come from somewhere other than a person.
The repeated questions can be answered at any hour by an AI chatbot that works only from your own content, as long as it says what it is and hands anything else to a person. Whether that suits your business is the subject of the guide to AI customer service for a small business.
How to improve response time
without hiring.
Small teams get faster by deciding what to answer first and by not writing the same answer twice. Typing speed has little to do with it. Six habits, in the order they pay off.
-
01
Set inbox times, and keep them
Clear email and tickets at fixed points, say 9:00, 12:00 and 16:00, instead of whenever a notification lands. A promise of one working day only needs two of those to hold, and the work in between gets done.
-
02
Triage before you answer
Read the queue top to bottom first. Orders that can’t ship, payments and anything angry go first; “do you ship to Ireland?” can wait an hour or go to the FAQ. Oldest first after that, not newest.
-
03
Use statuses so nothing waits twice
Open means you owe a reply, waiting means they do, closed means done; Builderify’s Inbox moves a conversation between the first two when either side replies. A shared inbox with those three keeps two people from answering the same email, and keeps a forgotten one visible.
-
04
Keep templates for the top ten questions
Most of a week’s messages are the same few questions. Write each answer once, keep it where you reply (in Builderify, as saved replies in Support Tickets and Inbox), and edit it per customer before sending.
-
05
Send an auto-acknowledgement with the real time
One automatic reply that says the message arrived, when you’ll answer and what to do if it’s urgent. It doesn’t count as a response, but it ends the “did they get it?” follow-up emails. The planner above writes it.
-
06
Let AI answer the repeated questions
An AI chatbot that answers only from your own pages takes the questions you’ve answered a hundred times, at any hour, and passes the rest to a person. Set its fallback line so it never guesses.
Where to publish your response time.
Wherever someone is about to wait.
Put the promise next to each way of reaching you, in the same words everywhere. Customers don’t read a policy page before they write; they read what is beside the box they’re typing into.
Contact page
One line per channel with the hours and timezone, right above the form. The contact us page guide covers the rest of that page.
Chat and form text
The welcome text in the chat window and above the ticket or callback form. Replace “as soon as possible” with the actual time.
Automatic replies
The email auto-reply, the ticket receipt and the confirmation after a form: the same promise, plus what to do if it’s urgent.
Footer and voicemail
Your hours and timezone in the site footer, and a voicemail greeting that says when you call back.
Every channel in one widget.
And what each one records.
Builderify puts chat, tickets, callbacks and an AI chatbot in one bubble on your site, with one script tag. Support Tickets records how long each first reply took; Inbox and Live Chat don’t, and there is no average-response report, so for a monthly figure use the by-hand method in chapter 03.
Live Chat
You answer from the dashboard in a browser; there is no mobile app. New chats can alert you on Telegram, and owners are emailed about a new chat when nobody has Live Chat open. When nobody can take it, the chat asks for the visitor’s email, says you’ll reply by email, and the conversation becomes a ticket. Each new chat is 1 credit.
Support Tickets
Four statuses (open, in progress, resolved, closed), low, medium or high priority, and a reference number customers use to look a ticket up themselves. Set business hours and a first-reply target in hours; each ticket shows the time left and turns red when it passes, the queue counts the overdue ones, and an answered ticket shows how long its first reply took. Saved replies, written once in the desk settings, drop into a ticket or an Inbox reply. Each new ticket is 1 credit.
Inbox
Replies to your domain’s mailboxes land in the dashboard, threaded. Each conversation is Open, Waiting on them or Closed, and it moves by itself: your reply sets it to Waiting on them, theirs sets it back to Open. Suggest reply drafts an answer from the last few emails and your chatbot’s knowledge without sending it. It doesn’t send automatic replies, so set the acknowledgement with your email provider.
Callbacks
Requests queue first asked, first called, with the caller’s timezone and preferred time of day next to each, and a status of Waiting, Called, No answer or Closed.
AI Chatbot
Answers from the pages, text and Q&As you give it, at any hour. When your knowledge doesn’t cover a question it sends the fallback line you wrote and offers to pass the question to you, instead of guessing.
Your own words
The chat, ticket and callback blocks each have welcome text you write. Their defaults say “as soon as possible”; replace it with the promise from the planner.
A new live chat or ticket is 1 credit, and the widget counts 10 credits per 1,000 page loads. Every account gets 250 free credits a month, and one-time packs start at $9 with no monthly fee; purchased credits never expire. See pricing.
Start freeResponse times, before you ask.
One you promise per channel, publish and meet. Common practice for small teams is a reply within a couple of minutes on live chat while it shows as online, within one working day on email, tickets and social messages, and a callback in the window you offered. For scale, SuperOffice's test of 1,000 companies found an average email reply of 12 hours 10 minutes, and 62% never replied.
Within one working day is a promise most small businesses can keep every day; reply faster when you can. Send an automatic acknowledgement that says when you will answer and what to do if it is urgent, and state your hours and timezone so a Friday-evening email answered on Monday morning is on time.
First response time runs from the customer's message to the first reply a person writes. Resolution time runs until the problem is solved. An automatic acknowledgement does not count as a first response. Publish a first-response promise; give resolution times case by case.
For each conversation, subtract the time the message arrived from the time of the first human reply, counting only your open hours. Take the median across a week or two rather than the average, since one slow case drags an average up, and check what share of replies met the time you published.
Support Tickets does, ticket by ticket: set business hours and a first-reply target, and each ticket shows the time left, turns red when it passes and shows how long its first reply took, with an overdue count on the queue. Inbox and Live Chat do not record it, and there is no average-response report, so work out a monthly figure by hand.
Sources
- SuperOffice Customer Service Benchmark: 1,000 companies emailed with two questions (third annual report, 2018; page updated 16 March 2023)
- LiveChat Customer Service Report: chat metrics from LiveChat’s platform (data last updated 2024)
- Gorgias Customer Service Benchmarks: Real Data from 1,000+ Ecommerce Brands (updated 5 October 2026)
- Sprout Social Social media response time article, citing the Sprout Social Index (13 June 2024)
The four benchmark pages were read on 30 October 2026. Each vendor measured its own customers or ran its own test, and none is a standard. The planner’s thresholds and the per-channel promises are our guidance, not data. Builderify details come from the module pages, the rate card on this site and Builderify’s own code.
Stop losing the visitors
you already paid for.
More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.