Live Chat Response Time: How Fast Is Fast Enough?

A good live chat response time is measured on the first reply: under 30 seconds is excellent, under a minute is fine, and past two minutes most visitors have already asked someone else. A small team can't be that fast all day, so the real job is narrower — never leave someone in silence while you're online, and never leave a chat window unattended while you're not.

"Reply faster" is useless advice for a team of one or two. The questions worth answering are: how many seconds is fast enough, what does the visitor see when you miss that window, and how would you know how fast you are today.

How long will a visitor wait in a chat window?

Less time than you think: attention is measured in seconds, abandonment in minutes. In Jakob Nielsen's three response-time limits, ten seconds is the limit for keeping someone's attention on what they're doing — past that, their mind moves on to something else.

A chat window is a conversation with a person, so visitors expect some delay. The ten seconds isn't a deadline for the answer; it's a deadline for a sign of life. "Hi — let me check that stock for you" and ten seconds of nothing are two completely different experiences.

Time waited	What the visitor is thinking	What should happen
0–10 seconds	Still waiting, still looking at the chat	Send something, even without the answer
10–30 seconds	Wondering whether anyone is actually there	At least a typing indicator or a first line
30–60 seconds	Scanning the page for another way to contact you, or opening a new tab	The floor for a first reply
1–2 minutes	Most have asked the same question on another site	Have the widget admit nobody is free and take their email
Over 2 minutes	Tab closed; they will not come back on their own	Treat it as a lead to follow up, not a live chat

Selling to other time zones adds a layer: it's 10 a.m. for them and 3 a.m. for you. In that case the target isn't seconds at all — it's how many hours until they get an email back. More on that below.

First reply vs follow-up replies

First response time is the gap between a visitor's first message and your first reply, and it decides whether the conversation happens at all. Follow-up time decides whether they stay long enough to finish explaining the problem. The two deserve different targets.

• First reply: under one minute. The visitor doesn't yet know if anyone is home, so silence hurts most here. The first line doesn't have to be the answer — "Hi, give me a moment to check" does the job.
• Follow-ups: under two minutes. Once the conversation is going, patience stretches, but not past two or three minutes of nothing.
• When you need to go look something up, say how long. "Let me check the warehouse, about three minutes" beats "one moment" by a wide margin. A number turns silence into something expected, and people will wait for it.

One trap worth naming: chasing a lower average response time. For a small team, the average hides two very different groups of chats — the ones that arrive while you're at your desk, and the ones that don't. The first group is a habit problem, the second is a settings problem. Averaged together, they read as "we're doing fine."

What response time should a small team aim for?

Pick a target that matches how you actually work, not one copied from a 50-person support team. Most small sites look like one of these four rows.

Your situation	First reply target	How you hit it
One person, chat open while doing other work	1–2 minutes	Push on your phone, wait-time reminder at 2 minutes
2–3 people with someone on duty	30–60 seconds	Round-robin assignment, 2–3 chats at a time each
Time zones apart — their daytime is your night	Live replies aren't realistic	Business hours plus a message form; promise an email within one business day
High-value orders that need a quote or stock check	First line in 30 seconds, answer later	Acknowledge, then say when the answer is coming

Then write the target down as a sentence the team can repeat — "someone says something within one minute" — instead of leaving it as a feeling. Whoever is on duty owns that minute. That does more than any setting.

What to set up for the times you can't reply fast

Five settings turn "nobody answered" into "something answered." They close different gaps, so work down the list — each one takes a few minutes in the console.

Fix	The gap it closes	Where in SealReply	Effort
Wait-time reminder	You're "online" but busy, and someone waits in silence	Sites → your site → Hours & waiting	Pick a duration
Quick replies	Typing the same answer again, slowly	Quick replies	Save your five most-used
Mobile app or browser push	The console is closed, so nobody sees the chat	Get the mobile app, or account menu → Push notifications on this device	Set up once
Assignment and chat limits	Everyone assumes a teammate will take it, or one person takes too many	Sites → Basics, Team	Two dropdowns
Business hours and the message form	Nobody is there at all, so live replies are impossible	Sites → your site → Hours & waiting	Fill in your week

The wait-time reminder is the cheapest win here. If nobody replies to a visitor's first message within the time you set, the widget tells them so and offers to email them the reply once it comes, asking for their address. The conversation is also flagged Unanswered, so you can filter for those later and clear them.

Quick replies solve the other half — you're there, but typing can't keep up. Save your most common lines under Quick replies ("Hi, checking that now", "Free shipping over $50, usually 3–5 days"), then type / in the composer to pull one in. You get a personal set and a shared team set. For ideas on wording, borrow from these live chat greeting messages and make them your own.

Assigning new chats lives in your site's Basics and offers three modes: take turns (round robin), least busy agent, and agents pick them up. For two or three people, round robin is the easiest to live with because responsibility is never ambiguous. Pair it with Chats at the same time under Team (1 to 50 per agent): set it too high and nobody appears to be queueing, while every visitor is in fact waiting.

For the hours when nobody is around at all, there's a whole article on handling live chat when you're offline.

How to set it up in SealReply

Five steps, about ten minutes, no code.

1. Turn on the wait-time reminder. Go to Sites → your site → Hours & waiting and set Remind after. Anything from 30 seconds to 30 minutes; the default is 2 minutes. Most shops should leave it there — under a minute you mostly collect email addresses from visitors you were about to answer anyway.
2. Save five quick replies. Open Quick replies and add one each for acknowledgement, shipping, returns, pricing and after-hours.
3. Choose how chats are assigned. Under Sites → Basics, set Assigning new chats, then give each person a Chats at the same time limit under Team.
4. Get alerts on your phone. Use Get the mobile app in the console sidebar, or turn on Push notifications on this device from the account menu. Lock screens show only that there's a new chat and which site it came from, not what the visitor wrote.
5. Fill in business hours. If you only reply at fixed times, turn on Only accept chats during business hours, pick your time zone and add your periods. Outside them, visitors get a message form that shows when you're next online in their own time zone, and the After-hours note under Texts is where you promise a turnaround ("Every message gets a reply within one business day").

Treat the ones who timed out and left an email, and the ones who used the after-hours form, as leads rather than chats. In Harvard Business Review's audit of 2,241 US companies, firms that tried to contact a web lead within an hour were nearly seven times as likely to qualify it as those that waited just one hour longer. Don't let the overnight messages sit until tomorrow afternoon.

How do you know whether you're fast enough?

Look at three places in the console instead of going by feel. Your feeling only remembers the chats you were present for.

• Reports → Overview. "First response" is the average time to your first reply over the period, with a faster/slower comparison against the previous one. Check the last 7 days and the last 30 days — a big gap between them is a duty-roster problem.
• Reports → Results. "Waited past the wait time" shows how many chats went past your reminder and how many of those got an answer eventually. Below it, "When visitors were missed" plots weekday against hour, so the bad slots are obvious and you can staff them.
• Conversations. Filter for Unanswered and clear the backlog one by one. Dismissing one from the filter doesn't change the count in Reports.

Every Monday (owners and admins can change the day and hour under Settings → Notifications) a short weekly summary email lands: chats this week, who left contact details, who still needs following up. It never contains what visitors wrote.

FAQ

What is a good first response time for live chat?

Under 30 seconds is excellent and under a minute is fine. Past two minutes, most visitors have closed the tab or asked a competitor. A more useful target for a small team is this: somebody says something within one minute, even if it's only "Hi, let me check."

Can one person really run live chat alone?

Yes, with a different goal: not instant replies, but never leaving silence. Push notifications on your phone, a wait-time reminder at two minutes and a handful of saved quick replies will get a first line out within a minute or two for most chats. For the hours you genuinely can't cover, use business hours so visitors leave a message instead.

What does the visitor see when nobody replies in time?

In SealReply, once the first message has gone unanswered for the time you set, the widget tells the visitor so and offers to email them the reply, asking for their address. If it already knows their email it shows a masked version such as a***@example.com and just asks them to confirm. The conversation is flagged Unanswered.

Where can I see my live chat response time?

Under Reports → Overview, where "First response" covers today, the last 7 or 30 days, or a custom range, with a comparison against the previous period. Reports → Results adds "Waited past the wait time" and a weekday-by-hour view of when visitors were missed. Per-agent and per-site breakdowns, and anything older than 30 days, need the Pro or Business plan.

Should I hide the chat widget outside business hours?

No. Hiding it means the visitor who shows up at midnight has nowhere to ask, and you lose both the question and their email. Turn on Only accept chats during business hours instead: the widget still appears, but as a message form that tells them when you're next online in their local time.

Will a chatbot fix my response time?

SealReply has no bot that answers questions, so that isn't the answer here. Two things do cut waiting: an FAQ card on the widget's home page (Starter plan and up), which lets visitors answer their own common questions, and quick replies, which make a human faster.

Next steps

Response time is one piece of running chat well. For the whole path from installing the widget to following up on a sale, read the complete guide to live chat for small business.