30 Claude Prompts That Build Email Templates

You are a customer-support communications writer who builds clear auto-reply templates. <context> I need a reusable support ticket acknowledgement (auto-reply) email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - Company or product name: [NAME] - Typical first-response time: [E.G. WITHIN 24 HOURS] - Self-serve resources: [HELP CENTER / FAQ URL] - Tone: [WARM / PROFESSIONAL] - Ticket fields available: [TICKET NUMBER, SUBJECT] </inputs> <task> Build the template with: one subject line option that includes the ticket reference, a preheader, an empathetic opener using {{first_name}} confirming we received the request, a line restating their issue via {{ticket_subject}} and its reference {{ticket_number}}, a realistic response-time expectation using {{response_time}}, a link to self-serve help via {{help_url}} in the meantime, and a reassuring sign-off. Keep it human and honest. </task> <constraints> - Set a realistic expectation; never promise a time you can't hit. - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Empathetic, specific copy; no robotic "your request is important to us". </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to adapt it for out-of-hours or high-volume periods. </format>

You are a support writer who crafts resolution emails that leave customers satisfied. <context> I need a reusable "issue resolved" (ticket closed) email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - Company or product name: [NAME] - Ticket fields available: [TICKET NUMBER, ISSUE SUMMARY] - Whether to request feedback: [YES / NO] - Reopen instructions: [HOW TO REOPEN] - Tone: [FRIENDLY / PROFESSIONAL] </inputs> <task> Build the template with: one subject line referencing resolution, a preheader, an opener using {{first_name}}, a plain summary of what was fixed via {{issue_summary}} for ticket {{ticket_number}}, a line on how to reopen if the issue persists, an optional one-click satisfaction ask (thumbs up/down) linking {{feedback_url}}, and a warm sign-off from {{agent_name}}. Keep it clear and closing on a positive note. </task> <constraints> - State what was done in plain language; make reopening easy. - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Genuine, specific copy; no premature "glad we could help" if unresolved. </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to attach a full CSAT survey instead of the quick thumbs. </format>

You are an incident-communications specialist who writes calm, credible status emails. <context> I need a reusable service outage / incident notification email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - Product name: [NAME] - What's affected: [FEATURE / WHOLE SERVICE] - Current status: [INVESTIGATING / IDENTIFIED / MONITORING / RESOLVED] - Status page URL: [LINK] - Tone: [TRANSPARENT / REASSURING] </inputs> <task> Build a template with clearly marked slots for each incident stage: subject line, a one-line summary of what's affected via {{affected_service}}, the current status {{incident_status}}, what users may experience, what the team is doing, the next-update time via {{next_update_time}}, and a link to the live status page {{status_url}}. Include a short resolved-update variant at the bottom. Keep it calm, honest, and jargon-free. </task> <constraints> - No blame, no vague "some users"; be specific about impact and timing. - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Provide the resolved variant so the same template covers the all-clear. </constraints> <format> Return the full template (initial + resolved variant) as a code block artifact, then list the merge fields and note how to reuse it for planned maintenance. </format>

You are a customer-experience writer who crafts sincere service-recovery emails. <context> I need a reusable apology / service-recovery email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - Company or product name: [NAME] - What went wrong: [THE PROBLEM] - Who is affected: [SEGMENT] - The gesture offered: [REFUND / CREDIT / EXTENSION / NONE] - Tone: [SINCERE / ACCOUNTABLE] </inputs> <task> Build the template with: one subject line that signals accountability, a preheader, an opener using {{first_name}} that owns the problem directly via {{issue_summary}}, a plain explanation of what happened without excuses, what you've done to fix it and prevent recurrence, the goodwill gesture using {{gesture}} if offered, a direct line to reach a human via {{support_url}}, and a genuine sign-off from a named person. Keep it honest and specific. </task> <constraints> - Own it in the first two lines; no corporate deflection or "any inconvenience". - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Concrete fix and next steps; the gesture is optional but must feel proportional. </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to scale the tone up or down by severity. </format>

You are a customer-research writer who builds feedback-request emails that get responses. <context> I need a reusable feedback / CSAT request email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - Company or product name: [NAME] - The moment triggering it: [POST-PURCHASE / POST-SUPPORT / 30-DAY MARK] - Scale or question: [1-5 RATING / NPS / ONE OPEN QUESTION] - Estimated time to complete: [E.G. 30 SECONDS] - Tone: [FRIENDLY / CONCISE] </inputs> <task> Build the template with: two subject line options and a preheader, a short opener using {{first_name}} referencing the moment, one clear sentence on why their input matters, the survey ask with an estimated time {{time_estimate}}, a prominent single CTA linking {{survey_url}} (or inline rating buttons), and a thank-you line. Keep it under a screen and ask for one thing only. </task> <constraints> - One ask, one CTA; state the time cost honestly to lift completion. - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Specific reason their feedback matters; no generic "we value your opinion". </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to embed clickable 1-5 rating buttons that deep-link to the survey. </format>

You are a B2B sales writer who crafts follow-up emails that keep deals moving. <context> I need a reusable post-demo follow-up email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - What you sell: [PRODUCT AND CORE VALUE] - The prospect's main goal or pain: [WHAT THEY CARE ABOUT] - Key moment or objection from the demo: [WHAT STOOD OUT] - Next step you want: [PROPOSAL / TRIAL / SECOND CALL] - Tone: [CONSULTATIVE / CONCISE] </inputs> <task> Build the template with: two subject line options and a preheader, an opener using {{first_name}} that references a specific demo moment via {{demo_highlight}}, a two-line recap tying the product to their goal {{prospect_goal}}, a short bullet list of the exact next steps, a single clear CTA linking {{next_step_url}} (book time or view proposal), and a low-pressure sign-off from {{rep_name}}. Keep it tight and personalized. </task> <constraints> - One clear next step; reference something specific, not a generic "great talking". - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Concise, consultative copy; no pushy "just following up" filler. </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to fork it into a gentle second-touch nudge if they go quiet. </format>

You are an account executive's writing assistant who crafts proposal-send emails that get signatures. <context> I need a reusable proposal / quote send email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - What you're proposing: [SCOPE OR PACKAGE] - The headline value or outcome: [THE PAYOFF] - Price and terms: [AMOUNT, TERM] - Validity or deadline: [E.G. VALID 14 DAYS] - Next step: [E-SIGN / CALL TO DISCUSS] </inputs> <task> Build the template with: two subject line options and a preheader, an opener using {{first_name}} that frames the outcome via {{headline_value}}, a one-paragraph summary of what's included, the investment line using {{price}} and {{terms}}, a validity line using {{valid_until}}, a single prominent CTA linking {{proposal_url}} to view or sign, and an offer to hop on a call for questions. Keep it confident and clear. </task> <constraints> - Lead with outcome and value before price; one dominant CTA. - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Specific scope and terms; no vague "let me know your thoughts". </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to adapt it into a follow-up if the proposal isn't opened. </format>

You are a sales-development writer who crafts meeting-request emails that get on the calendar. <context> I need a reusable meeting request / booking email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - Who you are and what you do: [ROLE, COMPANY, VALUE] - Why now / the relevant trigger: [REASON TO TALK] - What the prospect gets from the call: [SPECIFIC PAYOFF] - Meeting length: [E.G. 15 MINUTES] - Booking method: [CALENDAR LINK / PROPOSED TIMES] </inputs> <task> Build the template with: two short subject line options and a preheader, a one-line opener using {{first_name}} tied to a relevant trigger via {{trigger_reason}}, a two-line value statement on what they'll get from a {{meeting_length}} call, a single clear CTA (calendar link {{booking_url}} or two proposed times), and a brief, respectful sign-off from {{rep_name}}. Keep the whole email under 120 words. </task> <constraints> - Under 120 words; one specific ask with an easy way to say yes. - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Lead with relevance to them, not your product pitch; no fluff. </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to write a two-line bump follow-up for non-responders. </format>

You are a sales writer who crafts gracious reschedule emails after a missed meeting. <context> I need a reusable no-show reschedule email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - What the meeting was about: [PURPOSE] - Your name and role: [REP, COMPANY] - The value they'd still get: [PAYOFF OF RESCHEDULING] - Rebooking method: [CALENDAR LINK / PROPOSED TIMES] - Tone: [UNDERSTANDING / LIGHT] </inputs> <task> Build the template with: one subject line that's warm and blame-free, a preheader, a light opener using {{first_name}} assuming good intent ("looks like we missed each other"), a one-line reminder of the meeting purpose via {{meeting_topic}}, a restatement of the value they'd get, a single easy rebooking CTA linking {{rebook_url}}, and a no-pressure sign-off from {{rep_name}}. Keep it short and free of guilt. </task> <constraints> - Zero blame or passive-aggression; make rebooking effortless. - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Brief and human; one clear CTA. </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to write a final "should I close this out?" break-up email. </format>

You are a closer's writing assistant who crafts final-step emails that get contracts signed. <context> I need a reusable deal-closing / signature nudge email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - What's being signed: [CONTRACT / ORDER FORM] - The agreed outcome or start date: [WHAT SIGNING UNLOCKS] - Any remaining blocker to preempt: [LEGAL / BUDGET / TIMING] - Deadline or reason to sign now: [DATE / ONBOARDING SLOT] - Tone: [WARM / DIRECT] </inputs> <task> Build the template with: two subject line options and a preheader, an opener using {{first_name}} restating the agreed outcome via {{agreed_outcome}}, a one-line reminder of what signing unlocks and the timeline, a sentence preempting the likely blocker via {{blocker}}, a single prominent CTA linking {{signature_url}}, a reason to act by {{deadline}}, and an offer to jump on a quick call if anything's unclear. Keep it confident and helpful. </task> <constraints> - One dominant CTA (sign); reference a real reason to act now, not fake urgency. - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Address the actual blocker; no generic "just checking in". </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to soften or sharpen the urgency by deal stage. </format>

You are an HR communications writer who crafts warm, practical onboarding emails. <context> I need a reusable new-hire welcome / first-day email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - Company name: [COMPANY] - Role and team: [TITLE, TEAM] - Start date and time: [WHEN TO SHOW UP OR LOG IN] - First-day logistics: [WHERE, WHAT TO BRING, WHO TO MEET] - Point of contact: [NAME AND HOW TO REACH] </inputs> <task> Build the template with: one warm subject line, a preheader, an enthusiastic opener using {{first_name}} welcoming them to the team, a clear first-day details block using {{start_date}}, {{start_time}}, and {{location_or_link}}, a short "what to expect on day one" list, a note on their point of contact via {{buddy_name}}, a line on what to bring or set up beforehand, and a warm sign-off from {{sender_name}}. Keep it welcoming and logistics-clear. </task> <constraints> - Logistics must be unmissable; one clear point of contact. - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Genuinely warm and specific; no corporate boilerplate. </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to adapt it for remote versus in-office starts. </format>

You are a recruiting-operations writer who crafts clear, respectful interview invitations. <context> I need a reusable interview invitation email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - Company and role: [COMPANY, TITLE] - Interview format: [PHONE / VIDEO / ONSITE] - Length and who they'll meet: [DURATION, INTERVIEWERS] - Scheduling method: [CALENDAR LINK / PROPOSED SLOTS] - What to prepare: [PORTFOLIO / TASK / NOTHING] </inputs> <task> Build the template with: one subject line naming the role, a preheader, a positive opener using {{first_name}} confirming they're moving forward for the {{role_title}} role, a details block covering format {{interview_format}}, length {{duration}}, and who they'll meet {{interviewers}}, a scheduling CTA linking {{scheduling_url}}, a line on what to prepare via {{prep_notes}}, and an encouraging sign-off from {{recruiter_name}}. Keep it clear and candidate-friendly. </task> <constraints> - Format, length, and prep must be explicit; one scheduling action. - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Respectful, transparent copy; no vague "we'd like to chat". </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to adapt it for a final-round versus first-round invite. </format>

You are an HR writer who crafts exciting, professional job-offer emails. <context> I need a reusable job offer email template (cover note that accompanies the formal letter) as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - Company and role: [COMPANY, TITLE] - Headline compensation: [SALARY / RANGE, KEY BENEFIT] - Proposed start date: [DATE] - Response deadline: [BY WHEN] - Point of contact for questions: [NAME] </inputs> <task> Build the template with: one celebratory-but-professional subject line, a preheader, an opener using {{first_name}} that clearly extends the offer for the {{role_title}} role, a short highlights block covering compensation {{compensation}} and start date {{start_date}}, a line pointing to the attached formal offer for full details, a clear next step to accept via {{offer_url}} by {{response_deadline}}, an invitation to ask questions with a named contact {{contact_name}}, and a warm sign-off. Keep it genuine and clear. </task> <constraints> - State the offer plainly; point to the attachment for legal detail rather than restating everything. - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Warm, specific, professional; no ambiguity about next steps or deadline. </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note what to keep in the email versus the attached formal letter. </format>

You are an internal-comms writer who crafts clear company-wide announcement emails. <context> I need a reusable internal company announcement email template as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - Company name: [COMPANY] - What's being announced: [NEWS / CHANGE / POLICY] - Why it matters to employees: [THE SO-WHAT] - What (if anything) employees must do: [ACTION OR NONE] - Where to ask questions: [CHANNEL / PERSON] </inputs> <task> Build the template with: one clear subject line stating the news, a preheader, a direct opener that leads with the announcement via {{announcement}}, a short "what this means for you" section, a clearly marked action-required block using {{required_action}} (or "no action needed"), a timeline or effective date via {{effective_date}}, a link or channel for questions {{questions_channel}}, and a sign-off from {{sender_name}}. Lead with the point, not the preamble. </task> <constraints> - The news goes in the first line; separate "what it means" from "what to do". - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Plain, honest copy; no burying the lede in mission-statement fluff. </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to adapt the tone for sensitive versus routine news. </format>

You are an HR-operations writer who crafts concise policy-update and reminder emails. <context> I need a reusable policy-update / reminder email template (e.g. PTO deadline, benefits enrollment, policy change) as a self-contained, ready-to-use artifact with subject options and merge placeholders. </context> <inputs> - Company name: [COMPANY] - Topic: [PTO DEADLINE / OPEN ENROLLMENT / POLICY CHANGE] - The key change or deadline: [WHAT AND WHEN] - What employees need to do: [SPECIFIC ACTION] - Where to go or ask: [PORTAL / HR CONTACT] </inputs> <task> Build the template with: one subject line naming the topic and any deadline, a preheader, an opener using {{first_name}} that states the update or reminder via {{policy_topic}}, a one-line summary of what changed or is due by {{deadline}}, a clearly bulleted "what you need to do" list with the action via {{required_action}}, a link to the portal or form {{action_url}}, a contact for questions {{hr_contact}}, and a brief sign-off. Keep it skimmable and action-oriented. </task> <constraints> - Deadline and required action must be unmissable; keep it under a screen. - Consistent {{snake_case}} merge tags listed at the end; plain-text friendly. - Concise and specific; no dense policy prose in the email body. </constraints> <format> Return the full template as a code block artifact, then list the merge fields and note how to reuse it as a final "deadline is tomorrow" reminder. </format>