Canned response: saving time without sounding like a robot

A canned response is a saved reply to a question you answer every week. Used well it buys back hours and makes the answer consistent, which matters more than the time: four people explaining a refund policy four ways produces four different understandings of it. Used badly it produces the reply everybody recognises instantly as not having been written for them.

Which questions deserve a canned response

• Anything asked more than about once a week, which is the threshold where the saving exceeds the maintenance.
• Anything where being consistent is the point: policy, pricing, eligibility, what happens next.
• Acknowledgements that buy time honestly — confirming receipt and saying when a real answer will arrive.
• The awkward ones. A refusal is the hardest thing to write well under pressure, so writing it calmly in advance is worth more than any time saved.
• Not anything requiring judgement about a specific situation, which is the category that produces complaints about feeling processed.

Keeping them from sounding automated

Three habits do most of the work. Write them in the voice of a person rather than an organisation — short sentences, no formal padding. Leave a visible slot at the top for one line addressing this specific person and their specific case. And never send one entirely unedited: the smallest personalisation changes how the whole message reads, and a reply that opens by naming what somebody actually asked does not feel canned even when nine tenths of it was.

The giveaway is usually structure rather than wording — the same opening, the same closing, the same length every time. If somebody receives two of your saved replies in a month, they will notice; varying the opening line is cheap protection against that.

Keeping the library usable

1. Keep it small. A library of eighty responses means nobody finds the right one and everybody writes fresh anyway.
2. Name them by the question they answer rather than by internal category, since that is how people search under pressure.
3. Give each one an owner and a review date, because the ones stating policy go stale silently.
4. Review what is actually being sent quarterly, and delete anything unused — unused entries are what make the library hard to search.
5. Update the response whenever the underlying policy changes, in the same change rather than afterwards.
6. Watch for the response that is sent constantly: that is usually a sign the product or the documentation should answer it instead.

The signal hidden in the top five

The five most-used responses in any support team describe the five things customers cannot work out for themselves. That list is a product and documentation backlog rather than a support achievement — a saved reply that goes out three hundred times a month is three hundred people who hit the same confusion. Fixing the cause removes the work entirely, which is better than answering it faster.

Ettex Chat keeps saved replies beside the conversation so the edit happens in context rather than in a separate window, which is what makes the personalisation actually get done. Where the same answer keeps being needed, the longer-term home for it is the knowledge base rather than the reply library.