Customers do not judge a support reply by its vocabulary. They judge it by whether the first line helps. Generated replies almost always open by restating the question, which reads as a machine confirming receipt instead of a person solving something. The fix is ordering, not tone.
Read any generated reply and you will find the same shape: thanks for reaching out, restatement of the problem, an apology, a general statement of intent, and a closing offer of further assistance. It is polite, complete and useless, because the customer has to read four sentences to find out whether anything will happen.
People write that way to avoid committing to an answer, which is exactly what the customer is afraid of. So the first line is where trust is won or lost, and it should be the outcome.
Four lines, in this order, work for almost every support situation:
Nobody notices a well-shaped reply. That is the point.
Say so in the first line. 'I cannot restore the deleted draft' is a poor greeting but an honest one, and it lets the customer start solving the problem instead of negotiating with you. Then say what you can do, export the fragments, share the version history, credit the month, and let them choose.
Resist the urge to soften a no with a paragraph. A softened no is read as a maybe, and a maybe turns one frustrated customer into three emails and a chargeback.
| What people usually write | What it looks like after |
|---|---|
| Thank you for reaching out. I understand your frustration regarding the duplicate charge on your account. I will look into this and get back to you shortly. | I have refunded the duplicate charge, you will see it on the statement in three to five business days. It happened because the first payment timed out and both went through. |
| We appreciate your patience as we investigate the issue you have reported regarding the export function. | The export is broken for accounts with more than 2,000 rows. I have no fix today. You can export in two halves until Thursday, and I will write again when it is fixed. |
| Please let us know if you have any further questions or concerns. We are always happy to help! | If the refund does not appear by Friday, reply to this and I will chase the processor myself. |
If you want this done to your own draft: ShipCopy takes a piece of text you already wrote and rewrites it in one of three modes — rewrite it to read human, turn a product description into launch copy, or turn a plain-language request into a reusable prompt. Six output formats, 13 languages. 10 generations free, no card.
See what it does Pricing — US$15/monthYes, once, in a short sentence, and only after the action. An apology before the fix reads as a substitute for it.
Short in structure, not in content. Four lines with an outcome and a date beat three paragraphs with neither.
They are usually reading for one thing: whether the person replying has authority. Name the action you took, not the team you escalated to.
Related guides
Get the checklist as a file you can actually use. One email with the full list, plus the three tells that get caught most often. No drip, no "just checking in" follow-up.