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
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
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 like this
Reply to an Angry Customer Complaint Without Blame or Vague Promises
Paste an angry customer message and get a calm reply that names their exact problem first, skips blame-shifting phrases, and ends with one dated next step.
Write a Refund or Return Denial Email That Keeps the Customer
Get a clear, polite denial email that explains the policy reason in plain words, offers an approved alternative, and includes a short chat version and escalation-risk note.
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.
Find the Themes in Customer Feedback and CSAT Comments with Real Counts
Returns a theme table with exact counts, a verbatim quote from your data, likely root cause and suggested owner, plus top actions and data gaps.
Summarize a Long Support Ticket Thread into an Escalation Handoff Note
Turns a messy ticket thread into a fixed handoff note covering the issue, steps tried, customer impact, confirmed facts, open questions and the exact action requested.
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.