What is canned response?

Why it matters

Canned responses are the cheapest consistency mechanism in support, and the fastest way to make a team sound like a form letter. The difference is whether the response is used as a starting point that gets edited or as a finished answer that gets sent.

What to know

• Track edit rate. Responses that are always heavily edited are badly written, not badly used.
• Placeholders that are left unfilled are the most visible support failure a customer can receive.
• Canned responses on complaints reliably escalate the complaint rather than resolving it.
• They are best for factual, procedural, and status content where consistency genuinely matters.
• A response used constantly with almost no editing is a fully specified automation candidate.

An example

Example: a canned response explaining data export steps is sent forty times a week with no edits. That is a perfect answer being delivered by an expensive method. A canned apology for a service outage sent unedited reads as indifference.

Common mistakes

• Sending a canned response with placeholder text still in it
• Using canned text for apologies and complaints
• Never measuring how much agents edit before sending
• Confusing canned responses with macros when comparing tools

Questions