The email writing prompts below cover the emails people put off: following up after silence, saying no, replying to an angry message, apologizing, asking a busy person for something and catching up on a long thread. Each one asks you for the facts and the outcome you want, so the draft says what you mean in fewer words.
How to use these prompts
Every prompt works in ChatGPT, Claude or Gemini. Replace the blanks in double braces, or keep the default after the colon: {{tone:warm but direct}} means "warm but direct" unless you change it.
Most bad AI emails come from thin input. The model knows nothing about the reader, the history or what you can promise, so it fills the gaps with polite filler. Anthropic's prompting best practices suggest a simple test: show your prompt to a colleague with minimal context, and if they would be confused, the model will be too. OpenAI's prompt guide for ChatGPT at work makes the same point with a different picture: treat the prompt like a handoff to a new intern.
So before you run a prompt, write down three things: who is reading, what you want them to do after reading, and the facts the email must include. Then always read the draft once as the recipient.
For one-off edits of a draft you already wrote, the best ChatGPT prompts include a short "clearer and shorter" rewrite.
Which prompts help you write emails people answer?
1. Ask a busy person for something
For a request to someone senior, external or swamped. The ask goes first, and saying yes takes one line.
Write an email asking {{recipient:a VP at a partner company}} for
{{ask:20 minutes to review our integration plan}}.
Context they need: {{context}}
Why it matters to them, not just to me: {{their_benefit}}
Deadline, if any: {{deadline:no hard deadline}}
Rules: put the request in the first two sentences. Keep it under
{{length:120 words}}. Make it easy to say yes with a one-line reply,
for example by offering two specific times. No "I hope this finds you
well". Give me two subject lines that state the ask.
2. Follow up after no reply
For the second or third nudge. It adds something new each time instead of just "bumping this".
I emailed {{recipient:a hiring manager}} {{days:8}} days ago about
{{topic:the product designer role}} and got no reply.
My original email:
{{original_email}}
Write a short follow-up (under 80 words) that adds one new, useful thing
(a fact, a link, a smaller ask or an easy way out), doesn't guilt them,
and keeps the same thread. Give two versions: one friendly, one more
direct. Suggest when to send a final follow-up if this one gets no reply.
3. Turn rough bullets into an email
When you know what to say but not how to say it. It keeps your facts and order and adds only the glue.
Turn these bullet points into an email to {{recipient:my team}}.
Bullets:
{{bullets}}
Keep every fact and do not add new ones. Lead with the point the reader
most needs. Use short paragraphs, and keep any list that is clearer as a
list. Tone: {{tone:warm but direct}}. End with the one action I need from
them, with a date if I gave one.
Which prompts help with difficult emails?
4. Say no without burning the bridge
For declining a request, a meeting, a project or a vendor. A clear no with a reason beats a vague maybe.
Help me decline this request politely and clearly.
The request: {{request}}
Who asked: {{relationship:a colleague in another team}}
My real reason: {{reason}}
What I can offer instead, if anything: {{alternative:nothing right now}}
Write a reply under 100 words that says no in the first two sentences,
gives a short honest reason, and offers the alternative if there is one.
No over-apologizing and no "maybe later" unless I said so.
5. Reply to an angry email
Paste the angry message and the facts. The model is good at spotting defensive phrasing you would miss.
Here is an angry email I received and the facts of what happened.
Their email:
{{angry_email}}
What actually happened: {{facts}}
What I can offer: {{offer:a call this week and a fix by Friday}}
What I can't do: {{limits}}
Draft a calm reply that acknowledges the specific problem in their
words, takes responsibility for what was ours, corrects any facts gently,
and ends with a concrete next step and date. No blame, no corporate
phrases like "we apologize for any inconvenience". Then list any line
in my facts that could make things worse if I included it.
6. Apologize for a mistake
For a missed deadline, a wrong invoice or a bug a client found. A good apology names the mistake, the fix and what changes.
Write an apology email to {{recipient:a client}} about
{{mistake:sending last month's report with the wrong figures}}.
Impact on them: {{impact}}
What we've done to fix it: {{fix}}
What we'll do so it doesn't happen again: {{prevention}}
Under 150 words. Name the mistake plainly in the first sentence, don't
minimize it, and don't over-explain how it happened. Tone:
{{tone:sincere and professional}}.
7. Push back on scope or a deadline
For when you can't take on more without something giving. It frames the trade-off so the other person chooses.
I've been asked to {{request:add three features before the launch date}}.
I can't do all of it by {{date:the 15th}} without a trade-off.
Current commitments: {{commitments}}
Options I can live with: {{options}}
Write an email to {{recipient:my manager}} that restates the request so
they know I understood it, explains the constraint in one or two
sentences, lays out two or three options with what each costs, and asks
them to pick one by {{decision_date:Thursday}}. Confident, not defensive.
Which prompts handle everyday work emails?
8. Introduce two people
For a double-opt-in intro that both people will actually act on.
Write an introduction email connecting {{person_a}} and {{person_b}}.
Who A is and why they want to meet: {{a_context}}
Who B is and what's in it for them: {{b_context}}
Keep it under 120 words. One line on each person, the specific reason
they should talk, and a suggested next step. Address both by first name.
Then write a short message I can send B first to ask if they're happy to
be introduced.
9. Announce a change to a team
For a new process, tool, policy or org change. It answers the questions people will otherwise ask in replies.
Write an email announcing {{change:that we're moving from weekly to biweekly releases}}
to {{audience:the engineering and support teams}}.
Details: {{details}}
Starts: {{start_date}}
Structure: what is changing (two sentences), why, what each audience
needs to do and by when, what stays the same, and who to ask. Add a
short FAQ with the three questions people are most likely to reply
with. Under 250 words, plain language, no hype.
10. Catch up on a long thread and reply
For the 40-message thread you were just added to. It separates what was decided from what still needs you.
Below is an email thread I've just been added to. I'm {{my_role:the project lead}}.
{{thread}}
First, summarize it in five bullet points: what this is about, what has
been decided, what is still open, who is waiting on whom, and any
deadline. Quote the line where each decision was made. Then draft my
reply: answer anything addressed to me, and ask one question about the
most important open point. Under 120 words.
11. Write a subject line and opening that get read
For any email that has to survive a crowded inbox.
Here is an email I'm about to send to {{recipient:the whole company}}.
{{email}}
Write 5 subject lines under 50 characters that say what the email is
about and what the reader should do. Then rewrite only the first two
sentences so a reader who stops there still gets the main point.
Don't change the rest.
Which prompts make emails sound like you?
12. Learn my email voice
Run it once, save the result, and paste the voice notes into future prompts. Anthropic's guide recommends 3 to 5 examples for best results.
Below are {{count:4}} emails I wrote and was happy with.
{{examples}}
Describe my email style as a short list of rules someone else could
follow: typical length, greeting and sign-off, sentence length, how I
make requests, words I use often, and things I never do. Then write
{{new_email:a reply declining a conference invite}} following those rules.
13. Adjust tone for a different reader
Same message, different audience. Useful when an email for your team needs to go to a client or an executive.
Rewrite this email for {{new_audience:a senior executive at a client}}.
It was written for {{old_audience:my own team}}.
{{email}}
Keep every fact. Change the length, level of detail, jargon and tone to
fit the new reader. {{constraint:Keep it under 100 words.}} Show the
rewrite, then a short list of what you removed so I can check nothing
important went.
14. Check a draft before sending
The last pass for any email that matters. It catches the problems that cause awkward replies.
Review this email before I send it to {{recipient:a new client}}.
{{draft}}
Check for: an unclear ask, a missing date or owner, anything that could
read as rude or passive-aggressive, facts or numbers I should double
check, names or details that look wrong, and sentences you could cut.
List problems with the exact line, then show a corrected version.
Don't change my voice.
How do you get better emails from AI?
Give the model the outcome, not just the topic. "Write an email about the delay" gets a generic note. "Get the client to approve the new date by Friday without losing their trust" gets an email built around that goal.
Paste the real material. The original message, the thread, the numbers. A model that has the thread writes a reply that fits it; a model that has a summary guesses.
Ask for less. Most drafts improve when you cut the length target in half. If the first draft is close, reply with one specific fix ("too formal", "move the ask to the top") rather than starting over.
Check facts and names yourself. A model can confidently fill in a date, a figure or a promise you never made. If a draft includes anything you didn't give it, delete it or confirm it.
Make your favorite one a skill
If you send the same kind of email every week, such as follow-ups or status notes, turn the prompt into a skill with your voice rules built in, so Claude, Claude Code or Codex applies them every time. Paste the prompt and your voice notes from prompt 12 into the free SKILL.md generator. For recurring company updates, the internal comms skill already has fixed formats. Related collections: meeting notes prompts for the follow-up after a call and sales prompts for prospecting emails.
To keep these one search away, save them in Kipt with their blanks, tag them by situation, and press ⌘K to find the one you need. Your library is plain Markdown in a private GitHub repo you own.