What is Canned Response?
Also called saved reply, macro, response template.
A canned response is a stored, reusable message that can be inserted into a conversation instead of being written from scratch. Most implementations support placeholders that fill in details such as a name, order number, or link at insertion time. They are also called saved replies or macros, and macros often bundle actions alongside the text.
The value is consistency more than speed. A stored reply carries approved wording for refund terms, security instructions, or regulated disclosures, so the same commitment is not phrased three different ways across a week of conversations. Version control on the library matters, since an outdated stored reply repeats a wrong statement reliably and at volume.
Templating features vary. Simple systems substitute a few variables, while richer ones support conditional sections, locale variants, and channel-specific formatting so the same response renders correctly as email, chat, or a message on a platform with limited markup. Macros extend this by attaching side effects such as applying a tag, changing status, or assigning the conversation.
For agent systems, a canned response library is useful as grounding rather than as the final output. Supplying approved wording as retrieval context lets a generated reply stay accurate on policy while still addressing the specific question asked. Some deployments keep a hard rule that certain sentences, such as legal or safety wording, must be emitted verbatim rather than paraphrased.
The failure mode is obvious to recipients. Inserting a template that does not address the question, leaving an unfilled placeholder visible, or stacking several templates in one reply all signal that the message was not read. Good practice treats the stored text as a starting point and requires that the specific question be answered directly.
Key points
- Stored reusable text with placeholder substitution
- Primary value is consistent, approved wording
- Macros add side effects such as tagging or assignment
- Useful as grounding context for generated replies
- Unfilled placeholders and off-topic inserts are visible failures
In practice
A support library holds an approved explanation of the refund window, with placeholders for the customer name, order reference, and expected date. When a question about a late refund arrives, the assistant retrieves that entry, uses the policy sentences verbatim because they are marked as fixed wording, fills the placeholders from the order record, and adds two sentences addressing the specific delay the customer described.