What is a canned response?
Also known as: saved reply, quick reply, canned message, canned reply, canned answer, canned text, response template
Published September 10, 2026 · Last updated October 8, 2026 · Reviewed by the Fidiora team
A canned response is a pre-written reply that a support agent saves once and inserts whenever the same question comes up, usually with placeholders for the customer name and details. It is also called a canned message, canned answer, or saved reply. Unlike a macro, it changes only the message, not the ticket status, tags, or assignee.
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.
- Canned response versus macro: a canned response changes only the message. A macro can also set tags, status, priority, and assignee in the same click.
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.
Canned response examples
| Situation | Canned response |
|---|---|
| Password reset | Hi [first name], you can reset your password from the sign-in page using Forgot password. The link is valid for [time]. If the email does not arrive, check your spam folder and reply here so I can send it manually. |
| Order status | Hi [first name], your order [order number] shipped on [date] with [carrier]. You can track it here: [tracking link]. If it has not moved in [days], reply and we will chase the carrier for you. |
| Feature request received | Thanks, [first name]. I have logged your request for [feature] with our product team and linked it to your account, so you will hear from us if it ships. In the meantime, [workaround] may help. |
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
Fidiora resolves the questions your canned responses answer, without an agent needing to select and send anything. Because it composes from your current documentation, the answer stays right when the underlying policy changes.
See PricingQuestions
What does canned response mean?
What is a canned message?
What is a canned answer?
When should you not use a canned response?
What is the difference between a canned response and a macro?
Do canned responses hurt customer satisfaction?
How do I keep canned responses current?
Related terms
See Fidiora resolve a ticket in 60 seconds.
No credit card, no sales call required. Connect your docs and watch it work.
No credit card · Live in under an hour · Read the setup guide