Rewrite an email to sound professional
Turn a blunt draft into something you can actually send — keeping your point and your voice, minus the heat, hedging and filler.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your prompt
Model-agnostic — works in Claude, ChatGPT, Gemini or any AI chat.
Why this prompt works
- →"Keep every factual point" stops the rewrite from sanding off the substance along with the tone — the usual failure of "make this nicer".
- →Banning added flattery and apologies keeps the result honest to what you actually said; models otherwise pad conflict emails with un-meant pleasantries.
- →"Shorter than my draft" is a hard, checkable constraint — professional rewrites that grow are usually worse.
Part by part
- keep every factual point I made
- Rewriting for tone is where facts quietly disappear, because the sentence carrying an inconvenient detail is often the one that read as heated.
- remove heat, blame and filler
- Three specific things to remove, which is enforceable. Asking for a professional tone is not, because professional is read as formal.
- do not add flattery or apologies I didn't make
- The instruction that protects your position. An inserted apology concedes something you did not intend to concede.
- Write it in my voice, not corporate boilerplate
- Guards against the default register, which is where every rewritten email converges if nothing stops it.
Common mistakes
Make this email sound more professional.Professional is read as formal, so the rewrite adds hedging, passive constructions and an apology you did not make. It is longer, less clear, and concedes ground.
Soften this email.Softening past a point removes the request. The most common failure in a difficult email is that the recipient finishes it without knowing what was being asked.
Rewrite this email.Without stating what you need from the recipient, the rewrite polishes the prose and may not contain a clear ask at all — which was usually the problem with the draft.
Questions
Why say what I need from them?
Because it is what the email is for, and a rewrite optimising for tone will bury it. Stating the goal separately means the rewritten version is built around the request rather than around the mood.
Will it actually keep my voice?
Partially. It holds better in a short email than a long one, and the instruction helps considerably — but expect to change a few phrases back. The structure is usually the improvement, not the wording.
Should I send an angry email at all?
Write it, then rewrite it, then wait an hour before sending. The rewriting is genuinely useful; the delay is what most often changes whether you send it, and that is usually the better decision.
What if the rewrite removes something I meant?
Put it back. The constraint says keep every factual point, and a firm statement of consequence is a fact rather than heat — models are cautious and will sometimes remove it anyway.