Why most work emails fail
An email that gets no reply usually made one of three mistakes: the reader could not tell what was being asked, could not tell whether it was for them, or could not tell how long it would take. None of those is a writing-quality problem. They are structural, which is why polishing the prose of a bad email rarely helps.
The fix is to decide the ask before you write a word. One request, stated once, with everything the reader needs to act on it in the same message. The [msm_tool slug="email-writer"] drafts around that shape, but the shape is yours to choose — a model cannot know what you actually want from someone.
Subject lines are routing instructions
Your subject line is read in a list of forty, on a phone, in about a second. It decides whether the message is opened today, opened Friday, or never.
- Say the thing. Invoice 2841 unpaid — due 14 March beats Quick question every time.
- Front-load. Mobile clients cut around thirty-five characters. Put the subject and the stakes first, context second.
- Signal the cost. Two minutes, no action needed, decision needed by Thursday all help someone triage honestly.
- Never use false urgency. URGENT on something that is not works once and costs you every subsequent message.
The structure that gets answered
- The ask, in the first two lines. Before any pleasantry, before background. If the reader stops after two lines — and many will — they should still know what you want.
- The minimum context. Only what is needed to act. Everything else is a link or an attachment.
- The deadline, with a reason. By Thursday, because the print run books Friday is answerable. ASAP is not a date and gets treated as none.
- One clear next step. Reply, approve, book a slot. Three possible actions produce zero.
Length follows from this rather than being a target. If the ask is simple, four sentences is a complete email and padding it is a discourtesy.
Register: warmer than you think, shorter than you think
Written text loses tone. A sentence that sounded brisk in your head reads as curt on a screen, and this gets worse across cultures and seniority. The correction is small and cheap: one line of genuine warmth at the top, plain verbs in the middle, and no passive-aggression anywhere.
Some phrases carry more edge than people intend. As previously mentioned, per my last email and just circling back all read as accusations, because that is how they are most often used. If you mean to escalate, escalate openly. If you do not, drop them.
Equally, formality is not politeness. Long Latinate constructions distance the reader without softening anything. We are unable to accommodate this request and we can't do this, but here's what we can do deliver the same refusal; only one of them keeps a working relationship.
Follow-ups, and when to stop
Silence is almost never a message. Inboxes are overloaded and your email was probably read on a phone, mentally filed, and lost. So follow up — but follow up usefully.
Wait a working week for something non-urgent. Reply in the same thread so the context travels with it. Restate the ask in one sentence rather than writing bumping this, which asks the reader to scroll and re-read. Add anything that has changed since.
Two follow-ups is the usual limit. After that the answer is a no that nobody wanted to type, and the respectful move is a short closing note: assuming this is not a priority right now — happy to pick it up if that changes. That sentence has restarted more stalled threads than any third chase ever will.
Difficult emails deserve a slower pass
Bad news, refusals, complaints and anything involving money or a contract should be drafted, left, and reread before sending. Generated drafts are useful here precisely because they are unemotional — but they are also unaware of the history between you and the recipient, which is usually the whole substance of a difficult message.
Three checks before sending one of these: is there a sentence that only makes sense if you already know how annoyed I am; would I be comfortable if this were forwarded to the person it discusses; and have I stated one decision or left the reader guessing which of three things I meant?
Editing a generated draft
Cut the opening line. Generated emails almost always begin with a sentence of throat-clearing that says nothing. Delete it and start at the ask.
Check every specific. Names, dates, amounts, invoice numbers and job titles are precisely what a model will fill in confidently and wrongly, and an email with the wrong figure in it is worse than no email.
Then put one sentence of your own in. The version that sounds like you is the one that gets a human reply.
What you type goes from your browser to the provider you chose, under their terms, and never through this site — worth remembering before drafting anything about a named colleague or an unannounced deal.