AI Email Prompt Templates: 18 Copy-Paste Prompts for Every Email You'll Ever Write

Write a meeting request email.

To: [name and their role, e.g., "Sarah Chen, VP of Engineering"]
My relationship with them: [boss / peer / someone I've never met / client / vendor]
Meeting purpose: [be specific — not "catch up" but "align on the Q2 roadmap priorities before Friday's planning session"]
Urgency: [need it this week / flexible / ASAP]
Preferred time: [suggest 2-3 specific time slots, or say "I'm flexible"]
Duration: [15 min / 30 min / 1 hour]
Format: [in-person / video call / phone]
What I need from them beforehand: [anything they should review or prepare, or "nothing"]

Context that matters:
- [e.g., "We discussed this briefly at last week's standup and she said to book time"]
- [e.g., "This follows up on an issue that came up in the product review"]

Tone: [casual because we're peers / professional because it's leadership / warm because it's a client]

Keep it under 100 words. Nobody reads long meeting requests. Subject line should say what it's about, not "Quick meeting request."

Write a project status update email.

To: [stakeholders — who needs this update]
Project: [project name]
My role: [what I do on this project]

Current status:
- Overall: [on track / slightly behind / at risk / ahead of schedule]
- Completed since last update: [list 2-4 things done]
- In progress: [list 2-3 things actively being worked on]
- Blocked/at risk: [list any blockers, or "none"]

Key metrics (if applicable):
- [e.g., "Sprint velocity: 34 points (target: 30)"]
- [e.g., "Budget spent: $45K of $80K"]
- [e.g., "Timeline: 2 days behind on the API integration"]

Decisions needed: [anything you need the reader to decide or approve, or "none — FYI only"]
Next milestone: [what's coming next and when]

Tone: [matter-of-fact / proactive and confident / flag concerns clearly]

Format as scannable — use bullet points and bold key items. The reader should get the full picture in under 30 seconds. Put the most important thing in the first sentence, not buried in paragraph three.

Write an escalation email. Something isn't getting resolved at my level and I need help from someone higher up.

To: [who I'm escalating to — their name and role]
CC: [anyone who should see this, or "no one"]
The issue: [what's going wrong — specific, factual, no drama]
Impact: [what happens if this doesn't get resolved — concrete consequences, timelines, dollars if possible]

Timeline so far:
1. [Date]: [What happened / what I tried]
2. [Date]: [Next step I took]
3. [Date]: [Current state]

What I've already tried to resolve it:
- [Attempt 1 and result]
- [Attempt 2 and result]

What I need: [specific ask — approval, intervention, decision, resources]
Deadline: [when this needs to be resolved by, and why]

Tone: professional and factual, not emotional. I'm not complaining — I'm making sure the right person has the information to act. No blame language. Focus on the problem and the path forward, not who's at fault.

Keep it under 200 words. Attach supporting detail if needed, but the email body should stand on its own.

Write an email delegating a task or responsibility to someone.

To: [name and role]
Our relationship: [direct report / peer / cross-functional colleague]
Task: [what I need them to do — be specific]
Why them: [why this person specifically — skill match, availability, development opportunity]
Context: [background info they need to do this well]

Details:
- Deadline: [date and time]
- Expected deliverable: [what "done" looks like — a document? A decision? A completed process?]
- Quality standard: [e.g., "client-ready" vs "rough draft for internal review"]
- Resources available: [links, files, people they can ask]
- Authority level: [can they make decisions, or do they need to check with me?]

My availability: [when they can reach me with questions]

Tone: [empowering for a junior ("I'm trusting you with this because...") / collaborative for a peer ("would really appreciate your help on this") / direct for a routine handoff]

Don't micromanage. Give them the what and the why, then trust them with the how.

Write a cold outreach email that someone would actually respond to.

To: [title/role of the recipient, e.g., "Head of Growth at a Series B fintech startup"]
My product/service: [what I sell]
The problem I solve for them: [specific pain point, not "we help companies grow"]
My proof: [one compelling data point, case study, or credibility signal]
The ask: [what I want — reply, 15-min call, try a free demo]

Their world:
- They probably get [X] cold emails per day
- They care about: [their priorities and pressures]
- They've probably tried: [competitor solutions or DIY approaches]
- What would make them reply: [genuine value, not just curiosity]

Rules:
- Subject line: 4-7 words, no clickbait, sounds like a human sent it
- Opening line: Reference something specific about them or their company (not "I came across your profile")
- No "I hope this finds you well"
- No "My name is X and I'm from Y" (save it for the signature)
- Get to the point in the first 2 sentences
- Total length: under 80 words (shorter = higher reply rate)
- CTA: one question, low commitment

Write 3 versions:
A) Lead with their pain point
B) Lead with a relevant result
C) Lead with a provocative question

Plus: a follow-up email for 3 days later (under 40 words, different angle, adds one new piece of value).

Write a follow-up email. I reached out but they didn't reply.

Context:
- Who I emailed: [name and role]
- My original email topic: [what I asked about / offered]
- When I sent it: [X days ago]
- Any previous relationship: [warm intro / cold / met at event / previous customer]
- How many follow-ups I've already sent: [0 / 1 / 2 — don't send more than 3 total]

Write a follow-up that:
- Does NOT start with "just following up" or "just checking in" (these are the most ignored openers)
- Adds new value (different angle, new data point, relevant article, fresh insight)
- Acknowledges they're busy without being passive-aggressive
- Is shorter than the original email
- Has a clear but low-pressure CTA
- Makes it easy to say "not interested" (paradoxically, this gets more replies)

Length: under 60 words. If the first email was long, this one should be punchy.

Write a proposal email summarizing what I'm offering and why they should say yes.

Client: [name and company]
Project/offer: [what I'm proposing]
Their need: [the problem we discussed, or the goal they mentioned]
Proposed solution: [high-level approach — 2-3 sentences]
Investment: [$amount or range, or "pricing attached separately"]
Timeline: [when it starts, how long it takes, key milestones]
Why us: [2-3 specific reasons — not generic "years of experience" but "we did this exact thing for Company X and the result was Y"]

Previous conversations: [what was discussed, any concerns they raised]

Structure:
1. Opening: Reference our conversation and restate their goal (show I listened)
2. Summary: What I'm proposing, in plain language
3. Approach: 3-4 key steps or phases (keep it high-level — details in attached doc if needed)
4. Investment: Clear pricing with what's included
5. Timeline: When they can expect what
6. Why now: Reason to move forward sooner rather than later (without fake urgency)
7. Next step: One clear action ("Reply to confirm, and I'll send the statement of work by Thursday")

Attach the detailed proposal if available, but this email should make the case on its own. Keep under 300 words — they'll read the attachment for details.

A prospect raised an objection. Write a reply that addresses it without being pushy.

Their objection: "[Paste what they said — e.g., 'the price is too high' or 'we're already using Competitor X' or 'not the right time']"
My product/service: [what I sell]
Their situation: [what I know about them, their company, their needs]
My honest assessment: [is their objection valid? partially valid? based on a misconception?]

Write a reply that:
1. Acknowledges their concern genuinely (not "I totally understand, BUT...")
2. Asks a clarifying question if the objection is vague
3. Addresses the specific objection with evidence, not rhetoric:
   - Price: frame as ROI or compare to cost of doing nothing
   - Competitor: differentiate on specific capability, not general "we're better"
   - Timing: reduce commitment ("what if we started with a pilot?")
   - Need: explore whether the need exists but isn't recognized yet
4. Ends with a question that keeps the conversation open (not a CTA to buy)

Tone: confident and helpful, not desperate. If they're not a fit, that's OK — say so. Trying to convince a bad-fit prospect wastes everyone's time.

Length: under 150 words. Objection responses should be focused, not a second pitch.

Write a reply to a customer complaint.

The complaint: "[Paste their email or summarize what they said]"
What actually happened: [the facts — was it our mistake, a misunderstanding, or a product limitation?]
What I can do to fix it: [refund / replacement / credit / escalation / explanation]
Company policy on this: [any relevant policies — return window, SLA, guarantee]
Customer history: [new customer / long-term / VIP / frequent complainer]

Reply guidelines:
1. Acknowledge their frustration first — before explaining anything. People need to feel heard.
2. Apologize if we're at fault. Be specific ("I'm sorry the shipment arrived damaged" not "I'm sorry you feel that way").
3. If it's NOT our fault, explain clearly without being defensive.
4. State what I'm doing to fix it — concrete action, not vague promises.
5. Give a timeline: when will they see the resolution?
6. Offer something extra if appropriate (not a bribe — a genuine goodwill gesture).
7. End with direct contact info for follow-up.

Tone: empathetic, professional, and solutions-focused. Never dismissive. Never combative. Even if the customer is being unreasonable, the email should read like I care about their experience.

Write a reply to a customer requesting a refund or cancellation.

Their request: "[What they asked for — full refund, partial refund, cancel subscription]"
Reason they gave: [why they want the refund/cancellation, or "no reason given"]
Are they eligible? [yes per policy / no — explain why / edge case — manager discretion]
What I'm offering: [full refund / partial refund / credit / alternative solution / denial with explanation]
Processing time: [how long the refund takes]
Customer history: [context — how long they've been a customer, total spend, previous issues]

Reply structure:
1. Thank them for reaching out (don't make them feel bad for asking)
2. Confirm what I'm doing: approve refund, process cancellation, or explain the alternative
3. If approving: clear next steps and timeline
4. If denying: honest explanation of why, with empathy, and offer the next-best alternative
5. If I can save the customer: offer a genuine reason to stay (not a guilt trip — maybe a discount, pause option, or feature they haven't tried)
6. Exit gracefully: if they're leaving, wish them well and leave the door open

Never make a customer fight for a refund they're entitled to. And never use the word "unfortunately" more than once.

Write a reply to a customer question about our product or service.

Their question: "[Paste their email or question]"
The answer: [the factual answer to their question]
Related info they might also need: [anything they'll likely ask next]
Link to help docs (if applicable): [URL]

Reply guidelines:
1. Answer their actual question in the first 1-2 sentences. Don't bury the answer after a paragraph of context.
2. If the answer is complex, break it into numbered steps.
3. Add a proactive tip — something they didn't ask about but will find useful.
4. Link to relevant documentation for deeper detail.
5. Offer to help further if the answer doesn't solve their problem.

Tone: helpful and clear. Like a knowledgeable friend, not a support bot. Use the product name, not "our platform" or "the system."

Keep it under 150 words. If it takes more than that to answer, the answer should probably be a help article.

Write an internal announcement email.

What's being announced: [be specific — organizational change, new hire, policy update, product launch, office move, etc.]
Sent from: [my role — CEO / team lead / HR / department head]
Audience: [whole company / specific team / department]
The "so what" for the reader: [how does this affect them personally?]
Effective date: [when does this take effect]
Questions/concerns should go to: [who to contact]

Key details:
- [Detail 1]
- [Detail 2]
- [Detail 3]

Sensitive considerations:
- [e.g., "some people will be worried about job security"]
- [e.g., "this reverses a decision we made 3 months ago"]
- [e.g., "none — this is straightforward good news"]

Tone should match the news:
- Good news (new hire, success, perk): warm, celebratory, but not over-the-top
- Neutral news (policy change, process update): clear, factual, helpful
- Difficult news (layoffs, restructure, setback): honest, empathetic, direct — don't bury the lead

Open with the news. Not with three paragraphs of context that make people nervous about what's coming.

Write an email asking someone for feedback on my work.

To: [name and role — boss / peer / cross-functional stakeholder / client]
What I need feedback on: [a document, presentation, project plan, design, code, proposal — be specific]
Attached/linked: [the thing they're reviewing]
Deadline for feedback: [when I need it by, and why]

Specific areas I want feedback on:
1. [e.g., "Is the executive summary clear enough for a non-technical audience?"]
2. [e.g., "Does the timeline seem realistic?"]
3. [e.g., "Am I missing any edge cases?"]

Context they need:
- [e.g., "This is going to the board next Tuesday"]
- [e.g., "I've already incorporated feedback from [other person]"]
- [e.g., "This is a first draft — I know sections 4-5 need work"]

Tone: collaborative, not needy. I'm not asking for permission — I'm asking for a perspective I don't have.

Make it easy for them: tell them exactly what to look at, what questions to answer, and how long it should take them. "Can you take a look at this?" with no direction = feedback that's either useless or never comes.

Write my weekly/monthly status report email.

To: [manager / team / stakeholders]
Reporting period: [dates]

Accomplishments:
- [What I completed — with outcomes, not just activities]
- [e.g., "Shipped the onboarding redesign — early data shows 15% improvement in activation rate"]
- [e.g., "Closed the deal with [client] — $45K ARR"]

In progress:
- [What I'm working on and where it stands]
- [Expected completion date]
- [Any dependencies or blockers]

Blockers / Need help with:
- [What's slowing me down — be specific about what you need from whom]
- [Or "None — everything on track"]

Priorities for next period:
- [Top 3 things I'll focus on]

Wins worth noting: [anything that deserves visibility — team collaboration, customer feedback, learning]
Learnings: [anything that changed my approach or understanding]

Format: scannable bullets, not paragraphs. Bold the most important items. My manager should be able to read this in 2 minutes and know exactly where things stand.

Write an email delivering bad news to [recipient].

The bad news: [what happened — be specific]
Who I'm telling: [their role and my relationship with them]
Their likely reaction: [how they'll probably feel — disappointed, angry, worried, confused]
Why it happened: [honest explanation — not excuses]
What I'm doing about it: [concrete next steps to address or mitigate the situation]
What I need from them: [understanding? A decision? Nothing — just informing?]

Important context:
- [e.g., "They were counting on this for their Q2 targets"]
- [e.g., "I promised this would be done by Monday"]
- [e.g., "This affects their team too, not just mine"]

Writing rules:
1. Lead with the news. Don't make them read 3 paragraphs before getting to the point.
2. Take responsibility if it's warranted. No passive voice deflection ("mistakes were made" → "I underestimated the timeline").
3. Show you understand the impact on THEM, not just on you.
4. Present the recovery plan — they want to know what happens now, not just what went wrong.
5. Don't over-apologize. One clear apology is stronger than five "I'm so sorry" sentences.

Tone: direct, accountable, and forward-looking. Not groveling, not defensive.

Write an email to address a conflict or disagreement with a colleague.

The situation: [describe what happened — the disagreement, the miscommunication, the friction]
My role in it: [how I contributed to the problem — be honest]
Their perspective: [how they probably see this situation]
What I want the outcome to be: [resolution, not victory — what does "resolved" look like?]
Our working relationship: [peer / they report to me / they're senior to me / cross-functional]

Write an email that:
1. Opens by naming the issue directly but neutrally — facts, not blame
2. Acknowledges their perspective ("I can see why you felt..." or "Your concern about X is valid")
3. Takes ownership of my part without being a doormat
4. Proposes a path forward — specific, actionable, fair
5. Invites their input ("I'd like to hear your thoughts" — and mean it)
6. Suggests talking in person if the email isn't sufficient

Tone: adult-to-adult. Not passive-aggressive ("as I mentioned previously..."). Not apologetic-aggressive ("I'm sorry but..."). Just honest and constructive.

This email should make them want to work it out, not prepare their defense.

Write an email making a case for a salary increase or promotion.

My role: [current title]
Time in role: [how long]
Who I'm writing to: [my manager's name and title]
Current salary: [amount, or "I'd rather not state it in the email"]
Target: [what I'm asking for — specific number, percentage increase, or "open to discussion"]

My case:
- Key accomplishments: [3-5 specific results with numbers where possible]
  1. [e.g., "Led the migration project that reduced infrastructure costs by $120K/year"]
  2. [e.g., "Grew the team from 3 to 7 and maintained below-average attrition"]
  3. [e.g., "Shipped 4 major features that drove 22% increase in paid conversions"]
- Scope increase: [ways my role has expanded beyond the original job description]
- Market data: [any salary benchmarks I've researched — Glassdoor, Levels.fyi, industry reports]
- Feedback I've received: [positive performance reviews, stakeholder feedback, awards]

Tone: confident and professional. I'm making a business case, not asking for a favor. No "I feel like I deserve..." — frame it as "here's the value I've delivered and here's what's competitive for this level of work."

End with a clear ask and suggestion for a meeting to discuss in person. Keep the email under 250 words — save the detailed case for the conversation.

Write a professional apology email.

What I need to apologize for: [be specific — missed deadline, mistake in a deliverable, dropped the ball on a commitment, unprofessional behavior]
To whom: [name, role, and relationship]
What actually happened: [the facts — no minimizing]
The impact on them: [how my mistake affected their work, timeline, reputation, or trust]
What I've done to fix it: [concrete actions taken, not just "I'll do better"]
What I'll do to prevent it from happening again: [systemic fix, not just willpower]

Write an apology that:
1. Leads with a clear, direct apology — no "I'm sorry IF you felt..." (that's not an apology)
2. Names specifically what I did wrong (shows I actually understand)
3. Acknowledges the impact on them — not just how I feel about it
4. Explains what happened briefly (context, not excuse)
5. States what I've done to fix the immediate problem
6. States what I'm changing to prevent repetition
7. Doesn't ask for forgiveness — that's their decision, not my request

Keep it under 200 words. Long apology emails feel like they're trying to be absolved. Short ones feel sincere.

Tone: genuine, accountable, concise. This email should rebuild trust, not beg for it.