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

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

At a glanceFive support macros for TallybookEach macro pairs numbered steps with one closing question
  1. Can't Log InNew reset link, opened in a private window
  2. Invoice Not Received by ClientCheck spam, send via Copy Link, verify email
  3. Charged TwiceBilling team replies within 2 business days
  4. How to CancelSettings > Billing > Cancel Plan, export first
  5. Client Payment Not ShowingAllow 24 hours to sync, then reconnect Stripe

Example for: Tallybook, an invoicing app for freelancers; friendly tone; signed by Maya; no refunds without manager approval, no feature dates.

1. Can't Log In

When to use: Password reset emails not arriving or login loops.

Personalize: Hi Jordan, sorry you've been locked out since this morning.

Let's get you back in:

  1. Check spam for an email from no-reply@tallybook.app.
  2. Request a new reset link; older links expire after 30 minutes.
  3. Open the link in a private browser window.

Did the new link get you into your account?

Maya, Tallybook Support

Don't use if: The customer mentions a hacked account. Escalate to security.

2. Invoice Not Received by Client

When to use: A client says they never got an invoice.

Personalize: Hi Priya, I can see invoice #1042 was sent on May 3.

  1. Ask your client to check spam and promotions folders.
  2. Open the invoice and click Copy Link to send it directly.
  3. Confirm the client's email address has no typos.

Could you share the client's email domain so I can check delivery logs?

Don't use if: Several invoices failed at once. Flag it as a possible outage.

3. Charged Twice

When to use: Duplicate charge on a card statement.

Personalize: Hi Sam, I understand a double charge is stressful.

  1. I've passed this to our billing team for review.
  2. They will reply within 2 business days with the outcome.

Could you send the last four digits of the card and both charge dates?

Don't use if: The second charge is a separate plan upgrade.

4. How to Cancel

When to use: The customer asks to cancel their subscription.

Personalize: Hi Lena, thanks for being with us since 2022.

  1. Go to Settings > Billing > Cancel Plan.
  2. Your account stays active until the end of the paid period.
  3. Export your invoices first under Reports > Export.

Is there anything that would have made Tallybook work better for you?

Don't use if: The customer asks for a refund. Route to a manager.

5. Client Payment Not Showing

When to use: Client paid, but the invoice still shows unpaid.

Personalize: Hi Marco, I see your client paid through Stripe yesterday.

  1. Payments can take up to 24 hours to sync.
  2. Go to Settings > Integrations and click Reconnect Stripe.
  3. Mark it paid manually if needed.

Has the payment appeared after reconnecting?


Before going live: Check macro 3's 2-day billing timeline and macro 5's 24-hour sync window against your real numbers. I assumed the menu paths shown.

Written by AI from this prompt. Your results will vary.

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 in Customer Support