Write Saved Replies (Macros) for Your Top Five Support Ticket Types
Get five short, ready-to-send support macros, each with an editable personalization line, clear numbered steps, and one closing question that moves the ticket toward done.
Prompt
You are a support team lead who writes saved replies (macros) that agents can send in under a minute.
Before writing anything, ask me these questions in one message and wait for my answers:
1. What is your product, and who are your customers?
2. What are your top five ticket reasons, in order of volume?
3. What tone does your team use (formal, friendly, casual), and how do you sign off?
4. What must agents never promise (refunds, timelines, features)?
Then write one macro per ticket reason. Rules:
- Each macro is 60-110 words in plain language with no internal jargon.
- Start with one line labeled "Personalize:" that shows the agent what to change per ticket, such as the customer's name or the exact error they quoted.
- Give the fix or next step as numbered steps, no more than 4.
- End with exactly one closing question that either confirms the issue is solved or asks for the single missing detail.
- Never promise anything from my answer to question 4.
Output format:
For each ticket reason: a heading with the macro name, a "When to use" line, the macro text, and a "Don't use if" line.
Finish with a short note on which macros need a policy or accuracy check before going live, and any detail you had to assume.Example output
Tips and common edits
Why this works
- Asking for the top five ticket reasons first ties every macro to real ticket volume instead of generic scenarios.
- The labeled personalization line keeps macros fast to send without reading as copy-pasted.
- One closing question per macro gets the customer to confirm or supply the missing detail, which cuts back-and-forth.
Use when setting up or cleaning up a help desk macro library. Have your top five ticket reasons and any refund or promise rules ready. Works in ChatGPT, Claude, or Gemini.
Common edits
- Ask for a second, shorter version of each macro for live chat or social replies.
- Change the word limit or add a rule to include a help-center link in every macro.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Audit a Help Center Article for Gaps, Jargon and Outdated Steps
Paste a help center article and get a pass/fail checklist scorecard plus a line-by-line fix list ranked by customer impact, without a full rewrite.
Find Help Center Gaps by Matching Support Tickets to Existing Articles
Get a ticket-to-article match table and a ranked list of new help articles to write, with ticket counts and deflection potential for each.
Turn Feature Notes into a Step-by-Step Help Center How-To Guide
Paste rough notes about a product feature and get a customer-ready how-to guide with one action per step, bold UI labels, expected results and a troubleshooting section.
Turn Support Ticket Topics into a Help Center Category Structure and Article List
Groups your pasted ticket topics into 5-8 customer-language categories, flags duplicates and orphans, and ranks proposed article titles by ticket volume.
Write Chatbot Intent Answers with Trigger Phrases and Human Handoff Rules
Get a set of chatbot intents for your top support questions, each with customer-style trigger phrases, a short bot answer, and an exact rule for handing off to a human.
Write Help Article Titles and Meta Descriptions in Your Customers' Words
Get help article titles that start with the customer's task verb and meta descriptions within search length limits, each with a character count and the customer phrase it matches.