Saved replies and macros written with AI

Saved replies, also called macros, canned responses or templates, are pre-written answers you insert into a support message and then personalize. Password resets, where to find replays, how to update a card: if you answer something every week, it deserves a saved reply. They are one of the simplest ways to answer members faster and more consistently.

Yet many owners have only two or three, written in a hurry years ago and now slightly wrong. Building a proper library feels like a big writing job. With AI it becomes an afternoon: you choose the questions, supply the facts and review the results, and the assistant does the bulk of the drafting.

Choose which replies to save

Start with evidence, not memory. Look at your recent support requests and list the questions that come up again and again. If you tag your requests, the counts are already there. If you have been building an FAQ from your inbox, as described in writing FAQs from your support inbox with AI, that list is a ready-made starting point.

Fifteen to twenty saved replies cover most of a typical membership's routine requests. Good candidates are questions where the answer is the same for everyone, such as how to reset a password or download a certificate. Poor candidates are anything where the right answer depends on the member's circumstances, such as billing disputes, complaints and cancellation requests. For those, a short opening line you can build on is safer than a full template.

Draft the library in one sitting

Gather the facts for each reply first: the exact steps on your membership platform, the right menu names, links and any policy wording. Then ask an assistant such as ChatGPT, Claude or Gemini to draft the set:

I run [membership name], a membership for [who your members are]. Write saved replies for my support inbox, one for each topic below. For each: a short internal name, a one-line answer first, then numbered steps if needed, then one line inviting the member to reply if it did not help. Include placeholders in square brackets where I should personalize: [first name] at the start and [personal line] after the greeting. Use only the facts in my notes; if a note seems incomplete, flag it instead of filling the gap. Keep each under [90] words. Tone: [paste your tone guide or three tone words]. Topics and notes: [paste each topic with your notes]

Nadia, who runs an online fly fishing community, drafted eighteen replies this way. The assistant flagged two notes as incomplete: one skipped the step where members choose a device, and another did not say what happens after a pause ends. Both would have caused follow-up questions, and both were quick to fix.

Build personalization in from the start

The difference between a helpful saved reply and a cold one is the space you leave for the member. Design every template with:

• A greeting slot for their name.
• A personal line slot directly after, where you respond to something specific in their message.
• A short and a detailed version for the most common topics, so a quick question gets a quick answer.
• A fallback line telling them exactly what to do if the steps do not work.

Tone matters as much here as anywhere. If drafts come back sounding like a corporate script, getting the tone right in AI support replies shows how to fix it with examples and a list of banned phrases.

Review every saved reply before it goes live

A mistake in a one-off email affects one member. A mistake in a saved reply affects everyone who receives it, possibly for months. So test each one properly:

1. Follow the steps yourself on a real account, on a computer and a phone.
2. Check every policy detail against your published terms.
3. Click every link.
4. Read it aloud to check it sounds like you.
5. Make sure no promise has crept in that you cannot keep for every member.

Organize the library and keep it current

A library is only useful if you can find the right reply in seconds. Use a consistent naming pattern, such as Category then topic: Access, password reset; Access, cannot see course; Billing, update card. Group them by the same categories you use for tagging requests. If your help desk supports it, add keywords so typing replay brings up the right template.

Saved replies go stale quietly. Every time you change a policy, rename a section or move a page, check which templates mention it. AI can help: paste your full library and a description of the change, and ask it to list every reply that needs updating and suggest new wording for each. You still review each change before saving it.

Every few months, look at which replies you actually use. Delete the ones you never send, and add new ones for questions that have become common. When you catch yourself editing the same template in the same way before every send, rewrite the template.

Send them like a person

Never send a saved reply unread. Fill in the name, write the personal line and check that the template really answers what was asked. Members will forgive a familiar answer; they will not forgive one that ignores their question. For more on writing replies that resolve things first time, see writing support replies that solve problems the first time. And for one-off messages that do not fit a template, the approach in using AI to draft support replies faster fills the gap.

First steps

• List the fifteen to twenty questions you answer most often.
• Write accurate notes for each: steps, menu names, links and policy wording.
• Draft the set with the prompt above, including greeting and personal line slots.
• Test every reply on a real account and check every link and policy.
• Name them consistently and group them by category.
• Review the library whenever something on your site changes.