Pasting the policy instead of answering
Quoting three paragraphs of terms before the answer reads as a brush-off. Answer first; link to the policy if they need it.
Let’s write an email!
Type a few lines about what you need to say, or paste your notes. Replying to someone? Open Details above and paste their email.
Customers who write to support have usually tried to fix the problem themselves first. What they want back is proof that someone read their message, the answer or the fix, and a clear picture of what happens next. Sympathy matters, but only after it is clear the problem is being dealt with.
Replies go wrong in two opposite ways. The canned kind opens with “we apologise for any inconvenience” and answers a slightly different question; the overpromising kind invents a refund date or a fix time that nobody has confirmed. Both produce a second, angrier email.
The Support reply purpose drafts from the facts you give it: the order or account, what went wrong, what you are doing about it and when. You get the reply body with a suggested subject and a pair of other subject options, and the purpose is designed not to add policies, dates or remedies that were not in your brief.
A one-line restatement of the customer's problem so they know it was read, then the answer or fix, in numbered steps if there are any. Next, what happens and when: the refund date, the delivery window, the callback. Finish with a named person and how to reach them. Promise only what has been confirmed, and use the order or ticket number throughout.
A real run of the Email Writer with the Customer support reply purpose, printed unedited.
Reply to a customer whose order 8841 (a blue ceramic table lamp) arrived with a cracked base. Apologise, confirm a replacement ships tomorrow by tracked courier and should arrive within three working days, tracking number to follow by email. They can keep or recycle the damaged one; no need to return it. Sign as Jonah from Customer Care.
Purpose Customer support reply, tone Empathetic, standard length. No recipient or sender name was given in Details, so the greeting and sign-off are the tool's defaults.
Hello,
I’m sorry to hear that the base of your blue ceramic table lamp (order 8841) arrived cracked. We understand how disappointing that must be.
We’ve arranged for a replacement lamp to ship tomorrow via a tracked courier, and it should reach you within three working days. I’ll email you the tracking number as soon as it’s available.
You can keep or recycle the damaged lamp; there’s no need to return it.
Thank you for your patience, and please let us know if there’s anything else we can help with.
Best regards, Jonah Customer Care
Generated by the Email Writer on 18 September 2026 and printed here unedited. Every date, name and number came from the brief; a draft is meant to be read and edited before it is sent.
The first two lines of a support reply decide how the rest is read. They should show that you understood the specific problem and set up the answer. The right balance of acknowledgement and action depends on what the customer wrote in about.
| Ticket type | Tone to choose | What the first lines should do |
|---|---|---|
| Damaged or faulty item | Empathetic | Name the item and the fault, then say what you are sending or refunding. |
| How-to question | Concise or Friendly | Answer directly; steps follow in a numbered list. |
| Billing error | Professional | Confirm the error and the amount, then the correction and its date. |
| Angry complaint | Empathetic | Acknowledge the specific failure once, without arguing, then the remedy. |
| Request you cannot meet | Professional | Say no clearly, explain why in one sentence, offer what you can do. |
A fix written as a paragraph (“go into settings and then open billing, where you'll find...”) forces the customer to hold the whole sequence in their head. Break it into numbered steps, one action each, starting with a verb, and use the exact labels they will see on screen.
For example: 1. Open Settings. 2. Choose Billing. 3. Select Update card. 4. Enter the new card and press Save. Four short lines are faster to follow than one long sentence, and if something goes wrong the customer can tell you which step failed.
Keep explanations separate from steps. If the customer needs to know why something happened, give it in one or two plain sentences before or after the list, not threaded through it.
The tool drafts from your brief and is built not to invent a policy, a timeline or a refund. That protection only works if the brief is accurate. If the warehouse has not confirmed a dispatch date, do not write one in; write when you will confirm it instead.
“I'll check with our warehouse and update you by 3 pm tomorrow” is a promise you control. “Your replacement will arrive on Thursday” depends on a courier you do not. Customers forgive a short wait far more readily than a missed date, and a reply that turns out wrong costs more than the time it saved.
Sign every reply with a name. “The team” gives the customer nobody to write back to, and one owner per ticket stops two agents giving different answers.
When the ticket is about a faulty product, your reply sits on top of legal rights. GOV.UK's guidance for UK sellers says a business must offer a full refund if an item is faulty, not as described or does not do what it is supposed to, and must repair or replace an item returned within six months unless it can prove the item was not faulty when bought. Customers have up to six years to make a claim (five in Scotland).
For online and phone sales, customers who tell you within 14 days of receiving an item that they want to cancel are entitled to a refund, and once the item comes back the refund must be paid within 14 days. A support reply should never offer less than these rules give; if your policy is more generous, say so plainly.
Some tickets need a human decision before any draft goes out: anything involving injury or product safety, a threat of legal action, a data or privacy complaint, or a customer who says they are in financial difficulty. Draft if it helps, but route those to whoever owns the decision and have them read it first.
A third reply to the same unresolved problem is also a signal to change channel. Offer a phone call or a named escalation contact rather than another email in the same pattern.
Put the facts the customer needs into the brief: the order or ticket number, the product, what went wrong, the remedy, any dates you have confirmed, and whether they need to return anything. Add the agent's name and team so the reply is signed.
Choose Empathetic when the customer is upset, Professional or Friendly for routine questions, and Concise for a quick how-to. Persuasive and Confident do not suit support work. Standard length fits most tickets; Short suits a one-step answer.
Quoting three paragraphs of terms before the answer reads as a brush-off. Answer first; link to the policy if they need it.
Requesting the order number that is in their first line tells the customer nobody read it. Check the thread before asking.
Marking it solved while the replacement is still in transit means the customer has to start again if it does not arrive.
“The courier messed up” may be true, but the customer bought from you. Own the problem and describe the remedy.
Name what went wrong in their words: “I'm sorry your lamp arrived with a cracked base” rather than “we apologise for any inconvenience”. Apologise once, near the start, then move to the fix. A concrete remedy delivered quickly reads as more sincere than a longer apology.
Yes, in most help desks and mail clients. Replying inside the ticket or thread keeps the history together for both sides. If your system allows it, add a short status after the original subject, such as “replacement sent” or “refund issued”, so the customer sees the outcome from the inbox.
Say so, say what you are doing to find out, and give a time you will update them by, then meet it. A holding reply with a real deadline is far better than a guessed answer that you have to correct later.
Yes. Put the decision and the reason in the brief, plus anything you can offer instead, and choose Professional or Empathetic. The draft states the refusal clearly rather than burying it, which avoids a follow-up asking what you meant. Read it once for tone before sending.
As long as the fix requires and no longer. A how-to answer might be a greeting, four numbered steps and a sign-off. A damaged-order reply needs the remedy, the dates and the return instructions. Anything beyond that, such as marketing or unrelated offers, belongs elsewhere.
It is designed not to. The Support reply purpose drafts from the facts in your brief and avoids inventing policies, timelines or compensation. Still check every number and date in the draft against your system before sending.
Written and checked by the AI Writing Assistant team. Last reviewed . Sources: GOV.UK: Accepting returns and giving refunds.
Each page opens the writer with that purpose already selected, shows a real draft the tool returned from a one-line brief, and explains what that kind of email has to do. The purpose menu above the brief covers all sixteen.