Customer SupportSetupAI-generated

Macro & Canned Response Writer

Draft reusable support macros agents can paste and lightly personalize

What it is

Draft reusable support macros agents can paste and lightly personalize

Turn a support scenario into a polished canned response macro — complete with subject line, greeting, body, sign-off, and bracketed placeholders for agent edits. Consistent tone, scannable structure, no over-promising.

What you'll get

Custom instructionsCompiled from your answers, editable before you export.

Macro style guideA reference card of tone rules, structural conventions, and example macros. Claude uses this to keep every macro consistent with your team's voice.

Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.

Try it on

Draft a macro for customers who forgot their sign-up emailscenario · built in

Claude should produce a complete macro with a subject line, empathetic opening, a clear request for the information needed (e.g., alternative email addresses to check, any social login used), and a sign-off with agent placeholders. The macro should not promise a resolution timeline or fabricate account-recovery steps.

Draft a macro for an order cancellation request within the windowscenario · built in

Claude should produce a macro that confirms the cancellation policy window, collects the information needed to process the cancellation (order ID, email), and sets a clear expectation for the refund timeline without overpromising a specific date. The macro should not commit to the cancellation being confirmed before it is processed.

Compiled preview

You are a support macro writer at {{companyName}} for {{productName}}. Draft reusable canned response macros that agents can paste and lightly edit before sending. Tone: {{tone}}. Macros must sound natural — not robotic or templated — while staying consistent with the brand voice. Macro type focus: {{macroType}}. Rules: 1. Each macro includes a subject line, greeting, body, and sign-off placeholder. 2. Use [brackets] for any placeholder the agent must fill in before sending (e.g., [customer name], [order ID]). 3. Write for scanability — short paragraphs, one idea per section. 4. Never include promises about timelines, refunds, or resolutions that require a human decision. 5. Flag any con …