How fast should a small business answer a website chat?

Why minutes, not hours

A chat is not an e-mail. People type a question into a chat box because they want the answer while they are still deciding: is the clinic open on Saturday, does the car come with full insurance, will the order reach Sharjah by Thursday. If the reply arrives an hour later, the visitor has closed the page.

There is no single correct number for every business, and nobody can promise you a conversion rate for hitting one. What works in practice is a target your team can actually keep, written down, and checked once a week.

A target table you can adopt

The first reply should carry content. "Hello, how can I help?" after a visitor already asked a question reads as a bot and resets the clock in their mind. Answer the question, or ask the one detail you need to answer it.

How two people hit two minutes

The common failure with two people is not speed; it is that both assume the other one has it. A simple rota fixes that.

1. Split the day into two shifts, for example Sunday to Thursday 9:00 to 14:00 for one person and 14:00 to 19:00 for the other, adjusted to your working week. Friday and Saturday get their own names.
2. The person on shift owns the unassigned view. Everyone else may help, but the owner of the shift is the one who is late if a chat waits.
3. Take the chat before you answer it, so the other person sees it is handled. In the StayReplied unified inbox a conversation has one owner, and presence shows who else is looking at it.
4. Hand over at shift change in writing. Any chat waiting on the customer or on a colleague gets an internal note: what was promised and by when.
5. Keep notifications on for the person on shift only. Two phones buzzing for every chat trains both people to ignore them.

What slows teams down, and the fix

• Looking up the same facts every time. Write your prices, hours and policies once, publish them, and answer from that page (knowledge and prices are drafted, reviewed and published, with every version kept).
• Waiting for a manager on simple questions. Decide in advance what the person on shift may answer alone: hours, address, published prices, booking steps.
• Answering in the wrong place. If one person replies from a personal phone and the other from the inbox, nobody knows what was said. Keep customer messages in one shared place; a shared inbox or personal phones explains the difference.
• Two people typing to the same customer. StayReplied asks you to review before sending if the customer wrote again while you were typing, and shows who is already in the conversation (more on stopping double replies).

Does AI help you answer faster?

It can draft or send replies for routine questions, but it is optional. No plan includes AI today: AI replies need your own Anthropic key. Each channel can be set so the AI is off, writes drafts for a person to send, or answers. Without AI, nothing replies on its own, so the rota above is what keeps the two minutes. Many small teams start that way, then add drafts once their published answers are complete. Complaints and refund demands always go to a person.

A weekly check that keeps you honest

Once a week, open ten chats from the past seven days and note, for each one, how long the visitor waited for the first useful reply. If more than two of the ten waited longer than your target, look at when they arrived. Usually the gap is a shift change, lunch, or the hour before closing, and one small rota change fixes it. If the gap is a sale day, see how a small team handles a chat rush.

When this is not for you

If you receive a handful of chats a week, a two-minute target is not worth a rota: one person checking the inbox a few times a day is enough, as long as the welcome message says when you reply (out-of-hours messages has wording). And if your customers mostly write on WhatsApp: web chat is the channel you connect today, and WhatsApp is coming soon. Plans and the trial are on the pricing page.