Free email reply generator for a stronger first draft.

Marsden Joinery fits kitchens. The message to answer comes from a customer whose worktop template slipped by a week at the stone supplier, asking whether the install can move forward to the week before Christmas instead, and whether there is a discount given the delay. The inputs are: the answer is no on the date and partly yes on the money, the relationship is worth keeping, and the reply has to go out today.

The draft that comes out reads like this. Hi Jenny. The week of the fifteenth is not possible and I am sorry about that. The stone has to be templated, cut and cured before it can be fitted, so the earliest realistic install is the week of the fifth of January. I have held Monday the fifth and Tuesday the sixth for you and will keep them until Friday. Chasing the template was ours to do and I did not chase it hard enough, so I am taking one hundred and fifty pounds off the final invoice. The oven and sink go in on the fifth, so you will have a working kitchen by that evening rather than at the end of the week. If the fifth does not suit, tell me by Friday and I will offer the next pair of dates I have. Tom.

It works because the answer is in the first line and the reason follows it rather than preceding it. The apology is one clause inside that sentence, enough to be credible and short enough that it does not become the subject of the email. The concession is a number rather than a gesture towards goodwill, so there is nothing left to negotiate. The dates are specific, the hold has an expiry, and the last line says exactly what the customer does if the answer is no.

It leaves things out on purpose too. There is no paragraph about the stone supplier, because the customer bought a kitchen from the joiner and the supply chain is not her problem. There is no list of four reasons the date is impossible, since each extra reason is another thing a determined reader can argue with individually. And it does not close on let me know if you have any questions, which invites a reply that resolves nothing.

The weaker version opens with thanks so much for your email and apologies for the delay in coming back to you, explains that it has been an incredibly busy period and the stone supplier has let us down again, promises to do everything we can to get you in as soon as possible, and ends with let me know your thoughts. The actual answer is nowhere in it. As soon as possible is not a date, so the customer still cannot decide whether to book time off. The discount is absent, which means she has to ask a second time and now feels like she is extracting it. Handing the decision back with nothing to decide guarantees another email, and probably a phone call in which the whole thing is said again.

Do not reply in writing when the message needs a voice. Money in dispute, a mistake that has cost somebody something, or anything a person is plainly upset about goes better on a call, because email lets both sides re-read, rehearse and take the worst available reading of every sentence. Ring them, sort it, then send four lines confirming what was agreed. The written record still matters, it just belongs after the conversation.

Do not draft the full reply when you do not yet have the answer. Two lines saying you have seen it and will come back by Thursday costs a minute and stops the other person chasing. A long holding message that dresses up not knowing is worse than silence, because it spends the reader's attention and delivers nothing they can act on.

Be careful when the reply carries contractual or legal weight: ending an agreement, accepting fault, anything heading towards a formal complaint or a dispute. A fluent, warm draft can concede something you did not intend, and once sent it is evidence. Acknowledge receipt, say when a full response will come, and get the substance checked by whoever needs to check it before it goes.

And stop drafting individually if you are writing the same reply every week. That is a saved response, a linked page, or a change to whatever prompts the question in the first place. Three near identical replies a week means information is missing somewhere upstream, and rewriting it politely each time hides the problem rather than fixing it. One more case for waiting: if you are angry, write the reply and do not send it. Leave it an hour, read it as the recipient, and cut the two sentences you added to make a point.

Answer, reason, next step, in that order. The first line carries the decision: yes, no, the date, the number. The reason goes second and should be one sentence, because a reason offered before the answer reads as preparation for bad news, and a reason offered at length reads as a case being built. The last line names what happens next, who does it, and by when.

Everything else is optional. A greeting and a sign off, obviously. A short acknowledgement where the message deserves one. Beyond that, extra paragraphs usually exist to manage your own discomfort rather than to inform the reader. Keep quoted history below your reply rather than interleaved, unless you are answering several distinct questions, in which case take them in the order they were asked and use their words for each so the mapping is obvious. If the thread has changed subject twice, start a new email with an accurate subject line instead of replying into a chain nobody can search later.

It is read on a phone, in a list, in under ten seconds on the first pass. In that time the reader is answering three questions: did I get an answer, when does the thing happen, and what do I have to do. A reply that needs a second careful read to yield any of those has failed, however well written it is.

That is why the first line matters more than the rest combined, and why a preview beginning with thanks for reaching out wastes the only guaranteed impression you get. It is also why numbers, dates and names should appear as themselves rather than buried in a clause: the week of the fifth is retrievable at a glance, early in the new year is not. When somebody has to forward your reply to a colleague, the test is whether the forwarded message stands alone. If your answer only makes sense with the message above it, the person forwarding has to write an explanation, and half the time they will get it wrong.

A reply resolves something. A holding note buys time and does exactly two things: confirms receipt and gives a date. Keeping them separate is what stops holding notes growing into half answers that commit you to a position you have not thought through. If you cannot give a date, give the date by which you will give a date, which sounds absurd and is still better than an open ended soon.

A formal letter, or a reply written as one, is a different instrument. It is deliberately cool in register because its job is to be read later by somebody who was not part of the conversation: a solicitor, an insurer, an adjudicator. Sending one where a normal reply would do is an escalation in itself, and recipients read it that way. The working rule is that warmth costs nothing until precision starts mattering more, and you generally know which situation you are in before you start typing.

Read the draft as the recipient rather than as the author. The reliable method is to read only the first line and the last line and ask whether those two carry the whole message. If they do not, move something. Then count the apologies. More than one means the second is doing no work, and the reader has started attending to your discomfort instead of the resolution.

Then check the facts that create obligations: dates, amounts, names, spellings, the deadline you have just committed to. A wrong date in a reassuring email costs more than a blunt reply with the right one. Check what you are sending as well as what you wrote, because a forwarded chain often contains internal comments the recipient should never see, and reply all sends those to everybody on it.

Last, read it aloud once if the tone is delicate. Written sarcasm and clipped politeness are nearly invisible on screen and unmistakable in the mouth. Anything that sounds cold when spoken will read colder to somebody already braced for bad news.