An email that goes unanswered has usually not been ignored. It has been opened, found to require more effort than the reader had available at that moment, and mentally filed under “later” — which is where email goes to die.
What usually helps is not persistence. It is writing something that can be answered in the ninety seconds the reader actually has.
Put the ask in the first line
The most common structural mistake is burying the request under context. The writer builds the case first, because that is how they thought about it. The reader gets three paragraphs of background and no idea what they are being asked for, and stops.
Invert it. First line: what you want, and by when. Then the context, for the reader who needs it.
Can you approve the revised budget by Thursday? Details below.
Someone who already trusts you replies in four seconds. Someone who needs the detail reads on. Both of them can act.
Ask for one thing
An email containing three requests gets answered on the easiest one, or on none, because a partial reply feels worse than no reply and the reader defers the whole thing.
If you need three things from someone, that is three emails — or one email with three numbered questions, which lets them answer in three lines. Numbering is not fussiness: it gives the reader an obvious structure for the reply and makes it visible when one has been missed.
Make the reply cheap
The best question is one that can be answered with a word.
“What do you think about the timeline?” requires the reader to compose an opinion from nothing. “Does 14 October work, or would you rather we pushed to the 21st?” can be answered with a date. Same information, a fraction of the effort.
Where you can, do the work of proposing. A draft someone can correct is far easier to respond to than a blank space they have to fill.
Length is a signal about effort
Long emails signal that responding will be expensive. If something genuinely needs a thousand words, it needs a document with a link and a two-line email explaining why the reader should open it.
The pattern that works: what I need, when I need it, why it matters in one sentence, and a link to everything else.
Say what happens if they do nothing
This is the most under-used sentence in professional email, and it works because it converts a vague request into a decision.
If I don’t hear back by Friday I’ll go ahead with option B.
The reader now knows the cost of silence. Someone who is fine with option B can say nothing and the work proceeds. Someone who is not will reply within the hour. Either way you stop waiting.
Used honestly this is a courtesy. Used as a threat to force agreement, people notice quickly.
Subject lines that do work
The subject line is read in a list, out of context, sometimes days later. It should say what the email is for, not what it is about.
“Approval needed: revised budget, by Thu” beats “Budget”. “FYI: no action needed — contract signed” beats “Update”, and tells someone they can leave it unread with a clear conscience, which they will remember kindly.
Write it the way public bodies are told to
The people who have thought hardest about being understood on the first read are the ones who write for the general public, because they cannot rely on the reader trying twice.
Both the US government’s plain language guidelines and the GOV.UK content design guidance land on the same short list: short sentences, everyday words, the important thing first, and the active voice so it is clear who is supposed to do what.
That last one matters more in email than anywhere else. “It would be good if the figures could be reviewed” leaves the reader unsure whether they are the one reviewing them. “Can you review the figures by Thursday?” is much harder to misread, and it is shorter.
The instinct to soften a request into passive vagueness is well meant — it feels less demanding. It mostly produces emails that get read twice and answered never.
When to stop emailing
Two signals mean writing has stopped working.
The thread is getting longer without getting closer. Three rounds without convergence usually means the disagreement is about something none of the messages have named. A ten-minute conversation will surface it.
The subject is emotionally loaded. Feedback, disagreement and bad news all read colder in writing than intended, and the reader supplies a tone you did not write.
The follow-up
If there is no reply, the effective follow-up is not “just checking in.” It repeats the ask, makes it easier, and gives an exit.
Still need a yes or no on the budget — happy to go with option B if you’d rather not spend time on it. Original below.
If two follow-ups produce nothing, the answer is that this is not a priority for them, and the useful move is to change what you are asking for or ask someone else. Continuing to send the same email is the definition of hoping.
For what to do when the conversation genuinely needs to be a meeting, see the meeting that should have been an email. There is more on managing digital noise in notifications worth turning off at work.
