Claude Prompts for Emails

You are an internal comms lead who writes clear, motivating team updates. Write an announcement email to the team. <context>What I'm announcing: [news — new hire, reorg, tool, win, goal]. Why it matters to the team: [impact on their work]. What (if anything) changes for them: [action needed, none]. Timeline: [dates]. Tone I want: [celebratory, matter-of-fact, reassuring].</context> <task>Write an announcement that leads with the news, explains the 'why', spells out what changes for the reader, and ends with next steps or where to ask questions.</task> <constraints>Under 160 words. Clear and human, no corporate filler. Answer 'what does this mean for me?' explicitly. If action is needed, make it unmissable. Skimmable structure.</constraints> <format>Subject line stating the news, a one-line TL;DR, a short 'what's happening' paragraph, a 'what this means for you' section, and a 'questions?' line with a channel. Use bold for the key action.</format>

You are a project manager who writes status updates people actually read. Write a status update email to stakeholders. <context>Project: [name, goal]. Reporting period: [dates]. Progress: [what shipped/completed]. On track? [green/yellow/red] because [reason]. Risks or blockers: [items]. What I need from stakeholders: [decisions, resources]. Next milestones: [items + dates].</context> <task>Write a status update that gives a clear health signal up top, summarizes progress, flags risks honestly, and makes any asks explicit.</task> <constraints>Under 170 words. Lead with the status (green/yellow/red), not a wall of detail. Be honest about risks. Separate 'FYI' from 'action needed.' No jargon.</constraints> <format>Subject line with project + status color, a one-line summary, sections: Done, In progress, Risks/Blockers, Decisions needed (with owner + date), Next up. Bullets, not paragraphs.</format>

You are a manager who gets buy-in from other teams. Write an email requesting help or resources from another team. <context>Who I'm asking: [team/person]. What I need: [specific deliverable or help]. Why it matters: [business/customer impact]. Deadline: [date] and why. What's in it for them: [shared goal, reciprocity, visibility]. Effort involved: [rough estimate].</context> <task>Write a request that states the ask precisely, justifies the priority, respects their workload, and makes saying yes easy.</task> <constraints>Under 130 words. Respectful of their time and priorities — acknowledge you're adding to their plate. Be specific about scope and deadline. Offer to trim scope or reciprocate. One clear ask.</constraints> <format>Subject line naming the ask, greeting, a short 'here's what I need and why' paragraph, a scope + deadline line, a 'here's what I can offer / flex' line, and a CTA to confirm or discuss.</format>

You are a thoughtful manager who gives feedback that lands. Write a feedback email to a direct report. <context>Person: [name, role]. The feedback: [specific behavior or work — positive, constructive, or both]. Concrete examples: [what happened]. The impact: [on team, project, or them]. What good looks like: [desired behavior]. Their strengths to anchor on: [context].</context> <task>Write feedback that is specific and behavioral, anchored in examples, focused on impact, and paired with a clear path forward — never vague or personal.</task> <constraints>Under 160 words. Kind and direct. Describe behavior, not character. Use real examples. Balance any critique with genuine recognition. Invite their perspective — feedback is a dialogue, not a verdict.</constraints> <format>Greeting, a warm opener, the specific observation + example, the impact, the path forward, and an invitation to discuss in your next 1:1. Keep it personal, not a form letter.</format>

You are an HR or ops lead who rolls out policy changes clearly. Write a company-wide email announcing a policy change. <context>The change: [old policy → new policy]. Why: [reason — legal, business, feedback]. Effective date: [date]. Who's affected: [everyone / specific groups]. What people must do: [action, if any]. Where to get help: [contact/resource].</context> <task>Write a memo that states the change and effective date up front, explains the reasoning honestly, clarifies who's affected and what to do, and points to support.</task> <constraints>Under 180 words. Transparent and empathetic — acknowledge if it's an adjustment. No legalese. Make the effective date and required actions impossible to miss. Anticipate the top question.</constraints> <format>Subject line naming the change, a TL;DR box (what's changing, when, what you need to do), a 'why' paragraph, a 'who this affects' section, a mini-FAQ of 2-3 likely questions, and a support contact.</format>

You are a newsletter editor who writes engaging company updates. Write one issue of an internal or customer newsletter. <context>Audience: [customers / employees / community]. This issue's items: [product news, tips, event, spotlight, metric]. The one thing I most want them to do: [primary CTA]. Voice: [friendly, expert, playful]. Length target: [short/medium].</context> <task>Write a newsletter issue with a strong intro, 3-4 skimmable sections, and one clear primary CTA — informative, not promotional.</task> <constraints>Length as specified. Lead with value, not announcements. Each section earns its place. One primary CTA, secondary links minimal. Conversational voice throughout. Scannable on mobile.</constraints> <format>Subject line + preview text, a short personal intro, 3-4 sections each with a heading and 2-3 sentences, a clear primary CTA button line, and a one-line sign-off. Suggest 2 subject-line variants.</format>

You are a product marketer who announces releases so people actually adopt them. Write a product update email. <context>What's new: [features/improvements]. Who benefits and how: [use cases]. The headline feature: [the one to lead with]. What users should do: [try it, update, watch demo]. Any migration or action needed: [detail]. Link: [changelog/docs].</context> <task>Write an update that leads with the most valuable change framed as a user benefit, explains what it unlocks, and drives one action.</task> <constraints>Under 160 words. Benefit-first, not feature-list dumping. Lead with the biggest win. Show, don't just tell (a one-line example). One primary CTA. Link to details for the curious.</constraints> <format>Subject line naming the top benefit, a one-line hook, a 'what's new' highlight for the headline feature with a concrete example, a short bulleted list of smaller updates, and a primary CTA. Add a 'see full changelog' link line.</format>

You are a content marketer who nurtures leads with genuinely useful emails. Write one educational nurture email. <context>Audience: [who they are, where in the funnel]. The problem they have: [pain]. The lesson/tip I'm teaching: [insight, framework, how-to]. How my product relates (softly): [connection]. Where I want them to go next: [content, trial, call].</context> <task>Write an email that teaches one useful thing they can act on today, then makes a soft, relevant transition to the next step.</task> <constraints>Under 170 words. 90% value, 10% pitch. Teach something they can use even if they never buy. The product mention must feel earned, not bolted on. One low-pressure CTA.</constraints> <format>Subject line promising the lesson, a hook that names the pain, the teachable insight with a concrete example or steps, a soft one-line bridge to my product, and a single CTA. Skimmable formatting.</format>

You are a lifecycle marketer who re-engages dormant subscribers or users. Write a win-back email. <context>Who: [inactive users/subscribers]. How long dormant: [time]. What's changed since they left: [new features, content, offer]. Why they might have gone quiet: [guess]. The incentive if any: [discount, free month, new value]. The exit option: [preference update or unsubscribe].</context> <task>Write a re-engagement email that acknowledges the gap without guilt, gives a concrete reason to return, and respects their choice to opt down.</task> <constraints>Under 120 words. Light and human, a touch of personality. Lead with what's new or the incentive, not 'we miss you' alone. Make returning one click. Offer a graceful opt-down, not just a hard unsubscribe.</constraints> <format>Subject line with curiosity or an offer, a warm one-line opener, the 'here's what's new / here's the offer' hook, a single strong CTA button line, and a soft 'update your preferences' link. Suggest 2 subject lines.</format>

You are an event marketer who writes invitations that drive registrations. Write an event invite email. <context>Event: [name, type — webinar, workshop, launch, meetup]. Date/time + timezone: [detail]. Who it's for: [audience]. The value / what they'll learn or get: [outcomes]. Speakers or highlights: [names/topics]. How to register: [link]. Urgency: [limited seats, deadline].</context> <task>Write an invitation that sells the outcome (what they'll walk away with), makes the logistics crystal clear, and drives registration with light urgency.</task> <constraints>Under 150 words. Benefit-led — why attend, not just what it is. Logistics unmissable (date, time, zone). One primary CTA repeated once. Genuine urgency only.</constraints> <format>Subject line with the hook, a one-line value promise, a short 'what you'll get' bulleted list, a clear logistics block (date/time/where), a primary 'Register' CTA line, and a P.S. with urgency. Add 2 subject-line variants.</format>

You are a communications lead who writes apologies that rebuild trust. Write an apology email for a mistake or outage. <context>What went wrong: [incident]. Who was affected and how: [impact]. What caused it: [honest cause]. What we're doing to fix it: [immediate fix]. What we're doing so it won't recur: [prevention]. Any goodwill gesture: [credit, extension].</context> <task>Write an apology that owns the mistake plainly, acknowledges the impact, explains what happened and what we're changing, and offers a fair gesture.</task> <constraints>Under 150 words. Sincere and direct — 'we're sorry,' not 'we apologize for any inconvenience.' No blame-shifting or PR spin. Be specific about the fix and prevention. Human sign-off from a named person.</constraints> <format>Subject line that names the issue, a plain apology in the first line, a short 'what happened' explanation, 'what we've done and what's next,' the goodwill gesture, and a signed sign-off with a contact for follow-up.</format>

You are an accounts-receivable pro who collects payment while keeping the client. Write an email chasing an overdue invoice. <context>Client: [name, company]. Invoice: [number, amount, original due date]. How overdue: [days]. Prior reminders sent: [none/some]. The relationship: [ongoing/one-off]. Payment options: [link, methods]. Any late-fee policy: [detail].</context> <task>Write a firm-but-friendly reminder that states the specifics, makes paying effortless, and asks for a commitment date if they can't pay immediately.</task> <constraints>Under 110 words. Professional, not apologetic or aggressive — this is owed money. State the exact invoice and amount. Give a one-click payment path. Ask for a specific date if there's an issue. Escalate tone only if prior reminders were ignored.</constraints> <format>Subject line with invoice number + 'payment reminder', greeting, a clear line stating amount + due date + days overdue, a payment link line, and a 'if there's an issue, when can we expect payment?' close. Provide a gentler first-reminder version and a firmer final-notice version.</format>

You are a trusted senior professional who disagrees with a manager constructively. Write an email pushing back on a decision or request. <context>What I'm pushing back on: [decision/request]. Why I disagree: [risks, data, tradeoffs]. What I recommend instead: [alternative]. What I understand about their goal: [their intent]. My relationship/standing: [context]. Willingness to comply if overruled: [yes].</context> <task>Write pushback that shows I share their goal, presents evidence and a concrete alternative, and offers to align once we've discussed — respectful, not combative.</task> <constraints>Under 150 words. Curious and collaborative, never insubordinate. Acknowledge their objective first. Lead with data or a specific risk, not feelings. Offer a clear alternative and a path to decide together. Signal you'll commit either way.</constraints> <format>Greeting, a line affirming the shared goal, the concern with specific evidence, a concrete recommendation, and a 'can we talk it through?' close. Keep it as something they'd respect, not resent.</format>

You are a client-services lead who delivers bad news without losing the account. Write an email breaking difficult news to a client. <context>The bad news: [delay, overrun, scope cut, failure]. Why it happened: [honest reason]. The impact on them: [timeline, cost, outcome]. What we're doing about it: [recovery plan]. Options for them: [choices]. What I need from them: [decision, patience].</context> <task>Write an email that delivers the news clearly and early, takes appropriate ownership, presents a recovery plan and options, and keeps confidence in us.</task> <constraints>Under 160 words. Lead with the news — no burying it in paragraph three. Honest, no excuses, no over-promising. Pair the problem with a plan. Give them agency with options. Confident, solution-focused tone.</constraints> <format>Subject line that's honest but not alarmist, a direct opening stating the news, a brief 'why' in plain terms, a recovery plan with dates, options for them to choose, and a next-step request. Offer to hop on a call.</format>

You are a career coach who helps people make the case for a raise or promotion. Write an email requesting a compensation review. <context>My role: [title]. Time in role / at company: [duration]. Key accomplishments and impact: [results, metrics]. Scope that's grown: [added responsibilities]. Market data or benchmark: [comp range]. The specific ask: [raise %, new title, band]. When I want to discuss: [timing].</context> <task>Write an email that requests a conversation, summarizes my impact with evidence, states a specific ask backed by rationale, and stays collaborative.</task> <constraints>Under 150 words. Confident and evidence-based, not entitled or apologetic. Lead with impact and metrics, not tenure or need. Make a specific ask with a clear rationale. Frame it as a discussion, not an ultimatum.</constraints> <format>Subject line requesting a comp conversation, greeting, a short 'here's the impact I've delivered' section with 2-3 concrete results, the specific ask with market rationale, and a request to meet. Keep it forwardable to HR.</format>