What is in this pack
AI prompts for email writing are pre-built instructions that help individuals and teams draft professional emails faster and more consistently. This page is for team leads, managers, and professionals who write a lot of email and want repeatable results across ChatGPT, Claude, Copilot, and Gemini.
This pack covers five categories: cold outreach, follow-ups, internal updates, customer-facing responses, and difficult conversations. You get 20+ prompts, each with clear variables so you can drop in your own context, plus notes on what to adjust first.
One honest caveat up front: AI drafts work best as a starting point, not a finished product. For sensitive situations, like delivering bad news or responding to a frustrated customer, the model output will almost always need a human pass before you send it. If you are writing something high-stakes, this pack will save you time on structure and tone, but not on judgment.
Published: 2025-07-14. Last updated: 2025-07-14.
The prompts, by category
These prompts are grouped by the job they do. Each one works in ChatGPT, Claude, Copilot, and Gemini with no modification. Variables appear in [BRACKETS]; swap them before you send.
Category 1: Outreach and cold email
Write a cold outreach email from a one-sentence pitch
When to use it: First contact with a prospect, partner, or press contact who has never heard of you. Change first: [VALUE PROPOSITION] and [RECIPIENT ROLE]. Generic value propositions produce generic emails.
Variables: [SENDER NAME], [SENDER ROLE], [COMPANY], [RECIPIENT ROLE], [VALUE PROPOSITION], [CALL TO ACTION]
Write a short cold outreach email from [SENDER NAME], [SENDER ROLE] at [COMPANY], to a [RECIPIENT ROLE].
The single value proposition is: [VALUE PROPOSITION].
Rules:
- Subject line included
- Under 120 words in the body
- One call to action: [CALL TO ACTION]
- No superlatives, no "I hope this email finds you well"
- Plain, direct tone[NEEDS REAL OUTPUT] What to notice:, ---
Follow up on an unanswered outreach email
When to use it: Three to seven days after a cold email that got no reply. Change first: [ORIGINAL HOOK], so the follow-up references something specific rather than just saying "following up."
Variables: [ORIGINAL EMAIL SUMMARY], [ORIGINAL HOOK], [DAYS SINCE SENT], [ONE NEW DETAIL OR REASON]
Write a follow-up email for an outreach message sent [DAYS SINCE SENT] days ago that received no reply.
Original message summary: [ORIGINAL EMAIL SUMMARY]
Original hook: [ORIGINAL HOOK]
New detail or reason to respond: [ONE NEW DETAIL OR REASON]
Rules:
- Under 80 words
- Acknowledge the silence briefly, do not apologize for following up
- End with a low-friction ask (a yes/no question or a single link)Write an outreach email using a mutual connection
When to use it: When a colleague or contact has agreed to be named as a reference point. Change first: [MUTUAL CONNECTION NAME] and [CONNECTION CONTEXT], because vague name-drops backfire.
Variables: [SENDER NAME], [MUTUAL CONNECTION NAME], [CONNECTION CONTEXT], [ASK OR GOAL]
Write a warm outreach email that opens by referencing [MUTUAL CONNECTION NAME] and the context of that connection: [CONNECTION CONTEXT].
The goal of the email is: [ASK OR GOAL]
Rules:
- Subject line included
- Reference the mutual connection in the first sentence, then move on
- Under 150 words
- Do not overuse the mutual connection's nameCategory 2: Internal communication
Summarize a long email thread for a late-arriving stakeholder
When to use it: Before a meeting, or when someone joins a project after several email exchanges have already happened. Change first: Paste the actual thread text in place of [THREAD TEXT].
Variables: [THREAD TEXT], [READER ROLE], [KEY DECISION NEEDED]
Summarize the email thread below for a [READER ROLE] who is joining the conversation late.
Thread:
[THREAD TEXT]
Output format:
- What has been decided (bullet list)
- What is still open (bullet list)
- The one decision or action [READER ROLE] needs to weigh in on: [KEY DECISION NEEDED]
Keep the total summary under 150 words.[NEEDS REAL OUTPUT] What to notice:, ---
Write a project status update email
When to use it: Weekly or milestone-based updates to a manager or cross-functional group. Change first: [STATUS] (on track / at risk / delayed) and [NEXT MILESTONE DATE].
Variables: [PROJECT NAME], [STATUS], [COMPLETED THIS PERIOD], [BLOCKERS], [NEXT MILESTONE], [NEXT MILESTONE DATE], [ASKS FROM RECIPIENTS]
Write a project status update email for [PROJECT NAME].
Status: [STATUS]
Completed this period: [COMPLETED THIS PERIOD]
Current blockers: [BLOCKERS]
Next milestone: [NEXT MILESTONE] by [NEXT MILESTONE DATE]
Asks from recipients: [ASKS FROM RECIPIENTS]
Rules:
- Subject line in format: [Project Name] Update | [Date] | [Status]
- Scannable: use short paragraphs or bullets
- Lead with status, not with context
- Under 200 wordsEscalate an issue without sounding reactive
When to use it: When a problem needs senior attention but you do not want to appear panicked or to assign blame prematurely. Change first: [IMPACT] first. The seriousness of the tone should match the actual business impact, not the level of your frustration.
Variables: [ISSUE DESCRIPTION], [IMPACT], [STEPS ALREADY TAKEN], [WHAT YOU NEED FROM RECIPIENT], [DEADLINE FOR RESPONSE]
Write an escalation email about the following issue: [ISSUE DESCRIPTION]
Business impact: [IMPACT]
Steps already taken: [STEPS ALREADY TAKEN]
Ask: [WHAT YOU NEED FROM RECIPIENT]
Response needed by: [DEADLINE FOR RESPONSE]
Rules:
- Factual tone, no blame language
- Open with the issue and impact, not with background
- Close with the specific ask and the deadline
- Under 180 wordsDecline a request professionally
When to use it: Saying no to a colleague's ask without damaging the working relationship. Change first: [REASON FOR DECLINE]. Vague declines feel dismissive; one honest reason reads better.
Variables: [REQUEST DESCRIPTION], [REASON FOR DECLINE], [ALTERNATIVE IF ANY]
Write a professional email declining the following request: [REQUEST DESCRIPTION]
Reason for declining: [REASON FOR DECLINE]
Alternative to offer (leave blank if none): [ALTERNATIVE IF ANY]
Rules:
- Acknowledge the request before declining
- One sentence on the reason, not a paragraph
- If an alternative exists, offer it briefly
- Under 120 words
- Do not use "unfortunately" as the first wordCategory 3: Customer and client communication
Respond to a customer complaint
When to use it: Any time a complaint arrives by email, whether through a support inbox or directly to a team member. Change first: [ROOT CAUSE] and [RESOLUTION OFFERED]. If either is missing, the model will hedge and the email will sound evasive.
Variables: [CUSTOMER NAME], [COMPLAINT SUMMARY], [ROOT CAUSE], [RESOLUTION OFFERED], [NEXT STEP AND TIMELINE]
Write a response to the following customer complaint on behalf of our team.
Customer name: [CUSTOMER NAME]
Complaint: [COMPLAINT SUMMARY]
Root cause: [ROOT CAUSE]
Resolution: [RESOLUTION OFFERED]
Next step and timeline: [NEXT STEP AND TIMELINE]
Rules:
- Open by acknowledging the customer's experience, not by apologizing for "any inconvenience"
- State the resolution clearly in one sentence
- Close with the concrete next step and who owns it
- Under 200 words
- Warm but not sycophantic[NEEDS REAL OUTPUT] What to notice:, ---
Send a proactive delay or issue notification
When to use it: Before a customer notices a problem themselves. Getting ahead of an issue is almost always better than reacting. Change first: [EXPECTED RESOLUTION DATE]. Do not use this prompt if you do not have a realistic estimate; vague timelines erode trust faster than the original problem.
Variables: [CUSTOMER NAME OR SEGMENT], [ISSUE DESCRIPTION], [IMPACT ON CUSTOMER], [CAUSE IF KNOWN], [EXPECTED RESOLUTION DATE], [INTERIM WORKAROUND IF ANY]
Write a proactive notification email about a service issue or delay.
Recipient: [CUSTOMER NAME OR SEGMENT]
Issue: [ISSUE DESCRIPTION]
Impact on customer: [IMPACT ON CUSTOMER]
Cause (if known): [CAUSE IF KNOWN]
Expected resolution: [EXPECTED RESOLUTION DATE]
Interim workaround: [INTERIM WORKAROUND IF ANY]
Rules:
- Lead with what happened and what it means for the customer
- Do not lead with an apology, but include one
- Plain language, no jargon
- Under 180 wordsRequest a testimonial or case study from a happy customer
When to use it: Shortly after a successful delivery, renewal, or milestone where the customer has expressed satisfaction. Change first: [SPECIFIC OUTCOME] to reference something real. Generic testimonial requests get ignored.
Variables: [CUSTOMER NAME], [SPECIFIC OUTCOME], [FORMAT REQUESTED], [EFFORT REQUIRED], [YOUR NAME AND ROLE]
Write a testimonial request email to [CUSTOMER NAME].
Specific outcome to reference: [SPECIFIC OUTCOME]
Format being requested: [FORMAT REQUESTED] (e.g., two-sentence quote, 15-minute call, written case study)
Effort required from the customer: [EFFORT REQUIRED]
Sent by: [YOUR NAME AND ROLE]
Rules:
- Open by referencing the specific outcome
- Make the ask explicit and low-friction
- Explain briefly what the format involves
- Under 150 words
- No guilt, no pressure languageWrite a renewal or re-engagement email
When to use it: For customers approaching contract renewal, or contacts who have gone quiet. Change first: [REASON TO STAY OR RETURN]. If you do not have a genuine one, this email will not work regardless of how well it is written.
Variables: [CUSTOMER NAME], [PRODUCT OR SERVICE], [RENEWAL DATE OR INACTIVITY PERIOD], [REASON TO STAY OR RETURN], [NEXT STEP]
Write a renewal or re-engagement email for [CUSTOMER NAME] regarding [PRODUCT OR SERVICE].
Context: [RENEWAL DATE OR INACTIVITY PERIOD]
Reason to stay or return: [REASON TO STAY OR RETURN]
Next step: [NEXT STEP]
Rules:
- Do not open with "I noticed you haven't..."
- Reference something specific about their use or history if possible
- One clear call to action
- Under 160 wordsCategory 4: Scheduling and logistics
Request a meeting with someone you do not know well
When to use it: Asking for time from someone outside your organization or from a senior person internally. Change first: [AGENDA ITEMS], because people agree to meetings when they know exactly what will be covered.
Variables: [YOUR NAME], [YOUR ROLE], [RECIPIENT NAME], [MEETING PURPOSE], [AGENDA ITEMS], [PROPOSED DURATION], [PROPOSED OPTIONS]
Write a meeting request email from [YOUR NAME], [YOUR ROLE], to [RECIPIENT NAME].
Purpose: [MEETING PURPOSE]
Agenda items: [AGENDA ITEMS]
Proposed duration: [PROPOSED DURATION]
Time options: [PROPOSED OPTIONS]
Rules:
- Subject line included
- State the purpose in the first sentence
- List agenda items as a short bullet list
- Under 130 words
- End with a scheduling link or two to three specific time optionsReschedule a meeting you need to cancel
When to use it: When you must cancel with less notice than you would like. Change first: [REASON] should be honest and brief. Elaborate excuses tend to backfire.
Variables: [ORIGINAL MEETING DATE AND TIME], [RECIPIENT NAME], [REASON], [NEW PROPOSED TIME OR NEXT STEP]
Write a rescheduling email for a meeting originally set for [ORIGINAL MEETING DATE AND TIME] with [RECIPIENT NAME].
Reason for rescheduling: [REASON]
New proposed time or next step: [NEW PROPOSED TIME OR NEXT STEP]
Rules:
- Apologize once, briefly
- Offer a concrete alternative, not just "let me know when you're free"
- Under 100 wordsSend a meeting recap and action items
When to use it: Within a few hours of any meeting where decisions were made or tasks were assigned. Change first: Paste real notes into [RAW NOTES]. The quality of the output depends entirely on the specificity of what you put in.
Variables: [MEETING NAME], [DATE], [ATTENDEES], [RAW NOTES]
Convert the following meeting notes into a professional recap email.
Meeting: [MEETING NAME]
Date: [DATE]
Attendees: [ATTENDEES]
Raw notes: [RAW NOTES]
Output format:
- Summary (two to three sentences)
- Decisions made (bullet list)
- Action items (table: Owner | Task | Due Date)
- Next meeting or next step (one line)[NEEDS REAL OUTPUT] What to notice:, ---
Category 5: Tone and rewrite tasks
Rewrite an email to match a specific tone
When to use it: When a draft exists but the tone is wrong for the recipient or context. Change first: [TARGET TONE]. Be specific ("warmer but still professional" or "more direct, remove hedging language") rather than vague ("better").
Variables: [ORIGINAL EMAIL], [TARGET TONE], [WHAT TO PRESERVE]
Rewrite the following email to match this tone: [TARGET TONE]
Original email:
[ORIGINAL EMAIL]
What to preserve: [WHAT TO PRESERVE]
Rules:
- Keep the core message and factual content intact
- Do not add new information
- Flag any sentence where the tone change required a significant rewordingShorten an email without losing the key ask
When to use it: Any time a draft runs over 200 words and the recipient is senior or time-poor. Change first: [KEY ASK], so the model knows what it cannot cut.
Variables: [ORIGINAL EMAIL], [KEY ASK], [TARGET WORD COUNT]
Shorten the following email to approximately [TARGET WORD COUNT] words.
Original email:
[ORIGINAL EMAIL]
Key ask that must remain: [KEY ASK]
Rules:
- Cut throat-clearing and redundant context first
- Preserve the key ask exactly
- Do not change the sign-off or subject line unless they are unusually long
- Output the shortened version, then a one-line note on what was cut and whyMake a formal email more direct
When to use it: When a draft is technically correct but buries the point under qualifications. Change first: Paste the actual draft rather than describing it.
Variables: [ORIGINAL EMAIL]
Rewrite the following email to be more direct. Remove hedging language, passive voice, and sentences that delay the main point.
Original email:
[ORIGINAL EMAIL]
Rules:
- Move the main point to the first or second sentence if it is not already there
- Keep formal language where the context requires it; do not make it casual
- Flag the three most significant changes you made and explain each brieflyAdapt a template email for a specific recipient
When to use it: When your team uses a standard template but a specific recipient warrants a more tailored message. Change first: [RECIPIENT CONTEXT] and [WHAT MATTERS TO THIS RECIPIENT]. The model cannot personalize without real details.
Variables: [TEMPLATE EMAIL], [RECIPIENT NAME], [RECIPIENT CONTEXT], [WHAT MATTERS TO THIS RECIPIENT]
Adapt the following template email for a specific recipient.
Template:
[TEMPLATE EMAIL]
Recipient name: [RECIPIENT NAME]
Recipient context: [RECIPIENT CONTEXT]
What matters to this recipient: [WHAT MATTERS TO THIS RECIPIENT]
Rules:
- Do not rewrite the structure or core message
- Add one to two personalized sentences at the opening or closing
- Flag every change you made so it can be reviewed before sendingCategory 6: Sensitive situations
Deliver difficult feedback by email
When to use it: When feedback must be delivered in writing, for example after a verbal conversation has not resolved the issue, or for documentation purposes. Change first: [SPECIFIC BEHAVIOR OR OUTCOME]. Vague feedback emails create defensiveness without producing change.
Variables: [RECIPIENT ROLE], [SPECIFIC BEHAVIOR OR OUTCOME], [IMPACT], [EXPECTED STANDARD], [NEXT STEP]
Write a professional feedback email to a [RECIPIENT ROLE].
Specific behavior or outcome: [SPECIFIC BEHAVIOR OR OUTCOME]
Impact of the behavior: [IMPACT]
Expected standard: [EXPECTED STANDARD]
Next step: [NEXT STEP]
## Real example outputs
Five prompts in this pack are marked [NEEDS REAL OUTPUT]. Once those outputs are captured from a live model run, each one will appear here with a "what to notice" line explaining what a good response looks like and where you might push back or iterate.
In the meantime, here is what to watch for across any email prompt you run:
| Signal | Good output | Worth revising |
|---|---|---|
| Tone match | Reads like your voice, not a template | Formal where you'd be casual, or vice versa |
| Length | Fits the ask (short request, short email) | Padding in the middle paragraphs |
| Call to action | One clear ask, placed near the end | Multiple asks, or no ask at all |
| Variables filled | All [BRACKETS] replaced with real content | Any bracket left in the final draft |
:::keypoint heading="Worth pausing on"
A prompt that produces a passable first draft is not the finish line. The revision pass, where you cut the padding and put your voice back in, is where the time saving actually happens.
:::
The prompts that generate the most useful raw material tend to be the ones with more context in the brief, not the short ones. If an output feels generic, the fix is almost always adding a sentence about your audience or the prior conversation before you rerun it.
## How to adapt these for your team
The prompts above work as written, but they'll work better once they reflect your actual context. Here's a practical sequence for rolling them out with a team.
**Start with your signature block and sign-off style.** Paste your standard email footer and preferred closing line into each prompt you plan to reuse. One edit, done once.
**Swap the tone instruction for your brand voice guide.** If your company has a documented tone of voice, replace phrases like "professional but warm" with two or three lines pulled directly from that document. The model will follow it closely.
**Build a shortlist, not a library.** Resist saving every prompt. Pick five or six that cover your most repeated email types, name them clearly, and share only those with your team. A long list gets ignored.
:::keypoint heading="Worth pausing on"
AI drafts save time on structure and opening lines. They do not replace judgment on sensitive messages. Anything involving a complaint, a termination, or a legal matter should still be drafted by a person first, with AI used only to tighten the language afterward.
:::
Once you've settled on a core set, [shared folders in Convergence](/product/shared-folders) let the whole team pull from the same prompts without version drift.
## Save this folder to your workspace
These prompts work best when your whole team is pulling from the same source. If everyone keeps their own copy, versions drift: someone trims a variable, someone else rewrites the tone instruction, and within a month you have five slightly different prompts producing five slightly different results.
:::cta heading="Want your team sending better emails from day one?" href="/product/shared-folders" button="Start free"
Convergence lets you save this entire prompt pack to a shared folder, so every teammate is working from the same version across ChatGPT, Claude, Copilot, and Gemini.
:::
Shared folders solve the version problem. One person owns the prompt, edits it when something stops working, and everyone else sees the update immediately. No Slack messages asking "which version are we on?"
A few things worth doing before you share:
- Rename any prompt whose job title changed since you saved it.
- Strip out variables that only applied to one project.
- Add a short note inside each prompt saying when you last tested it and on which model.
For more prompts organized by role, browse the [full prompt library by role](/prompts) or check out [AI prompts for business teams](/prompts/business).
## Frequently asked questions
### Do ai prompts for email writing work across different AI tools?
Yes. Every prompt in this pack is written to run without modification on ChatGPT, Claude, Copilot, and Gemini. The variables in brackets are the only parts you need to change. Minor output differences between models are normal, mostly in tone and length, but the structure holds.
### How specific do I need to be with context?
More specific inputs produce better outputs. A prompt that includes your recipient's role, the action you want them to take, and any relevant deadline will outperform a generic one every time. The bracketed variables are your checklist for that.
### Will these prompts work for cold outreach?
They will generate a draft, but AI tends to produce outreach that reads like outreach. For cold email especially, you should rewrite the opening line yourself.
### Can I save these prompts for my whole team?
Yes. [Shared folders in Convergence](/product/shared-folders) let you store, version, and distribute prompts to your team so everyone works from the same starting point.
### How often should I update a saved email prompt?
Review prompts when your messaging changes, a campaign ends, or outputs start feeling off. A prompt that worked well three months ago may need a tone adjustment as your product or audience shifts.