Fast first replies are the point of live chat. How to measure response time properly, set targets from your own baseline, staff the busy hours and set honest expectations when nobody is online.
People open a chat window because they want an answer while they are still on the page. That makes response time the number that most shapes how live chat feels to your customers. A quick, helpful first reply turns a hesitant visitor into a conversation. A long silence turns live chat into a slower version of email.
This guide covers how to measure response time properly, how to set targets from your own data instead of borrowed benchmarks, and the practical changes that make a team faster without making it sloppy.
The first reply does three jobs at once. It tells the visitor that a person has seen the message. It sets the pace of the conversation. And it decides whether they wait or leave: a visitor comparing options, or stuck at checkout, rarely sits in front of a silent chat window for long. Later replies matter too, but a conversation that starts well usually survives a slower second message. One that starts with silence often never gets a second message at all.
First response time is the gap between a visitor's first message and the first reply from a person on your team. Automated greetings and bot messages should not count; they are useful, but they are not an answer.
Use the median. Averages are pulled around by outliers: one message that arrives at 2 a.m. and gets answered at 9 a.m. can make a team that replies within a couple of minutes all day look slow. The median tells you what a typical visitor experienced. Look at the outliers separately rather than letting them distort the headline number.
Resolution time measures how long it takes from the start of a conversation until it is closed. A fast first reply followed by an hour of back-and-forth is not a good experience, so track both.
The most important number may be the simplest: conversations nobody answered. Each one is a visitor who asked and heard nothing back. Keep this close to zero before you worry about shaving seconds off anything else.
TalkingDot's Reports show conversation volume, median first response time, median resolution time, CSAT and unanswered conversations, and you can export the data as CSV if you want to slice it yourself.
Published industry benchmarks rarely match your team size, hours or customers. A target you set from your own data is more honest and easier to act on.
Speed comes from coverage more than effort. Decide who watches the inbox and when, and make it one named person's job for each block of the day; "everyone keeps an eye on it" usually means nobody does. Small teams often rotate a first-responder role in shifts of a few hours, so everyone else can focus on deeper work.
Be honest about your hours. Office hours you can actually staff beat round-the-clock availability you cannot. In TalkingDot you set them in Settings → Office hours; outside those hours the messenger switches to away mode and shows when you will be back.
Waiting feels shorter when people know how long it will be. TalkingDot's messenger can show an expected reply time, so visitors see before they type whether to expect an answer in minutes or hours. Set it to what you actually achieve, not what you hope for.
Away messages apply the same idea outside office hours. A good one says when you are back, how you will reply and what the visitor can do in the meantime:
We're offline right now and back at 9:00 tomorrow. Leave your email and we'll reply there, or search our help center for a quick answer.
Pair it with email capture so after-hours questions do not vanish when the visitor closes the tab. If your workspace has an inbound email domain configured, visitors can also reply to your answers by email.
/ in the composer to insert one, with variables such as the visitor's name filled in for you.Chat volume is rarely flat. The busiest hours heatmap in TalkingDot's Reports shows which hours and days bring the most conversations. Compare it with your median first response time: if replies slow down exactly when volume peaks, move a shift or add a second person for those hours rather than asking everyone to type faster. The teammate leaderboard helps you spot who is overloaded; it is more useful for balancing work than for ranking people.
Any metric can be gamed. A reflexive "Hi, one moment!" lowers first response time without helping anyone. A quick acknowledgement is fine when you genuinely need a minute to look something up, but if it becomes a habit, watch resolution time and CSAT. They will tell you whether visitors are being helped or just greeted.
If you want these numbers without building spreadsheets, create a free TalkingDot workspace; response-time reports are part of every workspace, and setting up office hours takes a couple of minutes.
Intercom has no free plan, so many small teams look elsewhere. Here is what to check in a free live chat plan, and what TalkingDot, tawk.to, Crisp, Tidio, HubSpot and Zoho SalesIQ include at $0.
One script tag is all it takes. Where to paste the TalkingDot snippet on WordPress, Shopify, Wix, Squarespace, Webflow or Google Tag Manager, what to set up next, and how to test it before customers see it.
Bots are good at routing, collecting details and pointing to help articles; people are better at nearly everything else. How to design button-based flows, hand off cleanly, avoid dead ends and measure the result.
Create a free account, paste one line of code and start talking to your visitors.
Free foreverNo credit cardUnlimited teammates