Designs a reusable macro and canned-response library that stays human and on-brand. Use when building, auditing, or expanding a support team's template playbook.
Click to play with sound.
---
name: Support Macro Library
description: Designs a reusable macro and canned-response library that stays human and on-brand. Use when building, auditing, or expanding a support team's template playbook.
---
# Support Macro Library
A macro library fails in one of two ways: it sounds robotic and customers notice, or it is so generic that agents spend more time editing than if they had typed from scratch. Good macros are 80% done and 100% on-brand.
## Taxonomy first
Before writing a single macro, map the top 20 ticket categories from the last 90 days. Group them into five to eight parent buckets (billing, onboarding, bugs, feature requests, account management, policy questions, escalations, general how-to). Every macro belongs to exactly one bucket. Name macros with the pattern '[Bucket] - [Specific Scenario]' so agents can find them in two seconds without a search.
## Anatomy of a high-quality macro
Every macro has three zones:
- Opening (1 sentence): acknowledge the specific scenario without being sycophantic.
- Body (2-4 sentences): the actual answer, action, or next step. Use '[placeholder]' tokens for values agents must personalize - customer name, order number, date, etc.
- Close (1 sentence): a single clear next step or an open door for follow-up.
Keep every macro under 150 words. If it exceeds that, split it into two.
## Personalization tokens
Use consistent token syntax across the whole library. The recommended pattern is double brackets: [[customer_name]], [[order_id]], [[product_name]], [[resolution_date]]. Document all tokens in a shared reference sheet. Agents must fill every token before sending - build a checklist reminder into your helpdesk workflow if possible.… install to load the full skill