Canned Responses That Sound Human
The goal isn't speed. It is consistency, with the personal parts left for the agent to write.
Structure beats volume
Organise by folder and name for the situation, not the content. An agent searching for "refund" under pressure needs to find it in one guess.
Use placeholders for the name, ticket ID and order details, and leave a deliberate blank where the agent should say something specific about this customer. A response that's 80% prepared and 20% written reads as human. One that is 100% prepared reads as a form letter, and customers can tell.
Keep it alive
Review quarterly. Delete anything unused, rewrite anything that produced a complaint, and add responses for whatever your last month of tickets was really about.
A library that grows and never shrinks becomes a library nobody searches.
The duplicate trap
Sooner or later somebody writes a "you already have a ticket open for this" response. It's polite, it is efficient, and it means the duplicate got all the way to an agent who had to spend time on it.
The better outcome is that the second ticket never reaches an agent at all, because it was merged into the first on arrival.
Frequently asked questions
How many canned responses should we have?+
Enough to cover genuinely repetitive replies. Prune quarterly, because an unsearchable library gets bypassed.
Do customers notice canned responses?+
They notice replies that do not address their situation. A canned skeleton with a specific opening and closing reads as attentive.
Delete the duplicate response
When duplicates merge on arrival, nobody needs a template explaining that a ticket already exists.
Start free trial14-day free trial. No credit card required.