Canned responses for customer service save typing, but the best ones still answer the person who wrote in. Set them up, add specific details, and know when to edit.
Where do I set up canned responses?
Start where your team already answers messages. The same feature has different names: Gmail calls them Templates; Zendesk and Intercom call them macros; Help Scout calls them saved replies. Paths and variable behavior below are from vendor docs checked November 7, 2026.
| Tool | Feature and setup path | Variables or placeholders | Best fit |
|---|---|---|---|
| Gmail | Templates. On a computer, open Settings → See all settings → Advanced → enable Templates → Save changes. Compose the reusable text, then More options → Templates → Save draft as template → Save as new template. | Google’s setup guide describes inserting saved message text; it does not document merge fields for templates. | A solo inbox or small team that reuses email wording. Templates are available on desktop, not in Gmail mobile. (Gmail Help) |
| Zendesk | Macros. In Admin Center, go to Workspaces → Agent tools → Macros → Create macro. Add a comment or another action, then Create. Admins can make shared macros; agents can make personal ones. | Macros can use ticket placeholders such as {{ticket.requester.first_name}}. A missing field can render blank, and some placeholders are evaluated when the macro is applied. (Zendesk Help, Using placeholders) | Ticket queues where a saved reply may also set fields, tags, or assignment. |
| Help Scout | Saved replies. In a conversation, type the text, open the shortcut menu with / or Insert, then Saved Reply → Save this reply. Or use Settings → Inboxes → choose an inbox → Saved Replies → New Saved Reply. (Help Scout Support) | Variables use forms such as {%customer.firstName%}; a fallback can be written as {%customer.firstName,fallback=there%}. (Help Scout variables) | Email replies that need customer, conversation, or user details filled from Help Scout. |
| Intercom | Macros. Go to Settings → Inbox → Macros → + New macro. Add message content and any inbox actions, choose who can use it, then save. (Intercom Help) | User and company attributes fill in only in conversations with a single participant (Intercom macros). On the ticket-creation screen, select the customer first; personalization does not resolve without one (Using macros in the Inbox). | Shared inboxes where one shortcut can insert a reply and queue actions. |
Gmail is enough for canned responses if you only need reusable email text. Choose a help desk macro when the same action also needs to update the ticket or inbox. Treat platform variables as convenience, not proof that the whole reply fits: they can fill a name or ticket value, but they cannot write the case-specific sentence for you.
What should a canned response say to sound personal?
Keep the repeatable answer in the template and leave one place for the detail that proves you read this message. A reliable order is: name the specific issue, answer it with confirmed facts, then give the next step and its timing.
Use this as a starting frame:
Hi [name],
[Specific detail from their message]. [Direct answer, using confirmed account or policy facts.]
[What happens next, who owns it, and a real time or date if confirmed.]In empathy statements for customer service, refer to the burden or event they described instead of using a generic feeling claim. For example: “You cancelled on March 4 and are still waiting for the $49 refund. I’m sorry your first email went unanswered.” That line acknowledges both details without claiming to know exactly how the customer feels.
The specific detail belongs in the reply, not only in a greeting variable. “Hi Jamie” can be generated for many conversations. “Your first email reached us on March 5 and was not assigned” shows the customer which part of their case you checked. Use only details in the message or verified account records.
When should I personalize a template, and when is it fine as written?
Use the saved text as written only when the answer itself is stable and the customer’s question matches it. Personalize any detail that changes by person, ticket, or current status; write a fresh response when the issue is unclear, sensitive, or does not fit the saved answer.
| Message part | Reuse as written when… | Edit before sending when… |
|---|---|---|
| Verified instructions or policy | The steps and policy still apply to this case. | Product version, account state, or policy may differ. |
| Greeting and acknowledgment | It is brief and fits the channel. | The message includes a specific concern worth naming. |
| Customer, order, or ticket details | A verified variable resolves to the right record. | The field is blank, stale, or not visible in the composer. |
| Apology or reassurance | The wording names the actual issue. | It promises a result, cause, or timeline you have not confirmed. |
| Next step | The same action and owner apply. | This case needs a different owner, question, or deadline. |
Do not send a macro just because it shares a keyword with the ticket. If you cannot tell what the person is asking, ask a clarifying question first. That decision rule also keeps a canned response from turning into an automatic reply: a person reads, chooses, checks, and sends it.
What do canned response examples look like in a real reply?
The showcase input is fictional: a person says a $49 refund is missing and a first email went unanswered. The facts say the first refund was returned, a new one was issued March 19, and the bank estimates 3 to 5 business days.
One of three plain Claude runs included this verbatim excerpt:
Hi,
You're right to be frustrated. You cancelled on March 4, and by March 19 you still didn't have your $49 back or any reply from us. I'm sorry about both.
Each protocol engaged with the March 19 delay, the $49 charge and cancellation, and the unanswered email, then selected a different approach and form:
| Draw | Approach and form | Verbatim excerpt from Claude’s showcase output |
|---|---|---|
close_the_loop | Say what changed; detail first; up to 120 words; no sign-off. | Your $49 refund for the March 3 charge was approved on March 6. Your bank returned it to us on March 8, and nobody here noticed. |
two_remedies_choice | Offer two timed options; answer first; up to 60 words; next-message time. | Your $49 refund was re-issued March 19 and should show within 3 to 5 business days. Your bank returned the first one, approved March 6, on March 8. |
one_diagnostic_question | Ask what decides the fix; acknowledge first; up to 250 words; invite a reply. | You paid $49 on March 3, cancelled the next day, and by March 19 you still had nothing back. |
The second draw also offers a refund reference, absent from the facts; verify it before use. In these six Claude outputs, plain replies were 166, 152, and 162 words; protocol replies were 98, 57, and 203. This sample measures no quality or outcome. Review the full showcase.
We make Unsame. It returns an instruction for your model; it does not write the reply and never sees your model key, as described in the support FAQ. Read every draft and check its facts before sending. The login page starts a free account.
What should I remove from a canned response?
Delete customer service phrases that do not add a fact, decision, or next step. Replace stock empathy statements and vague promises with the detail you checked and the action you will take.
| Avoid | Replace with |
|---|---|
| “We apologize for any inconvenience.” | “Your first email reached our shared inbox on March 5 and was not assigned. I’m sorry we left you waiting.” |
| “We understand how frustrating this must be.” | “You cancelled on March 4 and are still waiting for the $49 refund.” |
| “We’ll get back to you as soon as possible.” | “I’ll update you by [confirmed date/time].” If no time is confirmed, say what you will check and do not invent a deadline. |
| A paragraph of every possible fix | The one answer that matches the case, then one question if a missing fact changes the next step. |
Before saving a new reply, scan recent conversations for a repeated answer, give the template a searchable name, mark every field an agent must verify, and assign someone to review it when the underlying policy changes. Use a plain-text document or email draft if you do not have a help desk.
A useful canned response leaves the routine part ready and the customer-specific part visible, so the agent can finish the answer instead of pasting past the question.
— Don
