What does a professional email look like?

A subject line that summarises the message, a one-line greeting, the point inside the first two sentences, supporting detail in short paragraphs, one clear ask with a date, and a plain sign-off. Under 200 words covers almost everything, and that shape holds across every scenario here.

How do I write a professional email saying no?

Decline in the first sentence so nobody has to hunt for the answer, give one honest reason without over-explaining it, and offer an alternative only if you would genuinely deliver it. Padding a no with paragraphs of apology reads as reluctance and invites a negotiation you did not want.

How do I deliver bad news over email?

Lead with the fact, then the cause, then your plan, then what you need from them. Never open with context and reveal the problem in paragraph three — readers who feel managed stop trusting the rest of the message, including the parts that were good news.

Why is this free — what's the catch?

No catch and no signup. This tool is funded by EaseClaw, an AI agent that finds people publicly asking for what you sell and drafts your replies. If the free tool is useful, some people try the free trial. That's the whole business model.

Professional Email Example Generator

Pick the situation, add two lines of context, get the whole email — subject line included.

Searching for a professional email example usually returns a page of samples written for nobody: “Dear Mr. Smith, I am writing to inform you that…”. They are useless, not because the structure is wrong but because the specifics are missing — and specifics are the entire difference between an email that gets answered and one that gets archived. This tool builds the example around your situation instead. Pick the scenario, add a couple of lines about who it is for and what happened, and you get one complete email with a subject line, ready to send after a read-through.

The six emails every professional actually has to write

The introduction: who you are in half a line, why you are worth a reply in the other half. Anything longer turns into a résumé that nobody asked to receive.
The ask: put it in the first two lines, make it specific, and name the deadline. Requests buried under justification read as either unimportant or quietly manipulative.
Saying no: decline in the first sentence, give one real reason, and offer an alternative only if it is real. A soft no stretched over four paragraphs wastes everybody's week.
Bad news: lead with the fact, then the cause, then what you are doing about it. Burying the problem under context makes the reader trust the rest of the email less once they find it.
The thank you: name the specific thing they did and the specific effect it had. Generic gratitude is worth roughly what it costs to write, which is nothing at all.
All six: one purpose per email, and a subject line that summarises rather than labels. “Update” is not a subject line, it is a category.

Example output

Scenario + context: Delivering bad news · Client's site migration will miss the agreed launch date by nine days because their old host is slow releasing DNS.

Subject: Launch moving to 24 March — why, and what happens next

Hi Tom,

The migration will miss the 15 March launch. The new date is 24 March, and I'd rather you heard that today than on the 14th.

What happened: your current host requires a written DNS release and quotes seven working days for it. We submitted on 3 March. They've confirmed receipt and won't accelerate.

What we're doing: the staging site is finished and frozen, so nothing else slips while we wait. I've asked for written confirmation of their release date and will forward it the moment it arrives. If it lands early, we launch early.

What I need from you: nothing today. If you'd like to escalate with the host, I'll send you the ticket reference.

The delay is on the calendar, not on the work.

Thanks,
Ana

(Example output — yours is generated from the scenario and context you enter.)

Frequently asked questions

What does a professional email look like?: A subject line that summarises the message, a one-line greeting, the point inside the first two sentences, supporting detail in short paragraphs, one clear ask with a date, and a plain sign-off. Under 200 words covers almost everything, and that shape holds across every scenario here.
How do I write a professional email saying no?: Decline in the first sentence so nobody has to hunt for the answer, give one honest reason without over-explaining it, and offer an alternative only if you would genuinely deliver it. Padding a no with paragraphs of apology reads as reluctance and invites a negotiation you did not want.
How do I deliver bad news over email?: Lead with the fact, then the cause, then your plan, then what you need from them. Never open with context and reveal the problem in paragraph three — readers who feel managed stop trusting the rest of the message, including the parts that were good news.
Why is this free — what's the catch?: No catch and no signup. This tool is funded by EaseClaw, an AI agent that finds people publicly asking for what you sell and drafts your replies. If the free tool is useful, some people try the free trial. That's the whole business model.

More free tools

Professional Email RewriterPaste the rough version. Get the one you can send — and a note on what changed.Follow-Up Email GeneratorThree follow-ups that don't start with “Just checking in”.Sales Email Templates + AI PersonalizerTen skeletons that work, and an AI that puts your prospect's flesh on them.

All free tools →