Rewrite a Support Reply to Be Clearer, Shorter and Friendlier

Returns your support draft cut by at least 30 percent, with every fact and commitment kept and a table of risky promises plus safer wording.

Prompt

Prompt
Act as a senior customer support editor who trains agents on tone and clarity.

I will paste a draft support reply right after this message, plus the customer's original message if I have it. Rewrite the draft so it is clearer, shorter and friendlier.

Rules:
1. Cut the word count by at least 30 percent. Report the original and new word counts.
2. Keep every fact, number, date, link, order or ticket reference and commitment from the original. Do not add new promises, discounts or policies.
3. Open with the answer or next step in the first sentence. Use at most one short apology, and only if something went wrong.
4. Use plain words, sentences under 20 words, and address the customer as "you". Put any steps the customer must take in a numbered list.
5. Flag every promise the agent may not be able to keep, such as exact deadlines, guaranteed outcomes or "this won't happen again", and use safer wording in the rewrite.

Output format:
**Rewritten reply** (ready to send)
**Word count:** original vs. new, percent cut
**Facts and commitments kept:** checklist
**Risky promises:** table with columns Original wording | Why it's risky | Safer wording
**Tone note:** one line, only if the customer seems upset

If anything in the draft is unclear or contradicts itself, point it out instead of guessing.

Example output

At a glanceSupport reply rewrite at a glanceDamaged, late blender reply for an online kitchenware store
Original word count
174 words
Rewritten word count
108 words
Length cut
38%
Target was at least 30%
Risky promises reworded
3
8 facts and commitments kept

Example for: an online kitchenware store agent replying to a customer whose blender arrived damaged and late.

Rewritten reply

Hi Dana,

Your replacement blender (order #48213) shipped today with tracking number TRK-55920-PL. Tracking shows expected delivery by Friday, March 14.

I've also started a refund of $18.50 for the express shipping you paid for, since the first order arrived late. It usually appears on your card within 5-10 business days.

To return the damaged blender:

  1. Print the prepaid label at returns.example-shop.com/48213.
  2. Pack the blender in any sturdy box.
  3. Drop it at any UPS location within 30 days.

Sorry for the trouble with the first delivery. I've passed your feedback to our shipping team. Just reply here if anything else comes up.

Best,
Marco

Word count: 174 original vs. 108 new, 38% cut

Facts and commitments kept:

  • [x] Order #48213
  • [x] Replacement shipped today, tracking TRK-55920-PL
  • [x] Delivery date Friday, March 14
  • [x] $18.50 express shipping refund
  • [x] Refund timing 5-10 business days
  • [x] Prepaid return label link
  • [x] 30-day return window, UPS drop-off
  • [x] Feedback sent to shipping team

Risky promises:

Original wordingWhy it's riskySafer wording
"It will definitely arrive by Friday"Carrier delays are outside your control"Tracking shows expected delivery by Friday, March 14"
"Your refund has been processed immediately"Contradicts the 5-10 day timing later in the draft"I've started a refund... it usually appears within 5-10 business days"
"I've made sure this will never happen again"No agent can guarantee future shipments"I've passed your feedback to our shipping team"

Tone note: Dana used capitals and mentioned a birthday gift, so the reply leads with the fix and keeps the apology to one sentence instead of three.

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

Tips and common edits

Why this works

  • A hard 30 percent cut with before-and-after word counts stops the model from making only light edits.
  • The facts checklist makes it easy to confirm no order number, date or commitment was dropped while shortening.
  • The risky-promises table catches guarantees like exact delivery dates that often lead to a second complaint.

Use before sending a long or messy reply. Paste the draft, and the customer's message if you have it, into ChatGPT, Claude or Gemini. Check the risky-promises table against your actual policy.

Common edits

  • Ask for a version under 60 words for live chat or SMS replies.
  • Add your brand voice rules, such as no exclamation marks or always sign off with the team name.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Customer Support