AI Prompts for Email Drafting: Professional, Sales, Internal, Client

Published: July 2026 | 8 min read

Email is still the most important business communication tool, and AI can make you dramatically better at it. Not just faster — actually better. The right prompts produce emails that are clear, appropriately toned, and get responses. These prompts cover the most common business email scenarios.

Professional Business Emails

1. Professional Email from Bullet Points

Role: Professional business communicator
Task: Write a professional email from these bullet points.
Sender: [Your name, role]
Recipient: [Name, role, relationship to you]
Bullet points to include: [Paste your raw notes — what you want to say]
Email context: [Why are you writing? what response do you want?]
Requirements:
1. Subject line (descriptive, specific, not clickbait)
2. Greeting (appropriate to relationship)
3. Opening (1 sentence: why you are writing)
4. Body (your points, expanded into clear paragraphs, organized by importance)
5. Call to action (what you want the recipient to do, by when)
6. Closing (professional)
7. Signature block placeholder
Tone: [Professional but not stiff / formal / casual professional / urgent]
Length: [Under 200 words / under 300 words / as needed]
Constraint: No filler phrases ("I hope this finds you well"). Get to the point in sentence one.

2. Difficult Email (Bad News, Pushback, Refusal)

Role: Professional communication specialist
Task: Write a difficult email that maintains the relationship.
Situation: [Describe — declining a request, pushing back on scope, delivering bad news, saying no to a proposal]
Recipient: [Name, role, relationship, their communication style]
Key points to convey: [What needs to be said — be honest about the message]
Requirements:
1. Subject line (clear, not alarming, not vague)
2. Opening (acknowledge their request/perspective first)
3. The message (deliver the news directly, no burying the lede)
4. Rationale (brief, honest, no over-explaining)
5. Alternative/compromise (offer something if possible)
6. Next steps (what happens now, how to move forward)
7. Closing (preserve the relationship — professional, forward-looking)
Tone rules:
- Respectful, not apologetic (unless you genuinely erred)
- Direct, not padded (padding makes bad news worse)
- Empathetic, not sympathetic (understand their position, do not pity)
- Firm on the decision, open on the relationship
Constraint: Under 250 words. The longer a difficult email, the worse it gets.

3. Email Thread Summary

Role: Communication efficiency specialist
Task: Summarize this email thread for a new stakeholder joining the conversation.
Thread: [Paste the email chain — all messages in order]
Output:
1. Subject: Re: [original subject] — Summary
2. Thread Summary (3-5 bullet points: what has been discussed, what is decided, what is open)
3. Key Decisions (what has been agreed so far)
4. Open Questions (what still needs to be answered)
5. Action Items (who is doing what, by when)
6. Next Step (what is the current ask/next action needed)
7. Relevant Attachments (list with descriptions)
Format: A new person should be fully caught up after reading this summary.
Constraint: Under 300 words. No quoting previous emails — synthesize.

Sales & Outreach

4. Cold Outreach Email

Role: Sales communication specialist
Task: Write a cold outreach email to [prospect description].
Product/service: [What you sell, what problem it solves]
Prospect: [Role, industry, company size, likely pain points]
Trigger event: [Why now? What happened that makes this relevant? — be specific]
Requirements:
1. Subject line (under 50 chars, curiosity-driven, not salesy)
2. Opening (1 sentence: acknowledge their world, do not talk about yourself)
3. Pain point (1-2 sentences: the specific problem they likely face)
4. Solution teaser (1 sentence: how others like them solved it, no product pitch)
5. Social proof (1 sentence: a result a similar company achieved)
6. CTA (one ask, low friction — not "schedule a demo" but "worth a 15-min call?")
7. Signature (name, title, company)
Rules:
- No "I hope you are doing well"
- No "I wanted to reach out"
- No feature dump
- No "we are the leading provider of..."
- Talk about THEM, not YOU
- Under 125 words total (cold emails should be SHORT)
Format: Ready to send. Include 3 subject line variants to A/B test.

5. Follow-Up Email (No Response)

Role: Sales follow-up specialist
Task: Write follow-up email #[number] for a prospect who has not responded.
Previous emails: [Summarize what was sent before — subject lines, key points]
Prospect context: [Who they are, what they were interested in, last interaction]
Follow-up type: [Gentle nudge / value-add / break-up email]
Requirements:
1. Subject line (new angle, not a reply to the same thread)
2. Reference previous contact (brief: "I sent a note about [topic] last week")
3. New value (add something new — a resource, insight, case study — do not just ask again)
4. CTA (same or lower friction than before)
5. Alternative: give them an easy out ("Is this still a priority? Happy to reconnect when it is")
Rules by follow-up number:
- Follow-up 1: Add value, different angle (day 3-4)
- Follow-up 2: Different format (shorter, resource-led) (day 7-10)
- Follow-up 3: Break-up email ("I will stop reaching out, here is a resource for when you are ready") (day 14-21)
Length: Under 100 words. Shorter than the original.
Format: Ready to send.

6. Proposal Email

Role: Sales proposal writer
Task: Write an email to accompany a proposal document.
Context: [What was discussed, what the prospect needs, what was agreed verbally]
Proposal: [Attach/provide link — describe what is in it: scope, price, timeline]
Requirements:
1. Subject line (clear: "Proposal: [Project Name] for [Company]")
2. Opening (reference the conversation/meeting that led to this)
3. What is attached (1-2 sentences: what the proposal covers)
4. Key highlights (3 bullet points: scope, investment, timeline — at a high level)
5. What you need from them (review, sign, questions, next step)
6. Validity (how long is this proposal valid? why?)
7. Availability for questions (when/how can they reach you)
8. Closing (professional, looking forward to working together)
Tone: Confident, not desperate. The proposal speaks for itself — the email frames it.
Length: Under 200 words. The proposal is the star, not the email.

Internal Communication

7. Project Status Update Email

Role: Project manager writing a status email
Task: Write a project status update email.
Project: [Name, phase, overall health: Green/Yellow/Red]
Period: [Week/sprint/milestone]
Format:
1. Subject: [Project Name] Status Update — [Date] — [Green/Yellow/Red]
2. TL;DR (1-2 sentences: current state + any decisions needed)
3. This Period (bullet list: what was accomplished)
4. Next Period (bullet list: what is planned)
5. Risks/Issues (bullet list: what is concerning, what is being done)
6. Decisions Needed (what input do you need from stakeholders, by when?)
7. Budget Status (on track / over / under — with variance)
8. Schedule Status (on track / at risk / behind — with variance)
9. Links (dashboard, detailed plan, risks register)
Rules:
- Green/Yellow/Red in subject line so people can triage
- Bad news first in the body (people skim and may miss it)
- Every risk needs an action
- Under 300 words
Format: Email-ready status update for stakeholders.

8. Team Announcement Email

Role: Internal communications specialist
Task: Write a team announcement email.
Announcement: [What is changing — new hire, reorganization, policy change, project kickoff, win/loss]
Affected people: [Who needs to know, how they are affected]
Format:
1. Subject line (clear: "Announcement: [what] — [impact]" not "Update from [team]")
2. The news (lead with the announcement, not the rationale — people want to know what changed first)
3. What this means for you (practical impact — how it affects the reader day-to-day)
4. Why this is happening (1-2 sentences of context, not a essay)
5. Timeline (when does this take effect? what are the milestones?)
6. What stays the same (reassure — what is NOT changing)
7. Who to contact (for questions, the right person, not "let us know")
8. Next steps (what the reader needs to do, if anything)
Tone: Honest, respectful, not corporate-speak.
Constraint: Under 300 words. No "we are excited to announce" — just announce it.

9. Cross-Department Request Email

Role: Interdepartmental communication specialist
Task: Write an email requesting help from another department.
Request: [What you need, from whom, why, by when]
Context: [Do they know you? Is this the first request? What is the relationship?]
Format:
1. Subject line (specific: "Request: [what you need] — [deadline]")
2. Opening (who you are, what team, why you are reaching out to them specifically)
3. The request (clear, specific, not open-ended)
4. Why (business context — why this matters, what it enables)
5. What you need from them (specific deliverable, format, timeline)
6. What you have already done (show you have tried, not just passing work)
7. What they get (mutual benefit? visibility? reciprocity?)
8. Ask for availability (if this is a big ask, check capacity before assigning)
9. Appreciation (genuine, not perfunctory)
Tone: Peer-to-peer, respectful of their time, not demanding.
Length: Under 200 words. If it is a big ask, ask to schedule a call instead of email.

Client & Customer Emails

10. Client Onboarding Email Sequence

Role: Customer success communication specialist
Task: Create a 5-email onboarding sequence for [new clients/customers].
Product/service: [What they just signed up for]
Customer: [Who they are, what they want to achieve]
Email sequence:
Email 1 (Day 0 — Welcome):
- Welcome + what to do first (one action, not a list)
- How to get help if stuck
Email 2 (Day 2 — Quick Win):
- How to achieve first success (specific, small, satisfying)
- Encouragement + what is possible
Email 3 (Day 5 — Deeper Dive):
- Now that you have the basics, here is the next step
- Link to a resource (guide, video, template)
Email 4 (Day 10 — Value Expansion):
- Features they might not have discovered yet
- Use case examples from similar customers
Email 5 (Day 14 — Check-in):
- How is it going? Any questions?
- Offer a call/chat (low friction)
- If they have not engaged, different CTA (what is holding you back?)
For each email:
1. Subject line (friendly, not "Onboarding Email 1")
2. Preview text (the snippet they see before opening)
3. Body (short, action-oriented, personal tone)
4. CTA (one clear next action)
5. Timing (when to send, what trigger)
Tone: Helpful, not salesy. They already bought — help them succeed.

11. Apology & Service Recovery Email

Role: Customer service communication specialist
Task: Write an apology email for [what went wrong].
Incident: [What happened, impact on customer, duration, severity]
Format:
1. Subject line (clear, not defensive: "Regarding [issue] — our apology and what we are doing")
2. Acknowledge the impact (what they experienced, how it affected them — be specific)
3. Apologize (genuine, not "we apologize for any inconvenience" — name the problem)
4. Explain (briefly: what caused it — not excuses, just facts)
5. What we have done (immediate fix — what was done to resolve)
6. What we are doing (preventive — what will prevent recurrence)
7. What this means for you (any compensation, SLA credit, future commitment)
8. How to reach us (if they have questions or ongoing issues)
9. Closing (recommitment to their experience)
Tone rules:
- Own it (no passive voice: "an error occurred" -> "we made an error")
- Be specific (not "we value you" but "we know this caused you to miss your deadline")
- Do not minimize (not "a brief interruption" if it was 4 hours)
- Do not over-promise (only say what you can actually deliver)
Length: Under 250 words. Longer feels like justification.

12. Email Newsletter Template

Role: Email marketing writer
Task: Create an email newsletter template for [company/audience].
Audience: [Who receives this? Customers, prospects, subscribers?]
Frequency: [Weekly/biweekly/monthly]
Template structure:
1. Subject line (consistent format: "[Newsletter Name] — [This week topic]")
2. Preview text (1 sentence: the most interesting thing in this issue)
3. Header (logo, newsletter name, date)
4. Lead story (main item — 2-3 sentences + link to read more)
5. Quick links section (3-4 items: "Also worth reading")
6. Tip/resource (1 actionable tip or useful resource)
7. From the community (if applicable: user question, testimonial, highlight)
8. Coming next (tease what is in the next issue)
9. Footer (unsubscribe, preferences, social links)
For each section:
1. Purpose (why this section exists)
2. Content type (article link, tip, announcement, etc.)
3. Length guideline (words per section)
4. Personalization tokens (first name, company, etc.)
Output: Reusable newsletter template with section guidelines.
Rules:
- 80% value, 20% promotion (not the other way around)
- Mobile-first design (60%+ will read on phone)
- One primary CTA per issue (do not compete with yourself)

Best Practices

For more communication content, see our ChatGPT prompts for meeting notes and ChatGPT prompts for report writing.