Canned responses are the highest-return tool in a support team's kit and the easiest to misuse. The difference is whether they are used as a starting point or as the entire reply.
What to save
Anything typed more than a few times a week, and specifically:
- Policy explanations — returns, warranty, delivery timelines.
- Step-by-step instructions, where getting a step wrong causes a second contact.
- Links to forms, guides, tracking pages.
- Holding messages for when something needs checking.
- Difficult messages — apologies, refusals — where wording matters and improvisation under pressure goes badly.
Leave a gap for the human
The best canned responses are deliberately incomplete. They carry the factual core and leave the first line for the agent to write. That one sentence — acknowledging this customer's specific situation — is what makes the rest read as an answer rather than a leaflet.
A practical convention is to start every saved reply with a placeholder the agent must replace, so sending it untouched is impossible by accident.
The tell customers notice
A reply that answers the general question but not the one they asked. "What is your return window?" answered with the full returns policy including sections about damaged goods and international orders reads as a document, not a response. Send the relevant part.
Write them properly
- Answer first, detail second.
- Short paragraphs — this is being read on a phone.
- Specific numbers and dates, never "our standard period".
- One clear next step.
- No corporate throat-clearing. "We appreciate you reaching out and value your business" wastes the first line customers read.
Organise so they are findable
A library nobody can search is a library nobody uses, and agents revert to typing from memory — which is where inconsistency creeps back in. Group by topic, give each a short memorable shortcut, and keep the total small enough to browse. Twenty well-chosen responses beat eighty that nobody can locate.
Keep them true
Canned responses rot. A policy changes, a link moves, a timeline shifts, and the saved reply keeps confidently stating the old thing — at scale, to many customers, with your team's full authority behind it.
Review the library quarterly: click every link, check every stated number against current policy, and delete anything unused. Assign an owner, because a library owned by everyone is reviewed by no one.
A reasonable rule of thumb
If a customer could tell the reply was pre-written and would mind, edit it further. If they could tell and would not mind — a tracking link, a form, an address — send it as it is. Speed is a courtesy too, and over-personalising a factual answer wastes everybody's time.