Email & Communication prompts

Generates a focused cold outreach email with a clear CTA, useful for sales, partnerships, or networking.

Write a concise, professional cold outreach email from me to [RECIPIENT NAME/ROLE] at [COMPANY NAME]. My goal is [SPECIFIC GOAL, e.g. schedule a 20-minute intro call]. My name is [YOUR NAME] and I work at [YOUR COMPANY/ROLE]. Keep the tone [TONE, e.g. warm and direct], limit the body to 3 short paragraphs, and end with a single clear call to action. Do not use filler phrases like 'I hope this email finds you well.'

How to use: Fill in the recipient details, your goal, and preferred tone; adjust the CTA to match your ask.

Cleans up and elevates the tone of a rough or casual draft, ideal before sending to clients or senior stakeholders.

Rewrite the following email so it sounds polished and professional while preserving all the original information and intent. Remove any casual language, fix grammatical errors, and improve sentence flow. Keep the length roughly the same — do not add new content.

Original email:
[PASTE EMAIL HERE]

How to use: Paste your raw draft in the placeholder; specify if you want formal vs. approachable-professional.

Creates a brief, respectful follow-up that nudges without annoying, useful after unanswered emails.

Write a polite, non-pushy follow-up email. Context: I sent an email to [RECIPIENT NAME/ROLE] about [ORIGINAL TOPIC] on [DATE OR 'roughly X days ago']. They have not responded. My goal for this follow-up is [DESIRED OUTCOME]. Keep it under 100 words, reference my previous message naturally, and close with a low-friction call to action.

How to use: Specify the original topic and how long ago you sent it to give the AI helpful context.

Drafts a tactful refusal email that maintains goodwill, useful for declining meetings, proposals, or favors.

Write a professional email declining the following request while preserving the relationship. The request is: [DESCRIBE THE REQUEST]. My reason for declining is [YOUR REASON — or write 'do not state the reason explicitly']. The tone should be warm but firm. Offer an alternative or next step if appropriate. Keep it under 150 words.

How to use: If you prefer not to give a reason, write that in the placeholder; the AI will decline gracefully without one.

Converts a long email chain into a scannable summary with action items, great before meetings or for catching up.

Read the email thread below and produce a structured summary. Format your output as:
1. **Context** (1-2 sentences)
2. **Key decisions or agreements reached** (bullet list)
3. **Open questions** (bullet list)
4. **Action items** — each with a responsible party and deadline if mentioned

Email thread:
[PASTE FULL THREAD HERE]

How to use: Paste the entire thread including sender names and timestamps for the most accurate output.

Produces an accountable, well-structured apology email that rebuilds trust without being overly self-flagellating.

Draft a sincere professional apology email from me to [RECIPIENT NAME/ROLE]. The situation is: [DESCRIBE WHAT HAPPENED]. Acknowledge the mistake clearly, take responsibility without over-explaining or making excuses, describe the corrective action I am taking or have taken ([ACTION TAKEN]), and close with a commitment to prevent recurrence. Tone: genuine and professional. Length: 3 short paragraphs.

How to use: Be specific about what went wrong and what fix is in place so the email sounds credible and actionable.

Turns disorganized notes into a complete, send-ready email, saving time when you know what to say but not how.

Convert the following rough notes into a well-written professional email. Preserve every point — do not drop any information. The email is from me ([YOUR NAME/ROLE]) to [RECIPIENT NAME/ROLE]. Desired tone: [TONE]. Add a subject line suggestion at the top.

Notes:
[PASTE BULLET POINTS OR ROUGH NOTES HERE]

How to use: The more detail in the notes, the better the output; include names, dates, and any specific requests.

Creates a warm, mutually beneficial introduction email, ideal for networking or facilitating business connections.

Write a double opt-in introduction email connecting [PERSON A NAME & BRIEF CONTEXT] and [PERSON B NAME & BRIEF CONTEXT]. Explain why each person benefits from knowing the other. Keep it under 200 words. Use a subject line format of 'Intro: [Person A] <> [Person B]'. Address both people in the greeting. Close by asking both to take it from here.

How to use: Provide a one-line bio for each person and one reason the connection is valuable to make it feel personal.

Generates an empathetic, de-escalating customer service response to a complaint, useful for support teams.

Write a professional customer service reply to the angry complaint below. Your reply should: (1) acknowledge the customer's frustration with empathy, (2) apologize for the experience without admitting legal liability, (3) briefly explain what happened if appropriate ([EXPLANATION, or 'do not explain cause']), (4) state the resolution or next step: [RESOLUTION/NEXT STEP], and (5) invite further contact. Tone: calm, caring, and solution-focused. Length: 3-4 paragraphs.

Customer complaint:
[PASTE COMPLAINT HERE]

How to use: Fill in the resolution before generating so the AI produces a concrete, actionable reply rather than a vague one.

Produces a confident yet collegial salary negotiation email grounded in the user's specific justifications.

Draft a professional email negotiating my salary for the role of [JOB TITLE] at [COMPANY NAME]. The offer I received is [OFFERED SALARY/PACKAGE]. My target is [TARGET SALARY/PACKAGE]. My key justifications are: [LIST 2-3 REASONS, e.g. years of experience, competing offer, market rate]. Tone: confident, collaborative, and respectful — not aggressive. Keep it under 250 words. Do not use ultimatums. End with an invitation to discuss.

How to use: Be specific about your target number and reasons; vague justifications produce vague letters.

Trims a verbose email to a more readable length, ideal for busy recipients or senior executives.

Shorten the email below by at least 40% while retaining every important piece of information, all action items, and the original tone. Cut filler phrases, redundant sentences, and over-explanation. Do not add new content. Output the revised email only — no commentary.

Original email:
[PASTE EMAIL HERE]

How to use: If certain sections must stay in full (e.g. legal language), note that before the placeholder.

Produces three audience-tailored versions of one message, useful when the same news must go to different stakeholders.

Take the core message below and rewrite it as three separate emails, each adapted for a different audience. Keep the facts identical; only change the tone, vocabulary, and level of technical detail.

Audience 1: [AUDIENCE 1, e.g. C-suite executive — high-level, brief]
Audience 2: [AUDIENCE 2, e.g. technical team — detailed, specific]
Audience 3: [AUDIENCE 3, e.g. external customer — plain language, benefit-focused]

Core message:
[PASTE OR DESCRIBE THE MESSAGE]

How to use: Define the audiences precisely so the tone shifts are meaningfully different across the three versions.

Generates a structured project status email that keeps stakeholders informed and flags any decisions needed.

Write a project status update email from me to [AUDIENCE, e.g. project sponsor, steering committee]. Use this structure:
- **Subject line** (concise and informative)
- **Overall status**: [GREEN / YELLOW / RED] — one sentence reason
- **Progress since last update**: [KEY ACCOMPLISHMENTS]
- **Upcoming milestones**: [NEXT 2-3 MILESTONES AND DATES]
- **Risks or blockers**: [RISKS, or 'none at this time']
- **Decisions needed from you** (if any): [DECISIONS NEEDED]

Tone: clear, factual, and confident. Total length: under 300 words.

How to use: Fill in all placeholders with current data; the clearer the inputs, the more useful the output.

Converts raw meeting notes into a polished recap with a clear action-item table, reducing follow-up confusion.

Write a meeting recap email to send to all attendees. The meeting was about [MEETING TOPIC] on [DATE]. Attendees included: [LIST NAMES/ROLES]. Use this format:

**Subject**: Recap – [MEETING TOPIC] – [DATE]

**Thank you note** (one line)
**Key discussion points** (3-5 bullets)
**Decisions made** (bullets)
**Action items** (table with columns: Task | Owner | Due Date)
**Next meeting** (if applicable): [DATE/TIME or 'TBD']

Notes from the meeting:
[PASTE YOUR NOTES HERE]

How to use: Even messy or incomplete notes work well — paste what you have and the AI will structure them.

Creates a high-stakes escalation email that documents the issue and demands resolution, useful for vendor management.

Draft a firm but professional escalation email to [VENDOR NAME] regarding [ISSUE, e.g. repeated late deliveries, unresolved support ticket]. Background: [1-3 SENTENCES OF CONTEXT, including dates and previous attempts to resolve]. I am escalating to [VENDOR CONTACT TITLE/NAME]. State the business impact clearly: [IMPACT]. Request a specific resolution by [DEADLINE]. Tone: assertive without being hostile. Include a subject line.

How to use: Include dates and ticket/reference numbers in the context for a credible, specific email.

Detoxifies an emotionally charged email before sending it, preventing professional damage from reactive writing.

Rewrite the email below to remove any passive-aggressive, sarcastic, or emotionally charged language. The goal is to communicate the same content professionally and constructively. Preserve all factual information and requests. Flag any phrases you changed and briefly explain why in a comment after the rewritten email.

Original email:
[PASTE EMAIL HERE]

How to use: Use this before sending any email you drafted while frustrated; review the flagged phrases to learn your patterns.

Drafts a considerate, context-rich reference request that makes it easy for the referee to agree and write well.

Write a professional email from me to [REFERENCE'S NAME/ROLE] asking them to serve as a reference for [PURPOSE, e.g. a job application at [COMPANY], a graduate school application]. Include: (1) a warm personal opening, (2) a brief reminder of our relationship and the work we did together: [CONTEXT], (3) why I am applying and why I think they would be a strong reference, (4) the deadline for the reference: [DEADLINE], (5) an offer to provide supporting materials. Keep it under 250 words and easy to say yes to.

How to use: The more relationship context you provide, the more personalized and persuasive the email will be.

Produces a clear, empathetic internal communication for difficult workforce changes, reducing confusion and preserving trust.

Draft an internal email from [SENDER NAME/ROLE] to [AFFECTED GROUP, e.g. 'the Marketing team'] announcing [SITUATION, e.g. a team restructuring that eliminates two roles]. The tone must be honest, humane, and clear — avoid corporate euphemisms. Include: (1) what is happening and why, (2) who is affected and the timeline, (3) what support is being offered: [SUPPORT, e.g. severance, career transition resources], (4) next steps and who to contact with questions. Do not minimize the impact. Keep it under 400 words.

How to use: Have HR review the output before sending; fill in all placeholders with confirmed details only.

Generates a complete 3-part email nurture sequence with escalating intent, useful for marketing or sales teams.

Write a 3-email nurture sequence for [AUDIENCE, e.g. leads who downloaded a free guide] with the end goal of [CONVERSION GOAL, e.g. booking a consultation call]. Product or service being promoted: [PRODUCT/SERVICE DESCRIPTION].

Email 1 (Day 0): Deliver value — educate or help, no hard sell.
Email 2 (Day 3): Build credibility — use a story, case study, or insight.
Email 3 (Day 7): Make the ask — clear CTA toward [CONVERSION GOAL].

Each email needs: Subject line, preview text, body (under 200 words), and CTA. Tone: [TONE].

How to use: Provide specifics about your audience's pain point so each email speaks directly to a real need.

Provides a structured expert critique plus a revised email, ideal for high-stakes messages before they are sent.

Act as a senior communications coach. Audit the email draft below and provide structured feedback in this format:

1. **Overall impression** (2-3 sentences)
2. **Clarity issues** — quote the unclear passage, then explain the problem
3. **Tone issues** — quote the passage, explain the risk
4. **Persuasion gaps** — what is missing that would make the reader more likely to act?
5. **Top 3 recommended edits** — specific, actionable
6. **Revised version** — full rewrite incorporating your recommendations

Email draft:
[PASTE DRAFT HERE]

Context: The email is being sent by [SENDER ROLE] to [RECIPIENT ROLE]. The desired outcome is [DESIRED OUTCOME].

How to use: Include the context fields so the AI judges the email against the right standards for audience and goal.

Creates a transparent, accountable crisis email that informs customers and protects brand trust during an incident.

Draft an external email from [COMPANY NAME] to customers addressing the following incident: [DESCRIBE INCIDENT, e.g. a data breach, service outage, product recall]. The email must: (1) state clearly what happened and when, (2) acknowledge the impact on customers without minimizing it, (3) explain what actions we have already taken, (4) tell customers what they need to do (if anything): [CUSTOMER ACTIONS, or 'none required'], (5) provide a support contact: [CONTACT INFO], (6) close with a commitment. Tone: transparent, accountable, and calm. Avoid legal boilerplate. Have your legal team review before sending.

How to use: Use only confirmed facts in the placeholders; do not speculate about causes or scope in the draft.

Produces six subject line variants with analysis, helping marketers choose the strongest option for A/B testing.

I have an email with the following body and context:

Context: Audience is [AUDIENCE]. Goal is [EMAIL GOAL, e.g. maximize open rate, drive clicks to a landing page].

Email body:
[PASTE EMAIL BODY HERE]

Do the following:
1. Generate 6 distinct subject line variants — vary the approach: curiosity, benefit-led, question, urgency, personalization, and plain-spoken.
2. For each variant, write a matching preview text (under 90 characters).
3. Score each subject line 1-10 for estimated open-rate potential and explain your reasoning in one sentence.
4. Recommend the top 2 for A/B testing and explain why.

How to use: Provide the full email body so the subject lines stay accurate and relevant to the content.

Produces a structured, executive-appropriate briefing email that respects senior leaders' time and frames issues strategically.

Draft a concise briefing email from [SENDER NAME/ROLE] to [BOARD OR EXECUTIVE COMMITTEE NAME] covering the following situation: [TOPIC/SITUATION]. The audience expects: executive-level brevity, strategic framing, and clear recommendations — not operational detail. Structure:
- **One-line headline** summarizing the situation
- **Context** (2-3 sentences maximum)
- **Key data or facts** (3 bullets, no fluff)
- **Implications** (what this means for the business)
- **Recommended action(s)** with rationale
- **Decision requested** (if any): [DECISION NEEDED, or 'none — informational only']

Total length: under 300 words. No jargon.

How to use: Summarize the situation in plain terms in the placeholder; the AI will elevate and structure it appropriately.

Flags compliance and legal risks in a draft and rewrites it safely, useful for regulated industries or high-stakes communication.

Review the email draft below for potential compliance and communication risks, including but not limited to: making promises the company may not be able to keep, implying guarantees, statements that could constitute legal admissions, discriminatory language, or privacy concerns. For each risk you identify: (1) quote the problematic text, (2) explain the risk category, (3) suggest a safer alternative phrasing. Then provide a clean revised version of the full email with all risks resolved.

Industry context: [INDUSTRY, e.g. financial services, healthcare, SaaS]

Email draft:
[PASTE DRAFT HERE]

Note: This output is a drafting aid and should be reviewed by qualified legal or compliance professionals before sending.

How to use: Always have a qualified compliance or legal professional review the final output before sending regulated communications.

Drafts a structured, persuasive internal proposal email using a classic problem-solution framework to move decision makers.

Write a persuasive internal email from me ([YOUR ROLE]) to [DECISION MAKER ROLE, e.g. VP of Operations] proposing [PROPOSAL SUMMARY, e.g. adopting a new project management process]. Structure the email using the Problem → Solution → Benefit → Ask framework:

1. **Problem**: Clearly state the current pain point using specifics: [SPECIFIC PROBLEM/EVIDENCE]
2. **Solution**: Describe the proposal concisely: [SOLUTION DETAILS]
3. **Benefits**: List 2-3 measurable or tangible benefits: [BENEFITS]
4. **Risks addressed**: Briefly pre-empt the most likely objection: [LIKELY OBJECTION]
5. **Ask**: One specific, low-friction next step: [DESIRED NEXT STEP]

Tone: collegial and confident. Length: under 350 words. Include a subject line.

How to use: Pre-empting objections in placeholder 4 often makes or breaks internal proposals — think like your skeptic.