A canned reply is a saved answer to a question that comes up again and again. An agent picks it from a list, and it drops into the reply box.
Some products call these macros. In some tools a macro may do more than insert text. Check what each maker means by the word, because the terms aren't used the same way everywhere.
Why teams use them
One maker's help page says agents "continue reinventing the wheel for the same queries"1. Wasted hours and inconsistent replies follow, it says.
Its fix is to "create pre-formatted reply templates to common questions as Canned Responses and allow agents to reuse them with a single click"1. That's the whole idea. Write a good answer once, then reuse it.
What goes into one
From that product's setup steps, a saved reply has a few parts.
- A title that staff can understand in a list.
- The message text, in a formatting editor.
- Placeholders, which are slots filled in from the ticket. The page says replies can be customized "using dynamic content placeholders"1.
- Optional attachments.
- A visibility choice: just you, certain groups, or everyone.
The page says a response can be available "only to you, to a specific set of groups, or to all agents"1.
Where they're used
In one product, the steps are to click Reply in the ticket, then "Click the Canned Response icon at the bottom left corner of the reply editor"2. Where the button sits varies by product, so look for it in any trial.
Keeping them from sounding robotic
A saved reply is a draft, not a finished letter. A few habits keep it human.
- Open with the customer's name through a placeholder, then add a line that shows you read their message.
- Write in the voice your team uses on the phone.
- Keep each reply short. Link to a help page for long steps.
- Leave a gap where the agent must add something specific.
- Don't promise more than your team can do.
Never let a placeholder go out empty. A message that says "Hi ," looks careless. Ask whether the tool warns you when a field is blank.
Care and upkeep
Replies go stale. A price, a policy or a menu path changes, and an old reply keeps repeating it. Give each reply an owner and a review date, even if it's just a note in the title.
Don't build a library on day one. Start with the questions you answer most. Add a reply only when you've written the same answer several times.
Keep your own rules about privacy and legal wording simple. If a reply touches refunds, data or contracts, have your lawyer or accountant read it first, and point customers to the official source for any rule that depends on country.
What to ask a vendor
- Can staff keep personal replies as well as shared ones?
- Can an admin control who edits shared replies?
- Do placeholders cover the fields you actually use?
- Can a reply attach a file?
- Is there a limit on how many you can save, or does the plan change it?
Get answers from the maker's documentation and record the date you checked.
Sources used
- Create common reply templates with canned responses, Freshworks (Freshservice Support)
- Using canned responses in ticket replies, Freshworks (Freshservice Support)