Live chat response time: how fast should you really reply?

What live chat response time actually measures

Live chat response time is how long a visitor waits for a person to reply after sending a message in a website chat. Most reports mean first response time: the seconds between the visitor's first message and the first human reply. It is the number visitors feel most, because it is the moment they decide whether anybody is really there.

Three different clocks all get called response time, and mixing them up is why the numbers you read online rarely agree:

• First response time. From the visitor's first message to your first reply. This is the figure in most live chat response time benchmarks.
• Average response time. The average gap between each visitor message and your reply, across the whole conversation.
• Wait or queue time. How long a visitor sits waiting to be picked up when everybody is busy. It can be long even when first response time looks fine, because some tools only start the clock once somebody accepts the chat.

If you are tracking one number on a small team, track first response time. It is the one that loses you the enquiry.

Live chat response time benchmarks: what the data says

We only used figures we could trace to the original publisher. Plenty of widely shared statistics did not make the cut, and there is more on that below.

Figures checked against each publisher's own page on 27 September 2026. LiveChat's data comes from businesses that use LiveChat, so it describes teams that have already invested in answering chat. The Comm100 figure is quoted from Help Scout because the original report was not available.

What customers expect when they open a chat

Aircall's study is the clearest picture of expectations. Of 750 online shoppers, 96% expected a live chat reply within five minutes, 80% of those wanted it within two, and 49% said they would leave the site if they did not see anyone typing within a minute. For email, 94% were happy to wait up to 24 hours. Chat is the channel where people expect to wait the least.

A smaller HubSpot survey of 100 US consumers points the same way: 66% expected a response within five minutes, and 59% only wanted to live chat with human representatives. Visitors who open a chat window usually want a person, and they want one soon.

Why the numbers you read online disagree

Three reasons. Different reports measure different clocks, so a first response time and a queue time can both be called response time. Different datasets describe different businesses: a vendor's benchmark only covers that vendor's own customers. And a surprising number of live chat statistics have no traceable source at all. While researching this post we found several figures repeated across many sites, each credited to a well known research firm, that we could not find in anything the firm had published. We left them out, and you should too.

So what is a good live chat response time?

Put the traceable data together and a simple rule falls out of it:

• Under 40 seconds: good. You are at or below the averages from the largest datasets.
• 40 seconds to 2 minutes: needs attention. Most visitors will still wait, but you are slower than typical and inside the window where people start to wonder.
• Over 2 minutes: a problem. You are past what most quick-reply expecters want, and heading towards the point where one visitor in four gives up.

Our own agent desk is built around the same line. A new chat rings, and the waiting timer turns amber at 40 seconds and red at two minutes, which is roughly where the published averages and expectations sit. You notice a slow reply while there is still time to fix it, not afterwards in a report.

Why a slow reply costs a small business more than it seems

On a small business website, the chat is often the enquiry. The person asking about delivery times or next Tuesday's availability is a customer in the middle of deciding, and a slow reply hands that decision to somebody else.

Small teams are not at a disadvantage here. In LiveChat's real estate data, businesses with 1 to 9 employees answered in 31 seconds on average, while those with 50 to 99 took 1 minute 22 seconds. Being small means fewer steps between noticing a chat and answering it.

What happens once the moment passes is well documented for web enquiries. In a 2011 Harvard Business Review study of 1.25 million web leads, firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as those that waited even an hour longer, and more than 60 times as likely as those that waited a day or more. It is about web leads rather than chat, and it is from 2011, but the lesson has not aged: interest fades fast.

That is why the details a visitor gives in a WPCentrify chat fill a lead card that saves to Lead Captures in one click, next to every contact form enquiry from the same website. A good conversation should never turn into an enquiry nobody follows up.

Fast is not the same as rushed

A fast first reply buys you time. It does not have to contain the answer. "Thanks, let me check that for you" in 20 seconds beats a perfect answer in four minutes, and it keeps the visitor on the page while you find out.

Once you have replied, slow down enough to get it right. In LiveChat's financial services data, small teams handled 37.2 chats per agent per day with 75.7% satisfaction, while mid-sized teams handled 19.9 chats per agent with 83.2%. The Comm100 benchmark reported by Help Scout found something similar from the other direction: the most highly rated teams spent longer on each chat, 11 minutes 47 seconds on average against 8 minutes 42 seconds.

How many chats can one person handle at once?

For most small teams, two or three at once is realistic. Beyond that, every conversation slows down together, and the numbers above suggest satisfaction follows. The right limit depends on your questions: order status is quick, a quote takes thought. In WPCentrify you set a limit for each person, so new chats go to somebody with room instead of piling onto whoever answered first.

How to improve live chat response time (without hiring)

These are the live chat best practices that make the biggest difference on a small team. Each one ends with how we handle it in WPCentrify, because we built our live chat around exactly these problems.

Only show "online" when somebody can answer

The quickest way to wreck your average is a chat window that says online at nine in the evening. LiveChat's data shows businesses available on chat for almost 18 hours a day; a small business is not. Set real business hours for each website, in that website's own time zone, with bank holidays included. Outside those hours, WPCentrify turns a request to talk to somebody into a message the visitor can leave, instead of a queue nobody is watching.

Make a new chat impossible to miss

Most slow replies are not slow people. They are chats nobody noticed. A new chat in our desk rings for a minute, shows how long the visitor has been waiting, and has Accept right on the card. Sound and desktop notifications cover the moments when the desk is in another tab.

Put the longest wait first

In LiveChat's data, the average queue wait was 4 minutes 18 seconds, and 27.4% of visitors left before anybody replied. When a busy person picks the easiest chat, somebody gets left at the bottom. Our queue is ordered by a weighted score in which the wait weighs most, and you can set a first-response target and a waiting target so a missed one is flagged and moved up.

Share the load instead of stacking it

If one person answers everything, their response time is your response time. Share chats round-robin, send them to whoever is least busy, or let people pick from the queue, and group people into teams for each website so the right person sees the right site.

Save quick replies for the questions you get every day

Delivery times, opening hours, how to book. If you type the same answer five times a week, save it. In our desk you type a forward slash to pick a saved reply, placeholders such as {visitor.name} fill themselves in, and a greeting can send itself the moment you accept the chat.

Let visitors see that somebody is there

Aircall found 49% of shoppers would leave if they did not see anyone typing within a minute. A typing indicator is the cheapest response time improvement there is, because it tells the visitor a reply is on its way. Both sides see typing and read receipts in WPCentrify, and messages survive a page reload, so a visitor who clicks through to another page keeps the conversation.

Answer about the page they are on

A lot of back and forth is just working out what somebody is looking at. The visitor panel shows the page they are reading right now, their local time, rough location and device, so your first reply can already be about the right product or service.

Keep the pre-chat form short, or switch it off

Every field before the chat is a delay before the first message. Ask for a name at most, or leave the pre-chat form off and ask for an email address later, when there is a reason to follow up. Our follow-up form only asks for what is still missing.

Live chat greeting and quick reply examples you can copy

Short, human and specific beats scripted every time. Here are live chat greeting examples and quick replies worth saving. Swap the placeholders for your own names.

Do canned responses make live chat sound robotic? Only when they go out unchanged. Treat each one as a starting point, and add a line about what the visitor actually asked.

What your live chat should say when you are offline

A live chat offline message has one job: tell the visitor exactly when they will hear back. "We'll be in touch soon" is not a time.

Then keep the promise. Reply to offline messages within the first hour of opening; the lead study above is the reason. WPCentrify switches each website's chat to leave-a-message outside the hours you set, so no visitor sits in a queue that nobody is watching.

The live chat metrics worth tracking on a small team

You do not need a dashboard of 20 numbers. These five live chat metrics tell you almost everything:

• First response time, for each website and each person. It is the headline number.
• Wait time: how long chats sit before somebody accepts them.
• Chats where the visitor left first. Each one is a lost enquiry. WPCentrify notices when a visitor has gone and marks the chat as Left, so it is counted rather than forgotten.
• Chats per person. If one person is always the busiest, share the load.
• Rating. Only 6.7% of chats in LiveChat's data were rated at all, so ask every time. When a chat ends, WPCentrify asks the visitor to rate it poor, okay or good, and shows the results for each person.

Response targets turn these into something you can act on. Set a first-response target and a waiting target for each website, and a missed one is flagged while the chat is still open.

Who should answer the chat on a client's website?

If you run websites for clients, the fastest responder is often not you. The receptionist at a dental practice knows whether Tuesday at three is free; your team has to ask.

That is why our live chat for WordPress lets you either answer every client site from one agency desk, or hand a website's chat to the client, so their own receptionists answer from a simpler desk at chat.wpcentrify.com. The client decides whether you can read their transcripts and see their team's ratings.

Whoever answers, the same habits apply: real hours, chats that are impossible to miss, and a first reply inside a minute.

How we built response time into WPCentrify live chat

Everything above, in one place:

• New chats ring, and the waiting timer turns amber at 40 seconds and red at two minutes.
• A queue where the longest wait weighs most, with first-response and waiting targets.
• Business hours for each website, with time zones and holidays, and leave-a-message when nobody is on shift.
• Round-robin, least-busy or manual routing, teams for each site, and a chat limit for each person.
• Quick replies with placeholders, typing indicators and read receipts.
• A visitor panel showing the page they are reading, and a lead card that saves to Lead Captures.
• End-of-chat ratings for each person, and a transcript emailed to the visitor.

It does not do file attachments or proactive messages yet. It also will not slow a site down to make up for it: only a small launcher loads with the page, and the chat itself loads when a visitor opens it. There is more on that on the live chat feature page.

If this is how you want chat to work, you can add live chat to your WordPress sites during early access.