AI prompts for emails: 12 prompts for requests, replies, hard messages and follow-ups

Twelve prompts that make AI write emails the way good writers do, with the point first, a word limit and nothing invented, plus which tool to use inside Gmail and Outlook.

The short answer

The best AI prompts for emails put the request or news first, name the reader and relationship, set a word limit, list what must not be said and ask the AI to flag gaps instead of inventing dates or promises. The 12 prompts here cover requests, updates, introductions, batch replies, thread summaries, follow-ups, saying no, angry emails, bad news, executive emails, onboarding sequences and meeting recaps. They work in ChatGPT, Claude, Google Gemini in Gmail and Microsoft Copilot in Outlook.

What makes a good AI prompt for emails

Email is the most common thing people ask AI to help with at work, and the most common place AI writing goes wrong. Ask "write an email to my boss about the project" and you get a polite, padded message that buries the point. The 12 prompts for emails on this page fix that by doing what a good writer does: they put the request or the news first, set a word limit, list what must not be said, and tell the AI exactly who the reader is.

Each prompt follows the structure OpenAI and Anthropic recommend in their prompting guides: clear instructions, the context the model cannot guess, explicit rules and a defined output. Several prompts tell the AI to write [CHECK], [OWNER?] or flag a question rather than fill a gap. In email, an invented date or promise can cause real trouble, so keep those rules in.

The prompts work in ChatGPT, Claude, Gemini and Microsoft Copilot. They are grouped into four jobs: writing new emails, managing your inbox, difficult emails, and emails to customers and senior stakeholders.

Prompts for writing clear work emails

The request prompt is the one to learn first. It puts the ask in the first two sentences, explains the deadline once with a reason and bans apologetic openers. Requests written like this get faster answers, because the reader knows in seconds what you need and why.

The update prompt turns bullet points into a status email with a one-line headline (on track, at risk or off track) and three sections: Done, Next and Need from you. That shape works for almost any recurring update. The introduction prompt uses the double opt-in convention, where you check with both people before connecting them, and gives each person a specific reason to reply.

Prompts for replying and managing your inbox

The batch reply prompt is where most people save real time. Paste several emails with a one-line note on what you want to say to each, and get all the replies back labelled by ID. The XML-style tags (<email id="1">, <my_note id="1">) keep each email and its note together; Anthropic's guide recommends tags like these whenever a prompt mixes several pieces of material.

The thread summary prompt is built for the moment you are added to a 40-message chain. It lists decisions, open questions and, most usefully, what you personally owe, with the exact line where you were asked. Check those quotes against the thread: they are the fastest way to confirm the summary is right.

If you would rather not copy and paste, use the assistant built into your email. Gemini works inside Gmail from the Google AI Plus plan, and Copilot works in the Outlook desktop app with a Microsoft 365 Personal, Family, Premium or Pro subscription (on Family, only the subscription owner gets the AI features). ChatGPT added iCloud Mail and Calendar plugins in October 2026 on all plans, which can find emails and catch you up on your inbox. The prompts on this page work in all of them.

Prompts for difficult emails

Difficult emails are where AI help is most valuable, because the hard part is emotional rather than technical. The "say no" prompt separates your real reason from the reason you can share, so you never accidentally put the private one in writing. The angry email prompt first breaks the complaint into specific points and the emotion behind each, then writes a calm reply that commits only to what you listed.

The bad news prompt follows the rule that crisis communicators use: news first, reason second, plan third. It bans euphemisms that make readers trust you less. Always reread a difficult email the next morning if you can, and never let the AI promise a remedy you did not authorise.

Prompts for customer and executive emails

Senior readers decide from the preview. The executive prompt puts the decision in the subject line and the ask plus your recommendation in the first sentence, then the options in three bullets. If you only change one habit after reading this page, make it this one.

The onboarding sequence prompt asks you for the single action that predicts customers stay, then builds four emails around it. That is a far better brief than "write a welcome series". The meeting follow-up prompt turns notes or a transcript into a recap with an action table and flags any action without an owner or date. On paid ChatGPT plans you can upload a meeting recording directly, since audio uploads arrived on 6 October 2026.

How to adapt these email prompts

  1. Describe the reader and the relationship. "My skip-level manager, who prefers bullet points and dislikes surprises" changes the tone and structure more than any adjective.
  2. Paste two emails you sent and liked. Examples are the most reliable way to set tone, according to Anthropic's guide.
  3. Set the length and give the reason. "Under 100 words because they read on a phone between meetings" works better than "be concise".
  4. List what must not be said. Prices, dates, legal positions and anything confidential. The AI cannot know these unless you tell it.
  5. Save your best versions. Keep your three most-used email prompts in a Claude Project, a ChatGPT project or a Gemini skill (Gems become read-only on 17 November 2026), or in our prompt kits.

For a full walkthrough, read how to write better emails with AI.

Which AI tool works best for emails, and why

The best tool for email is usually the one inside your inbox, because context matters more than raw writing quality. Gemini is the right pick for Gmail users on Google AI Plus or higher. Microsoft Copilot is the pick for Outlook, and with a Microsoft 365 Copilot licence it can use your organisation's mail and files through Microsoft Graph, under enterprise data protection. Our guides to Gemini and Copilot cover both.

For difficult emails and anything where tone matters, Claude by Anthropic writes the most natural drafts in our view; see the Claude guide. ChatGPT is the strongest all-rounder if you also need it for files and meeting recordings. Grammarly is the lightest option: it checks emails as you type, and its Pro plan adds tone adjustment and full-sentence rewrites.

Privacy matters more with email than almost any other task, because threads contain other people's personal data. Personal accounts of ChatGPT, Claude, Gemini and Grammarly can use your content to improve their models unless you change the setting. Use a work plan where training is off by default, or switch the setting off before pasting anyone else's messages. For the full ranking, read the best AI for writing emails.

Prompts to copy

Write a clear request email that gets a yes

Write an email to [name, role, relationship to me] asking for [specific request]. Why I need it: [reason]. Deadline: [date and why]. What it costs them: [time or effort involved]. What I can offer in return or to make it easier: [offer]. Rules: the request goes in the first two sentences. Under 120 words. One question only. Include the deadline once, with the reason. Friendly but not apologetic: no 'sorry to bother you' or 'I know you're busy'. Give me a subject line under 8 words that says what I need.

You get: A short request email with the ask up front and a subject line that gets it opened

Turn bullet points into a well-structured update

Turn these notes into an email update for [audience, e.g. my manager and two stakeholders] about [project]: <notes> [paste bullet points] </notes> Structure: a one-line status (on track, at risk or off track) with the reason, then three short sections headed Done, Next and Need from you. Bold any decision or date. Keep it under 200 words so it can be read on a phone. Do not add progress or dates that are not in my notes; write [CHECK] where something seems missing.

You get: A scannable status update with a clear headline and decisions in bold

Write an email introduction between two people

Write a double opt-in introduction email connecting [person A, role, company] and [person B, role, company]. Why they should talk: [specific reason]. What each could get from it: [A gets..., B gets...]. I have already checked with [both / A only]. If I have only checked with A, write a short opt-in email to B first, asking permission to share their details, and then the introduction. Under 120 words. Start with why the introduction is worth their time, give each person one line of context, suggest a concrete next step, and then step out with a line such as 'I'll let you two take it from here.' Subject line format: Intro: [A] and [B] on [topic].

You get: A warm, specific introduction both people will want to answer

Draft replies to a batch of emails

Below are [number] emails I need to answer, separated by tags. For each one, I have added a note on what I want to say. <email id="1">[paste email]</email> <my_note id="1">[e.g. yes, but only from March]</my_note> <email id="2">[paste]</email> <my_note id="2">[e.g. politely decline, suggest Sam]</my_note> Write a reply to each in my voice: [two adjectives, e.g. warm and brisk]. Each reply under 80 words, answering every question the sender asked. Label replies by ID. If an email asks something my note does not cover, flag it at the top of that reply instead of guessing.

You get: Ready replies to a stack of emails, with unanswered questions flagged

Summarise a long email thread and what you owe

<thread> [paste the whole email thread, oldest first] </thread> I am [name] in this thread. Summarise it for me in this format: 1. What this is about, in one sentence. 2. Decisions made so far, with who made them and when. 3. Open questions, with who is waiting on whom. 4. What I personally have been asked to do, with any deadline. 5. A suggested reply from me, under 100 words, that moves things forward. Quote the exact line where each action for me was requested.

You get: A thread summary, your actions with the original wording, and a draft reply

Write a polite follow-up when someone has gone quiet

I emailed [name, role] on [date] about [topic] and have had no reply. Here is my original email: [paste]. This matters because [reason]. It is the [first / second / third] follow-up. Write a follow-up under 70 words that adds something useful (a new detail, an easier option or a clear deadline), makes replying easy (for example a yes or no question), and does not use 'just following up', 'circling back' or guilt. If it is the third follow-up, make it a friendly close-the-loop message that leaves the door open.

You get: A follow-up that gives the reader a reason and an easy way to reply

Say no without damaging the relationship

I need to decline [request] from [person and relationship]. The real reason: [reason, which may be private]. What I can say publicly: [acceptable reason]. What I can offer instead: [alternative, or nothing]. Write two versions under 100 words: one short and firm, one warmer with the alternative. Each must say no clearly in the first two sentences, not over-explain, not promise anything I cannot do, and end on the relationship rather than the refusal.

You get: Two clear, kind ways to say no, without loopholes

Reply to an angry email calmly

<email> [paste angry email] </email> Context: [what actually happened, what we got wrong and what we did not]. What I can offer: [remedy]. What I cannot offer: [limits]. You are an experienced customer relations manager. First, list the sender's specific complaints and the emotion behind each, in a short table. Then write a reply under 180 words that acknowledges what we got wrong without blaming anyone, corrects any factual misunderstanding gently, states exactly what happens next and by when, and gives a direct contact. No 'we apologise for any inconvenience', no defensiveness and no promises beyond what I listed.

You get: A complaint breakdown and a calm, specific reply that de-escalates

Deliver bad news by email

I have to tell [audience, e.g. a client / my team] that [bad news, e.g. the launch is delayed by three weeks]. Why: [honest reason]. Impact on them: [impact]. What we are doing about it: [actions]. What they need to do, if anything: [action]. Write the email under 200 words. Put the news in the first sentence, then the reason in plain words, then the impact and plan. Take responsibility where it is ours. Avoid euphemisms such as 'slight adjustment' or 'exciting new timeline'. Offer a call for questions. Then give me a one-line subject that is honest without being alarming.

You get: A straightforward bad-news email that keeps trust intact

Write an email to a busy executive

I need [executive's name and role] to [decision or action]. Background they do not know: [context]. Options: [A, B, C with costs or trade-offs]. My recommendation: [option] because [reason]. Deadline for the decision: [date]. Write the email so it can be understood from the preview alone. Format: subject line that states the decision needed, a first sentence with the ask and my recommendation, then three bullets covering the options, then one line on what happens if no decision is made by the deadline. Under 150 words. No background story before the ask.

You get: An executive-ready email where the decision is clear from the preview

Write a customer onboarding email sequence

You are a lifecycle marketer. Write a 4-email onboarding sequence for new customers of [product] who signed up for [reason]. The single action that predicts they stay is [key action, e.g. inviting a teammate]. Common reason people get stuck: [problem]. For each email give: day to send, subject line, preview text, body under 120 words, and one call to action. Email 1 welcomes and points to the key action, email 2 removes the common blocker, email 3 shares this short customer example: [paste a real customer story with permission to use it], email 4 checks in personally from [name]. Write in a [tone] voice.

You get: A four-email onboarding sequence built around the action that keeps customers

Turn a meeting into a follow-up email

<notes> [paste meeting notes or transcript] </notes> Write a follow-up email to everyone who attended the [meeting name] on [date]. Include: a one-line purpose, decisions made, action items as a table with owner and due date, open questions, and the date of the next meeting if one was agreed. Use only what is in the notes; if an action has no owner or date, write [OWNER?] or [DATE?]. Under 200 words plus the table.

You get: A meeting recap with an action table and missing owners flagged

Start the ChatGPT lessons Start the Claude lessons