Support Macro Library Builder
The twenty answers you give every week, written once, written well, and governed so they don't rot into corporate sludge.
What it is
Turns the twenty questions you answer every week into a governed library of replies that sound like you and hold up under volume: harvested from real ticket flow, clustered by intent rather than wording, architected with a naming scheme agents can actually search, and fenced by the rules that keep macros honest. For founders answering their own inbox, for the first support hire, and for any team whose replies have drifted into five different voices.
What you receive
a complete, tone-consistent macro library built from the questions your business actually receives — clustered by intent, each macro with its trigger conditions, its variable slots and its escalation exit, plus the naming scheme, the never-macro list, and the maintenance rules that stop the library rotting
Delivered as a single, complete .md skill file — open it, paste it into any capable chat model, and work. No installation, no account with anyone but us.
Supported models
- Claude (Opus/Sonnet)
- ChatGPT (GPT-4o/5)
- Gemini
- any capable chat model
People reach for it when
- “customer support canned response examples”
- “how to write support macros zendesk”
- “customer service email templates for common questions”
- “standardise support replies across a team”
- “support macro library best practices”
Record
lineage: first-party house build
gates passed: demand-evidence · function-fit · beats-the-blank-page
status: IN THE COLLECTION
Sale-time bench runs and the fix-or-refund log attach to this record when the payment room opens.
In the collection. The sale room is being fitted; this work goes on sale when it opens.
Join the house — be written to when sales openBack to the collectionLicense
Free-shelf works ship under the DolceDrago House License — use the outputs freely, personal or commercial; the work file itself stays with the house.