Describe the situation
Say what has happened and what you want to happen, with the real names, dates, amounts and references. A sentence or two is enough; the example below started from one paragraph.
Describe the situation and get a subject line and a complete support reply email you can edit before you send.
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.
A customer has written in with a problem, a question or a complaint and you need to answer it in a way that fixes what can be fixed and tells the truth about what cannot. The Email Writer turns a few lines about the situation into a subject line and a complete support reply email, with the Customer support reply purpose already selected on this page. A support reply acknowledges the specific problem, gives the answer or the fix in steps the customer can follow, is honest about timelines and limits, and closes the loop so they know what happens next.
Three steps, about a minute.
Say what has happened and what you want to happen, with the real names, dates, amounts and references. A sentence or two is enough; the example below started from one paragraph.
Customer support reply is already selected. Pick a tone — Empathetic when the customer is upset; Professional or Friendly otherwise; Concise for a simple how-to answer. — and a length, and add the recipient and your name in Details so the greeting and sign-off are right the first time.
Read it as the recipient would. Fix the greeting if it needs fixing, cut a line, swap in an alternative subject. Then copy it, open it in your mail app, or download it.
The shape the draft follows, and the shape to check for before you send.
A real run of the tool with the Customer support reply purpose, 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.
Say the thing, front-load the words that identify it, and keep the part that matters inside the first 35–40 characters a phone shows. The tool returns three and shows a live character count.
Five things readers notice at once, and what the draft does instead.
"We apologise for any inconvenience" is what every customer expects and nobody believes. Name their problem.
A canned answer to a nearby question makes the customer write again, angrier.
A refund date or a fix time that turns out to be wrong is worse than "I will confirm by tomorrow".
"Go to settings and then find the billing tab where you can…" is a list pretending to be a sentence. Number the steps.
"The team will look into it" leaves the customer with nobody to write to. Sign it with a name.
Yes. Write support reply emails without an account, within the per-email word allowance shown next to the composer. Signing in raises it, and Pro removes the guest limits and the ads. The pricing page lists what each plan includes.
Subject: Keep the ticket or thread subject; add a status if it helps: Re: Order 8841 — replacement on its way. Opening: Thanks for writing, and a one-line restatement of their problem so they know you read it. The answer: The fix, in numbered steps if there are steps; the explanation, in one or two plain sentences, if there is one. What happens next: Who does what, by when — a refund date, a replacement's delivery window, a callback. Close: An offer to help further, by name, and how to reach you.
Empathetic when the customer is upset; Professional or Friendly otherwise; Concise for a simple how-to answer. Never Persuasive or Confident: a support reply is not a sales email.
As long as the fix needs. Steps go in a list; everything else stays short.
No. Names, dates, amounts, references and links come from your brief and are kept exactly; the tool is built not to add a promise, a policy, a deadline or a fact you did not give it. That is why the brief should carry the real details — the example on this page shows how little is needed.
Yes. The subject line and the body are editable in the page, two alternative subject lines are one click away, and six one-tap refinements make the draft shorter, longer, friendlier, more formal, more direct or more polite without rewriting the brief. Copy it, open it in your mail app, or download it as Word, PDF or text.
Check the draft's grammar, change its tone in one pass, or paraphrase a line that sounds like a template. One plan covers every tool.
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.