You want faster replies without customers feeling brushed off. Used well, canned responses for customer support do both: each saved reply answers one question, carries a personal detail and gets reviewed on a schedule. Treat it as a draft, not a finished message.
Saved replies are one piece of customer service messaging, alongside the other tools a support team uses to answer customers.
| Item | Value |
|---|---|
| Consumers who find scripted, impersonal responses frustrating | 38% |
| Businesses saying their users find scripted responses most frustrating | 43% |
| Starter library size suggested by one help desk vendor | 15-20 responses |
| Setup time suggested for that starter library | 30-60 minutes |
| Vendor-estimated cut in time spent on repetitive replies | 30-40% |
The first two figures come from a Kayako live chat survey, and the last three are estimates from Mojo Helpdesk’s guide. Figures can change, so check the source before you rely on them.
What canned responses are and where they help
A canned response is a prewritten reply that an agent saves and reuses for common questions. Fin’s glossary notes that helpdesks call them macros, saved replies, snippets or templates, but the idea is the same: write the best answer once and reuse it.
The labels overlap, but a macro often does more than insert text. On Fin’s account, it can also tag a ticket, move its status along or hand the conversation to another team.
Fin lists four reasons teams keep them:
- Speed: agents answer common questions in seconds, which lowers average handle time.
- Consistency: every customer gets the same approved answer.
- Onboarding: new agents can give accurate answers from day one while they learn the product.
- Quality control: fixing one saved reply corrects the answer for the whole team.
Mojo Helpdesk’s own guide puts the typical impact at a 30-40% reduction in time spent on repetitive replies. That is a vendor estimate, so treat it as a rough guide rather than a promise. If speed is your main goal, the guide to average customer support response time puts the targets these replies help you hit in context.
Why do canned responses sound robotic?
The trade-off is tone. Fin warns that a reply that reads like a form letter, or that answers a slightly different question than the one asked, can frustrate customers more than a slower, human reply.
Customers notice. Kayako surveyed consumers and businesses about live chat, and found that many consumers find scripted, impersonal responses frustrating. Businesses report much the same about their own users.
A 2020 CustomerThink article by Jeremy Watkin describes the usual failures, including an agent who accidentally sent a customer a greeting with the name placeholder still in it. In other cases, a macro answers only one of the many questions the customer asked. These are the common causes:
- Placeholders that never get filled in.
- A template that covers one question when the customer asked several.
- Pressure to clear the queue. In the same article, an agent told a trainer that management wanted emails sent as quickly as possible.
- Stiff wording. Kayako says overly polite or stuffy macros come across as pre-fabricated and insincere.
How to personalize a saved reply without losing the time savings
Personalizing does not mean rewriting. It means adding a few specific details to a solid base, and these steps keep it quick:
- Lead with the answer. Fin advises answering the question in the first sentence and putting the solution before any explanation or sign-off.
- Use placeholders. Names, order numbers and dates make a template feel specific, according to Fin.
- Mention the customer’s actual issue. Kayako’s example turns a generic greeting into “I’d be happy to help you with your reporting questions today, [Michael].”
- Check the context first. Freshworks says agents should make sure they have the context needed to move forward before responding with a solution.
- Sound like a person. Fin suggests a conversational tone and avoiding stiff, formal phrasing.
- Offer a human way out. Forethought’s sample automated reply ends with “If this is not helpful, please respond, and one of my human colleagues will get back to you shortly!”
Kayako’s rewrites show the difference. “Please kindly allow me a moment while I pull up your account” becomes “I’m going to take a minute and pull up your account in our back end.” If you want wording to start from, the customer service message templates guide is a good place to look.
The sources for these tips are Fin, Freshworks, Kayako and Forethought. All four are vendors, so read their advice as practical guidance, not independent research.
When to skip the template
Some messages should be written fresh. Kayako names three live chat situations where a canned response is the wrong choice:
- You are unclear what the customer is asking.
- You are feeling pressed for time.
- There is no relevant canned response.
Mojo Helpdesk adds that canned responses are a poor fit for complex technical issues, sensitive complaints and anything that requires investigation. Forethought says the best tickets for macros are informational ones.
Forethought also warns against two habits. An open-ended macro, one that includes a call to action or a question, forces the customer to reach out again. Sending customers to another department is, in its words, a surefire way of turning a good customer into an angry customer.
Keeping your library accurate and easy to search
Agents will keep their own copies if the shared ones are hard to use. The CustomerThink piece calls these rogue macros, because leaders cannot control the quality of the information in them. Its recommendation is to centralize your macros, whether in a ticketing system, a shared document or an internal knowledge base.
Start small. Fin suggests pulling the 20 to 30 most common question types and writing replies for those first. Mojo Helpdesk estimates 30-60 minutes to set up a starter library of 15-20 responses, though your own volume and approval process will change that.
The same CustomerThink article recommends reviewing all macros quarterly. Its checklist works well as a standing agenda:
- Check that links still work.
- Remove replies that repeat a knowledge base article word for word.
- Confirm the information is still correct.
- Fix grammar, spelling and formatting.
- Delete macros that simply do not get used, which makes the right one easier to find.
Fin adds a simple rule: assign an owner and review regularly, because outdated canned responses spread wrong information fast, especially after product or policy changes.

Frequently asked questions
What is the difference between a canned response and a macro?
Show answer
According to Fin, a canned response is the text of the reply, while a macro usually includes that text plus actions such as applying tags, changing the ticket status or reassigning the conversation. Some help desks use the terms interchangeably.
Are canned responses bad for customer experience?
Show answer
Not by themselves. Fin says customers mind generic, off-target replies, not reused ones, so a saved reply that answers the exact question in plain language is often a good reply.
How many canned responses should a team start with?
Show answer
Fin suggests starting from the 20 to 30 most common question types. Mojo Helpdesk suggests a starter library of 15-20 responses. Either way, begin with real ticket volume rather than guesses.
How often should canned responses be reviewed?
Show answer
The CustomerThink article recommends a review of all macros every quarter. Fin also advises giving each library an owner so changes to products or policies reach the saved replies quickly.



