How to manage saved replies and canned responses across multiple tools

Pick the reply your support team sends most, such as the one explaining a shipping delay, and count how many places it lives in. There’s probably a Zendesk macro, an Intercom macro, a Gmail template or three in individual agents’ accounts, a canned response in your chat tool, and a doc someone keeps for emergencies.

If those copies don’t all say the same thing, nobody did anything wrong. Each tool keeps its own library, and nothing connects them. Managing saved replies and canned responses across tools starts with deciding where the wording lives, then making it available everywhere agents type.

Why saved replies drift when every tool has its own library

Take the shipping-delay reply. It starts as one approved paragraph. An agent saves it as a Zendesk macro, someone on the chat team adds it to Intercom, two agents keep their own versions as Gmail templates, and the support lead pastes it into a shared doc. Each copy is reasonable on the day it’s made.

Then the carrier changes its delivery window from three to five business days to five to seven. The support lead updates the Zendesk macro and the shared doc and posts the news in Slack. The Intercom macro and both Gmail templates still promise three to five days, so customers who write in by chat or email get a different answer from customers who open a ticket.

That’s drift, and it comes from how saved replies are built. Every help desk, inbox, and chat tool stores replies inside its own product, so an update in one place doesn’t reach the others. A reminder in Slack helps for a day, but the old copies stay where they are.

You can run the same copy count on your own top five replies. List every place each one is saved, including personal templates and docs, then compare the wording. Any reply with more than one copy will drift the next time the policy behind it changes.

The more tools a team uses, the more places a reply can hide. In a 2023 Gartner survey of 4,861 digital workers in the U.S., U.K., India, and China, 47% said they struggle to find the information they need to do their jobs well, and desk workers used an average of 11 applications, up from six in 2019.

Switching help desks makes it harder still. When Jane’s support team moved off Help Scout, its saved replies didn’t move with them. Amy-Lynn Taylor, who leads customer insights and enablement at Jane, described what happened to the copies agents kept on their own:

Replies so quickly got out of date, and sometimes even had misinformation in them.

Amy-Lynn Taylor, Customer Insights and Enablement Expert, Jane

How saved replies work in each tool

Each tool handles saved replies well inside its own product. Here’s what each one offers, based on the vendors’ recent help documentation.

Zendesk macros

Zendesk calls saved replies macros, and a macro can do more than insert text. It can also apply actions to a ticket, such as adding tags or changing its status. Agents manually apply macros when creating or updating a ticket.

There are two types. Personal macros are for the person who created them, and shared macros are available to a wider group. As Zendesk says, “Admins, and agents in custom roles with permission, can create shared macros.” 

An account can have up to 5,000 shared macros. Macros are available on Suite Team and above, or on Support Team and above; limiting a macro to specific groups requires Suite Growth or Support Professional and above.

In channels that don’t support rich text, such as messaging, Zendesk applies a plain text version of the macro. For speed within the agent workspace, see these Zendesk keyboard shortcuts.

Intercom macros

Intercom also uses the term “macros,” and its current help articles don’t refer to them as “saved replies.” A macro can be available to everyone in the workspace, to certain teams, or to the person who made it (“Myself only”). Team-specific sharing depends on your Intercom plan.

Agents can insert a macro from the macros icon in the reply composer, by typing a backslash (\), or by typing # followed by any word from the macro’s name. In Intercom’s mobile apps, a macro inserts its content but not its actions. On Facebook, WhatsApp, and Instagram, images and GIFs are removed, and formatting is simplified.

Gmail templates

Gmail calls them templates. You turn them on under Settings, See all settings, Advanced, then save a draft as a template from the More options menu in the compose window. To use one, open More options, select Templates, and choose it under Insert template. According to Google’s help article, templates can only be turned on and used from Gmail on a computer, not in the mobile app.

The same article doesn’t describe sharing templates with a team, so teams usually rely on an add-on or a shared library. Our guide shows how to share email templates with your team, and our Gmail snippets guide covers faster ways to insert them.

Live chat canned responses

Chat tools vary, so here are two common examples. In LiveChat, a canned response can be Shared, for the whole team, or Private, for the person who created it, and it can be limited to one group of agents. Agents insert one by typing # followed by its shortcut.

Help Scout calls them saved replies and manages them per inbox, with a Copy button that copies a reply into another inbox. Agents open them by typing a slash (/) or clicking the plus (+) icon in the editor. If you need wording to start from, see our live chat scripts.

Tool	What it’s called	Personal and shared options	How agents insert	Where the library works
Zendesk	Macros	Personal; shared by admins and permitted agents, optionally limited to groups	Apply from the ticket	Zendesk tickets
Intercom	Macros	Everyone, specific teams, or Myself only	Macros icon, a backslash (\), or # plus a word from the name	Intercom Inbox
Gmail	Templates	Saved in each person’s account; team sharing isn’t described	More options, Templates, Insert template	Gmail on a computer
LiveChat	Canned responses	Shared, private, or limited to a group	# plus the shortcut	LiveChat
Help Scout	Saved replies	Managed per inbox, with a copy-to-inbox option	/ or the + icon	The Help Scout inbox it belongs to

The pattern holds across all five. Each library is built for its own product, so wording saved in one doesn’t appear in the others.

AI agents add another library to keep in sync

Many support teams are adding an AI agent that answers customers directly. That can add one more place where the same answer lives.

Intercom’s help center is explicit about it: “Fin AI Agent will not use Macros for customer replies.” Fin answers from knowledge content, such as help articles and Intercom snippets, a content type for information you may not want in a public help center. Intercom adds that “Only Copilot is able to recommend Macros if enabled.”

So the same refund question can get two answers: one from a human agent using a macro, and one from Fin using a help article or an Intercom snippet. If someone updates one source but not the other, customers get different answers depending on who or what replies first.

The fix is the same one that works for human agents. Keep the approved answer in a single, owned place and deliberately update the copy when the policy changes. 

A simple rule applies: generate when creation helps, and reuse when the organization already knows what good looks like.

Keep actions in the help desk and wording in one library

Help desk macros do two jobs at once. They change the ticket, with tags, status, and assignment, and they insert wording. The first job belongs in the help desk, because only the help desk can do it. The second job is the part that has to match everywhere your team writes.

Native macros are still the right answer for some teams. If your team works entirely within a single help desk, with a couple of channels and simple replies, the built-in library may be all you need.

One shared library starts to help when:

• The same answer goes out in the help desk, email, and chat
• Your team is growing, or you’re switching help desks
• Policies, prices, or delivery windows change often
• New agents need the current answers from their first day

CloseKnit Health reached that point when its teams needed the same patient messages in more than one system:

We have all of these different systems, and we wanted to have a unified voice when we talk to patients. Athena has macros, but we can’t use those in other systems.

Jacob Moore, Product Manager, CloseKnit Health

How to run one saved-reply library across every tool

Here’s how that works with TextExpander, using the shipping-delay reply as the example.

Put shared wording in shared Snippet Groups

Save each approved reply as a TextExpander Snippet, and organize Snippets into shared Snippet Groups by topic, such as Shipping, Billing, and Account. When a reply changes, you edit the Snippet once, and everyone with access gets the new version.

Snippet Group permissions decide who can change what. Can expand lets people view and use Snippets, Can edit lets them create and edit Snippets, and Can manage adds control over access and settings. New members get “Can expand” by default, so most agents use the replies while a few people maintain them.

Use the same Snippets in your help desk, inbox, and chat

The TextExpander Chrome extension works on any website or web-based application, which covers browser-based help desks, Gmail, and web chat tools. The Mac and Windows apps cover desktop email clients and other apps, and the iPhone and iPad apps cover mobile. Agents type the same abbreviation in each place, and the same approved wording appears.

AI Recommendations in the Chrome extension also surfaces relevant Snippets based on what an agent is working on, which helps new agents find the right reply before they’ve learned the abbreviations.

Add Fill-ins for the details that change

Most saved replies have a fixed part and a part that changes, and Fill-ins handle the part that changes. In the shipping-delay Snippet, a single-line field asks for the order number, a date picker sets the new delivery date, and a pop-up menu offers the approved reasons, such as a carrier delay or weather. The approved wording stays fixed, and the agent adds only what’s specific to this customer.

Multi-line fields and optional sections cover longer details and paragraphs that only apply sometimes. The fields appear when the agent expands the Snippet, so the details are in place before the reply is added to the message.

Give the library an owner and a review routine

A shared library stays current when one person owns it. CompanyCam built a shortcut-activated knowledge base and named Alex Williams its “TextExpander librarian.” The team works in Intercom, Vitally, Slack, and Salesforce, and each tool has its own macros, so keeping all copies updated by hand wasn’t sustainable.

I can update a TextExpander Snippet, and the team has access to the most up-to-date content immediately.

Alex Williams, Customer Onboarding Manager, CompanyCam

Pair the owner with a review routine. Check your most-used replies whenever a policy, price, or process changes, and do a full pass every quarter. On Business and Enterprise plans, Snippet Requests let agents propose a new Snippet or a change to an existing one, and the request goes to an Organization admin or someone with Can edit or Can manage permission to review.

A naming scheme for support abbreviations

A clear abbreviation scheme keeps shortcuts from colliding with your tools and makes them easy to learn. Three rules cover most teams:

1. Avoid characters your tools already use. Intercom opens macros with # or a backslash, LiveChat opens canned responses with #, and Help Scout opens saved replies with a slash. An abbreviation that starts with one of those characters can open the tool’s own menu, so check your help desk’s composer before you choose.
2. Use one prefix and a topic namespace. Start every support abbreviation with the same character, such as a semicolon, then add the topic and the reply: ;ship-delay, ;bill-refund, ;acct-reset. Agents can guess an abbreviation from its topic.
3. Keep the same abbreviation everywhere. Because the Snippet works in every tool, agents learn ;ship-delay once and use it in tickets, email, and chat.

For shortcuts that work inside the help desk itself, keep a list of your team’s Zendesk keyboard shortcuts next to the abbreviations, and if you’re comparing tools, our roundup of hotkey software covers the options.

One answer, one place

Go back to the copy count. The shipping-delay reply now lives in a single Snippet, in a shared Snippet Group, with a single owner. When the delivery window changes again, the owner updates that Snippet once, and every agent has the new wording in Zendesk, Intercom, Gmail, and chat the next time they type ;ship-delay.

Valentina Alividsa, who works in customer experience at Remote, described how a shared library fits into her day:

I use TextExpander for customizing email responses and storing data that I use regularly. It really helps with time consumption, as I spend less time looking for data or coming up with a reply. … I also incorporate it with Zendesk for easy use in daily tasks at work.

Valentina Alividsa, Customer Experience, Remote