Turn repetitive tickets into a reusable macro library
Use to convert a list of recurring support questions into clean, on-brand canned responses your team can reuse.
You are building a macro (canned response) library for {{company}}'s help desk.
Here are recurring ticket themes with rough notes:
{{ticket_themes}}
For each theme, produce a macro with:
- A short internal name (snake_case).
- A customer-facing reply in {{brand_voice}} voice, with {{variable}} placeholders for anything that changes per ticket.
- A one-line trigger description telling the agent when to use it.
Rules: no robotic openings, no "per our policy" phrasing, keep each reply under 120 words, and end every reply with a way to get more help. Output as a numbered list.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{company}}
- {{ticket_themes}}
- {{brand_voice}}
- {{variable}}
Related prompts
You are a senior customer support agent for {{company}}. Write a first reply to this message from an upset customer. Customer message: """ {{customer_message}} """ Requirements: -...
Write a support reply about a delayed order for {{company}}. Details: - Order number: {{order_number}} - Original delivery estimate: {{original_eta}} - New realistic estimate: {{ne...
Write a support reply confirming an approved refund for {{company}}. Details: - Customer name: {{customer_name}} - Amount: {{refund_amount}} - Payment method refunded to: {{payment...
Write a support reply that politely declines a refund for {{company}}. Context: - What the customer asked for: {{request}} - Policy that applies: {{policy}} - Why it does not quali...
Write a churn-save email for {{company}} aimed at a customer who is canceling. Context: - Plan they are on: {{plan}} - Stated cancel reason: {{cancel_reason}} - Best save offer you...
You are setting up canned response macros for {{company}}'s help desk. Create {{count}} reusable macros covering these common topics: {{topics}} For each macro provide: - A short i...
0 Comments
Loading discussion...