Canned responses

How to write canned responses that sound human

How to write canned responses that save time without making visitors feel they are talking to a script.

By DataConfluxLab · Published 2026-10-06 · 3 min read

A canned response saves time on the questions you answer every day. The risk is that a reply copied word for word can feel cold, especially when a visitor is stuck on something specific. The goal is not to avoid canned responses. It is to write them so they read like a person who has actually listened.

If you want a list of ready-made replies to start from, see the canned response examples. This guide covers how to write and maintain them so they stay useful.

Start with the questions you actually hear

Read your last fifty chats or support emails and list the questions that came up more than once. Shipping times, price questions, how to cancel and how to install the widget are common ones. Write one reply for each, and stop there. A short list that covers ninety per cent of your questions is more useful than a long list nobody can find.

Open with the visitor's words

The fastest way to make a reply feel personal is to reflect what the visitor said. If they asked about delivery to a specific city, start by naming that city. The rest of the reply can stay standard, but the first line should show you read their message.

Keep the answer direct

Visitors in a chat want an answer, not a paragraph of policy. Put the answer in the first two sentences, then add any detail they will need. If the answer depends on something you cannot know from the message, ask one clear question rather than sending a long list of options.

Leave room for the exception

Every canned response will eventually meet a visitor it does not fit. End each reply with a line that invites a follow-up, such as asking whether the answer covers their case. When a question does not fit any template, write a fresh reply rather than forcing a canned one. You can save the new reply afterwards if it turns out to be common.

Use a consistent voice

Decide how your team speaks before you write the replies. Some teams are formal, others are casual. What matters is that the whole team sounds the same, so a visitor who talks to two agents does not feel they reached two companies. Write a short style note with three or four rules, such as using first names, avoiding jargon and never blaming the customer, and check new replies against it.

• Use the visitor's name when you have it.
• Avoid jargon the visitor would need to look up.
• Never suggest the problem is the visitor's fault, even when it is.
• Finish with a clear next step.

Review them on a schedule

Products, prices and policies change, and an out-of-date reply does more damage than a slow one. Set a monthly reminder to check each reply against the current facts. When a price changes, search for every reply that mentions it. This is the step most teams skip, and it is the one that causes the most trouble.

Make them easy to find

A canned response that is hard to find is not saved time. Group replies by topic, use short titles that match what agents type, and keep the list small enough to scan in a few seconds. In LiveChatDock, canned responses are available on every plan, so the whole team works from one list.

Where to go next

Once your replies are in shape, the next question is when chat should answer a question at all. The guide on live chat and contact forms explains when each one works best. And if you are still deciding how many people you need to answer, read how many agents you need for live chat.