The best AI email writing prompts by situation share one shape — a role, the pasted thread, one specific task, a tone, a length cap, and an anti-hallucination rule. This library gives 50 prompts across follow-up, cold outreach, declining, apology, internal updates, sales discovery, meetings, and customer support to copy, adapt, and send.
50 AI email writing prompts by situation — follow-up, cold, decline, apology, sales, meetings, support — copy, adapt, send. A reusable library.
If you have ever typed "write a follow-up email" into ChatGPT and gotten back three paragraphs of hollow corporate prose, the problem was not the model. It was the prompt. Vague requests get vague answers. Specific ones get drafts you can almost send.
This is a library of 50 AI email writing prompts by situation — follow-up, cold outreach, politely declining, apologising, internal updates, sales discovery, meetings, and customer support. Each is written to be lifted and adapted: a scaffold with brackets for the parts that change, not a generic wish. Copy the one that fits, paste in the actual thread, and send the result to any AI tool — ChatGPT, Claude, Gemini, Copilot — or an AI-native inbox that already has the thread loaded.
We build AI Emaily, an AI-native email client, so we watch a lot of people use AI to write email. What follows are the prompts that keep working — grouped so you find the one you need in seconds, shaped so the model has enough to draft something usable on the first try.
Most "AI prompts for email" pages on the web are generic-writing prompts in disguise: "Write a professional email about [topic]." They rank on query volume, not on quality, and they produce exactly the drafts they complain about elsewhere on the page.
This one is organised by the situation you are actually in when you reach for AI. You are not writing "a professional email" — you are declining a vendor without burning the relationship, apologising for a missed deadline without over-apologising, or nudging a stalled deal without sounding desperate. Group by situation and the prompts get sharper, because each one can carry the constraints and cautions that its specific moment needs.
Every prompt below follows the same shape: a role, the context you paste in, one specific task, a tone, a length cap, and — where it matters — an instruction to use bracketed placeholders instead of inventing facts. That last rule is the single most important line in any email prompt in 2026. A hallucinated deadline or price in a message you actually send is a credibility problem, not a harmless miss.
Read once, then bookmark
Copy the prompts you use most into a notes app or a text-expander (TextExpander, Raycast, Alfred). Six prompts you can trigger in two keystrokes beat a bookmarked list you never open.
Follow-ups are where AI earns its keep — high volume, boring template, tone-sensitive. All six assume you paste the last message; without it, expect "just circling back."
Six follow-up prompts (copy, fill brackets, paste your thread)
1.1 Cold prospect, three-day silenceYou are a friendly SDR. Write a two-sentence follow-up to [name] whose reply has not come in three days after my initial pitch below. Reference one detail I give you in [brackets], keep it under 40 words, end with a soft yes/no question, invent nothing.
1.2 Warm prospect, one week outYou are me — warm and direct. Draft a three-sentence follow-up to [name], who I spoke with a week ago about [topic] and has not replied. Reference our actual conversation from the paste below. No "just circling back." End with one clear next step.
1.3 Proposal follow-upDraft a two-paragraph follow-up to [name] on the proposal I sent [date]. Recap the one number they cared most about, name the specific decision on the table, and ask whether they want a 15-minute call to unblock any questions. Under 90 words, no pleasantries.
1.4 Meeting recap + next stepsYou are the meeting owner. From the call notes below, write a recap: one-line summary, three bulleted decisions, a small table of owners to actions to dates, and one line inviting corrections. Under 150 words. Use only what is in the notes.
1.5 Waiting on a decision-makerDraft a two-sentence reply to [name] who says the ask is now with [decision-maker]. Warm, not pushy: acknowledge, name a specific date to check back, and offer to send a one-slide summary they can forward. No cadence questions.
1.6 The break-up (final follow-up)Write a four-sentence "final follow-up" to [name] who has gone quiet after four attempts. Direct, no guilt, no drama. Say I will stop reaching out, name the door I am leaving open, and end with one specific value-add they can say yes to in a word.
Cold outreach lives on one line: why now and why them. Every prompt asks you to supply the trigger — a round, a hire, a talk, a post — because the model cannot invent one that is true. Skip the trigger and the email is not ready to send.
Six cold outreach prompts
2.1 Cold with a mutual connectionYou are me. Write a four-sentence cold email to [name] at [company], introduced through [mutual, relationship]. Reference the intro naturally, name the one problem I can help with, and ask for 15 minutes. No fake familiarity. Under 80 words.
2.2 Trigger-event cold emailDraft a three-sentence cold email to [name] triggered by [specific event — round, launch, hire, post]. Tie our value to that event in one line, one specific proof point in the next, and end with a yes/no ask for a call. Under 70 words.
2.3 Cold pitch for a demoYou are a founder writing to a peer, not a form. Cold email [name] at [company] pitching a 15-minute demo of [product]. Lead with the outcome we deliver for [their type of team], one line of proof, one line of ask. Under 75 words. No superlatives.
2.4 Investor cold introDraft a five-sentence cold email to [investor] with our one-line pitch, our stage, the traction figure [X], the round we are raising [Y], and a soft ask for a 20-minute intro call. No hype words. Attach nothing but the deck link I give you.
2.5 Guest post / podcast pitchCold email [host / editor] pitching [topic] for their [show / publication]. Reference a specific recent episode or article by title. Explain in one line why I am the right person and give three concrete angles. Under 120 words. Warm, not fawning.
2.6 Job cold outreachYou are me, a candidate for [role]. Draft a cold email to [hiring manager] at [company]. Two-sentence why-this-role (tie to a real fact about the team), two-sentence why-me with one measurable win, one-line ask to talk. Under 110 words. No "passionate."
The hardest email is the one that says no and keeps the relationship intact. All six prompts follow the same shape: one sentence of decline, one line of the real reason, one clear door left open — warm without hedging.
Six decline prompts
3.1 Decline a meeting (still open to email)Draft a three-sentence reply declining [name]'s meeting request. Warm and specific: name why (paste the reason), offer to handle it over email, and ask them to send the two or three questions they want answered. No apologies for being busy.
3.2 Decline a vendor proposal, door openYou are a procurement lead with a friendly relationship with this vendor. Reply to [name]'s proposal below declining for now. Give the real reason (budget timing / priority), name a specific revisit window, and thank them once. Under 90 words, one paragraph.
3.3 Decline a speaking invitationDraft a three-sentence reply declining a speaking slot at [event]. Warm and flattering without gushing. Reason: [true reason]. Offer either to be considered next year or to suggest one alternate speaker (do not invent a name).
3.4 Decline additional scope from a clientYou are the project lead. Reply to [client] who has asked for [out-of-scope work]. Acknowledge the request, explain in one line why it does not fit the current contract, and offer a specific path (change order, phase two, referral). Warm, firm, under 100 words.
3.5 Decline a job offerDraft a four-sentence reply declining [company]'s offer for [role]. Genuine gratitude, one honest reason (paste it), and a specific line about keeping in touch with [named person]. No "exciting opportunity elsewhere" cliché.
3.6 Decline an intro requestReply to [name] who has asked me to introduce them to [third party]. Two sentences: why I am not the right introducer this time (real reason from the paste), and one alternative — either a better path or a warm no. Do not invent a warmer connection than I have.
A good apology owns the miss in one sentence, states the fix as a fact, and stops. The common failure is apologising three times, which reads as anxiety rather than accountability. Every prompt caps the apology at one and leads with the fix.
Six apology prompts
4.1 Missed deadlineYou are the project lead. Draft a reply to [name] who is frustrated the [deliverable] slipped past [date]. Own the miss in one sentence, state the real cause in one honest line, give the new date [X], and propose one concrete step. Apologise exactly once. Under 100 words.
4.2 Wrong information sentDraft a two-paragraph correction email to [recipient list] on the previous message about [topic]. Lead with the corrected fact in bold, explain what changed in one line, and thank them for reading again. No self-flagellation. Under 90 words.
4.3 Delayed responseReply to [name] whose email I did not answer for [X days]. Three sentences: brief acknowledgment (no long excuse), the answer they actually asked for, and one next step. Warm, not grovelling. Under 70 words.
4.4 Team member's mistakeYou are the manager. Draft a reply to [client] about [issue caused by team member]. Own it as "we," not "they." One sentence of accountability, one line of the fix in flight, one line of what changes so it does not recur. Do not throw the team member under the bus.
4.5 Product outageDraft a status email to affected users about the [service] outage from [start] to [end]. Structure: what happened in one line, who was affected in one line, what we are doing about it in three bullets, when the post-mortem lands. Plain language, no marketing softening.
4.6 Billing errorReply to [customer] about the incorrect charge of [amount] on [date]. One sentence of ownership, one sentence confirming the refund is issued (or in flight — use the fact I give you), and one line about the specific control we added. No blame on "the system."
Nobody reads internal email in full — they scan for what changed, who owns what, and what is on fire. Every prompt below forces the model into a shape a reader absorbs at a glance.
Six internal update prompts
5.1 Weekly statusDraft a weekly status email for [project / team]. Three sections with headings: Shipped this week, In flight, Blocked / help needed. Bullets only, three items max per section, one line each. No preamble. Under 200 words total.
5.2 Project blocked / escalationYou are the project owner. Draft an escalation to [exec] about [project] being blocked by [dependency]. One-paragraph plain-English summary, a table of impact by date, and the specific decision I need from them. Under 150 words.
5.3 New hire announcementDraft a three-paragraph welcome email introducing [new hire, role, start date] to the [team]. Include one genuine detail I give you about their background, what they will own in the first 30 days, and a light closing line. No "thrilled to announce."
5.4 Change in scope / pivotDraft an email to [team] announcing a scope change on [project]: what we were doing, what we are doing instead, why (in one line), what changes for owners, and what does not. Direct, honest, under 180 words.
5.5 Meeting cancellationDraft a two-sentence email cancelling the [meeting] on [date]. Explain the reason in half a line, say what is happening async instead (or when it will be rescheduled), and paste the doc / thread link I give you. No apologies for reclaiming time.
5.6 Post-mortem summaryDraft a post-mortem summary email for [incident]. Structure: one-line what happened, timeline as a small table (time / event), impact in numbers I supply, three action items with owners and dates. Blameless language throughout. Under 250 words.
Discovery emails move the deal without leaning on the model to invent details. Every prompt below assumes you supply the real pain point, the real number, and the real next step. Feed the model those and it holds the tone; skip them and it imagines them.
Six sales discovery prompts
6.1 Book a discovery call (warm lead)You are an AE. Draft a three-sentence email to [name] proposing a 20-minute discovery call. Reference the specific inbound they filled out (paste below), name the two questions the call will answer, and offer three time windows in [their timezone]. No filler.
6.2 Discovery follow-up with agendaDraft a pre-call email to [name] for our discovery on [date]. Recap in one line what I understand about their situation from the paste, list four bulleted questions we will cover, and confirm the meeting link. Under 120 words.
6.3 Send pricing after a callDraft a pricing email to [name] after our call. Recap the two constraints they told me (paste), present the [tier] that fits with the price [X] and what it includes, note what changes at the next tier, and end with a specific next step. No hard sell.
6.4 Send proposal with recapDraft a proposal email covering the doc attached. Structure: one-line problem in their words, three-line solution, the number and terms, the timeline, and one specific decision I am asking for. Under 200 words. Do not restate the doc — this is the wrapper.
6.5 Nudge a stalled dealDraft a two-paragraph email to [name] on a deal that has stalled for [X weeks] after [last activity]. Warm, no guilt. Reference the paste, name what has changed on our side (I will fill in), and offer one lightweight next step. Under 100 words.
6.6 Ask for a referral post-closeDraft a four-sentence email to [customer] one month after close, asking for a referral. Reference the specific outcome they got (paste the number), name the type of team we are looking to help, and make the ask concrete — one intro to one person. Warm, brief.
Calendar email is the easiest to over-write and the easiest to fix with a length cap. Most of these are one to three sentences on purpose. If a scheduling email needs more than that, something else is going on and a separate message handles it better.
Seven meeting and scheduling prompts
7.1 Propose three times across time zonesDraft a two-sentence email to [name] proposing three 30-minute windows in the next week that work in both [my timezone] and [their timezone]. Show times in both. Offer to send a calendar link if none work.
7.2 Reschedule with warmthDraft a two-sentence email asking [name] to reschedule our [date] meeting due to [real reason]. Propose two specific alternate times, apologise once, and thank them for the flexibility. No long explanation.
7.3 Cancel with an async alternativeDraft a three-sentence email cancelling the [meeting] on [date] and moving the discussion to async. Say why in one line, name the doc / thread where the conversation will continue, and give a deadline for input.
7.4 Meeting agenda ahead of the callDraft a pre-meeting email for [meeting name] on [date]. Include a three-line context recap, a bulleted agenda with time allocations (total = 30 min), the two decisions we need to reach, and the docs to skim beforehand. Under 150 words.
7.5 Meeting recap and action itemsFrom the notes below, draft a recap email: one-paragraph summary, table of decisions (decision / owner), table of action items (item / owner / date), and one "reply if I have missed anything." Use only what is in the notes.
7.6 Decline a recurring meetingDraft a three-sentence email to [organiser] dropping off the [recurring meeting]. Explain in one line what changed on my side, offer an async replacement (a weekly note or a Slack update), and thank them.
7.7 Ask to shorten a meetingDraft a one-sentence reply to [name] asking to shorten our [meeting] from [current length] to [shorter length]. Give the real reason and confirm the new time on the calendar. No apologies for being efficient.
Support email carries the most risk of a fabricated fact reaching a paying customer. Every prompt hard-codes the anti-hallucination rule: if the model lacks a real order number, refund date, or workaround, it leaves a bracketed placeholder that a human fills in before sending.
Seven customer support prompts
8.1 Angry customer, real error on our sideYou are a senior CX rep. Reply to [name] who is (rightly) upset about [issue]. Own it in one sentence, state the fix as a fact (paste the fact I give you), give the exact date the fix lands, and offer one concrete gesture. Apologise once. Invent nothing.
8.2 Angry customer, misunderstanding on their sideReply warmly to [name] whose complaint below is based on a misreading of [policy / feature]. Acknowledge the frustration, correct the misunderstanding with the actual policy (I will paste it), and offer to hop on a five-minute call. No condescension.
8.3 Refund yesDraft a three-sentence refund confirmation to [name] for the order / charge of [amount] on [date]. State that the refund is issued and when it should appear, invite them back with one specific offer, and thank them. No upsell.
8.4 Refund noReply to [name] declining a refund request, based on [specific policy line I paste]. Two paragraphs: acknowledge the situation with empathy, quote the relevant policy in one line, offer the one alternative available (credit, extended trial). Warm, clear, under 120 words.
8.5 Bug workaround while the fix shipsReply to [name] about the [bug] they reported. Confirm we have reproduced it, describe the workaround in three numbered steps I will paste, and give a realistic ETA for the fix (use [placeholder] if I have not given one). Under 130 words.
8.6 Feature request "not on roadmap"Draft a four-sentence reply to [name] whose feature request is not planned. Genuine thanks, honest "not on the roadmap right now," one line about the closest thing we do support, and an invitation to add their vote to the tracker. No fake hope.
8.7 Escalation acknowledgmentReply to [name] whose case has been escalated to [team]. One sentence: what has happened, who owns it now (name and role I will paste), and when they will hear back. No jargon. Under 50 words.
Copy the prompts you use most into whatever surface you already open in a hurry — a note, a Notion page, a text-expander snippet. Six prompts you can trigger with two keystrokes beat a bookmarked list you never open.
Three things upgrade output more than any rewording. First, paste the real thread — the actual words the other person used, not a summary. Second, add a one-block "voice sample" — two or three of your own real emails plus "match this sentence length and sign-off" — and drop the same block into every prompt. Third, keep the anti-hallucination line: "If any fact is missing, use a bracketed placeholder instead of inventing."
The best place to use every prompt in this library is AI Emaily — an AI-native email client where the AI already has the thread you are on, your voice is set once through a user-controlled Personal Context brain, and there is no tab-switch or paste-back step at all. That is the library's actual answer: not a better prompt, but an inbox where the prompt is mostly already handled. Start with a 7-day free trial at /pricing. If ChatGPT and Claude are already your daily tools, their Custom Instructions and Projects features do hold a voice profile across sessions better than a static text file will — that is a real edge for pure prompt iteration. But where AI Emaily wins is the step you do not see in any chatbot: the thread is already there.
One rule to keep in every prompt
"Only use facts I have given you. If something is missing — a name, a date, a number, a policy — use a [bracketed placeholder] instead of inventing." This is the difference between a draft you edit and a message that reaches a customer with a made-up refund date attached.
Real email is messy. A stalled-deal reply is a follow-up and a sales-discovery nudge; a missed-deadline note to a client is an apology and a status update. Pick the prompt whose primary job matches the outcome you need, then borrow one constraint from the other. If the outcome is "keep the deal alive," that is discovery; if it is "repair a broken commitment," that is apology.
The other trap is doing too much in one email. If a message has to acknowledge a delay, deliver a new date, upsell a retainer, and ask for a referral, you have four emails, not one. Write them in sequence rather than cramming them into a single prompt — one email, one job.
Where a prompt library stops helping — even a good one#
Fifty prompts in a place you can reach is a real upgrade over typing "write a follow-up" every morning. But every prompt above still asks you to do the same chores each time: switch tabs to the AI tool, paste the thread in, paste your voice samples in, read the draft, copy it back, and fix the formatting that broke in transit. The prompts brief the AI well; they do nothing about the tax of operating it.
AI Emaily is the AI-native email client built specifically to remove that tax. The AI lives inside your inbox and already has the thread you are on — the "paste your thread" instruction that appears in every prompt above simply does not apply. Voice is set once through a user-controlled Personal Context brain and per-client profiles, not learned from your sent mail, so the "match this voice" block never needs to be re-pasted. Drafts appear in the reply, in your voice, grounded in the real conversation. Copilot holds every send for your approval before anything goes out; undo and audit apply to everything; there is no training on your mail. Start a 7-day free trial on Pro or Autopilot at /pricing (card required, cancel by day seven for no charge). See how drafting works at /features/ai-drafting.
Honest scope: if your primary need is iterating on prompt wording and you already live in a chatbot all day, ChatGPT Custom Instructions and Claude Projects do hold a voice profile and system prompt across sessions more cleanly than any inbox-side tool. Where AI Emaily wins is not prompt-tuning; it is that a good prompt library still ends with you doing the paste, and AI Emaily is the place where that step is gone.
The prompt is the symptom, the paste is the disease
Every good prompt in this library is a workaround for information the AI should already have — your voice, the thread, your relationship with the sender. A library polishes the workaround. An AI-native inbox removes the need for it.
Nafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.
EntrepreneurAI Automation System BuilderAI EnthusiastBuilds AI Enterprise Solutions10+ years experience
Every prompt above ends with "paste your thread." AI Emaily is the AI-native email client that already has it — drafts reply in your voice, grounded in the real conversation, approve-before-send by default. 7-day free trial on Pro, card required, cancel by day seven. Start at app.aiemaily.com/signup.
