Prompt Templates for Email Writing: 10 Use Cases with Examples

Email prompts fail when they say write a professional email and nothing else. The model guesses your audience, goal, and length — then produces something that sounds like every other AI email in the inbox.

These 10 templates use the RTF structure (Role, Task, Format) from our prompt engineering cluster. Fill brackets, paste into GPT-5.5, Claude Opus 4.8, or Gemini 3.5 Flash for daily email work.

Global rules for all templates: specify word limit, ban filler openers, require one clear CTA, and never let the model invent facts about the recipient.

Before vs after: why vague prompts fail

Weak prompt:

Write a professional cold email to a VP of Marketing about our analytics tool.

Typical output problems: 280 words, opens with I hope this email finds you well, claims we spoke at a conference you never attended, lists five features instead of one pain point, CTA buried in paragraph four.

Strong prompt (RTF):

ROLE: B2B sales writer for Acme Analytics.

TASK: Cold email to VP Marketing at mid-market SaaS about reducing attribution reporting time.

CONTEXT: Pain: manual spreadsheet merges every Monday. Proof: customers cut reporting from 6 hours to 45 minutes.

FORMAT: Under 120 words. Subject line + body. One question CTA.

TONE: Peer-to-peer, not vendor-begging.

CONSTRAINTS: Do not claim prior contact. Do not invent their company news.

Expected output shape: subject under 8 words, body opens with their pain in their language, one proof line, single question CTA — ready to personalize with one company-specific sentence.

Tone table: pick before you prompt

| Situation | Tone keyword | Avoid |

| Cold B2B outreach | Peer-to-peer, curious | Desperate, hyperbolic |

| Executive meeting request | Respectful, concise | Over-apologizing |

| Support reply | Empathetic, procedural | Blame-shifting, jargon |

| Apology email | Accountable, specific | Vague sorry, legal overreach |

| Internal update | Direct, status-first | Narrative fluff, no ask |

| Job application | Confident, specific | Resume repetition, generic praise |

Add TONE: [row from table] to every template. Models default to enthusiastic vendor voice without it.

Subject line variant prompt

After any template output, run:

Using the email below, generate 5 subject lines:

(1) outcome-led, (2) curiosity gap, (3) social proof, (4) question format, (5) ultra-short under 5 words.

Rules: no ALL CAPS, no fake RE: or FWD:, max 50 characters each, match body facts exactly.

GPT-5.5 excels at character-limit obedience. Claude Opus 4.8 produces more natural curiosity gaps. Gemini 3.5 Flash is fastest for bulk subject A/B sets from a recipient table.

1. Cold outreach (B2B)

ROLE: B2B sales writer for [your company].

TASK: Cold email to [title] at [industry] company about [offer].

CONTEXT: Pain point: [specific problem]. Our proof: [one metric or client type].

FORMAT: Under 120 words. Subject line + body. One question CTA.

TONE: Peer-to-peer, not vendor-begging.

CONSTRAINTS: Do not claim we spoke before. Do not invent their company news.

Example output description: Subject like Cut Monday reporting to 45 min? Body opens with manual attribution pain, cites one customer metric, asks if they still run weekly spreadsheet merges — no product name until sentence three.

2. Follow-up (no reply)

ROLE: Same thread continuity — follow-up number 2.

TASK: Follow up on email below. Assume busy, not ignoring.

CONTEXT: [paste original email]

FORMAT: Under 80 words. New angle: [one fresh value point]. Same CTA.

CONSTRAINTS: No guilt-tripping. No just bumping this up.

Example output description: Shorter than original, adds one new proof point or case study angle, references prior email in one clause without quoting it whole, ends with same single question.

3. Meeting request

ROLE: Executive assistant tone.

TASK: Request 30-min call about [topic] with [person/role].

FORMAT: 3 sentences + 2 time options. Subject line included.

TONE: Respectful of time. Specific agenda in one line.

Example output description: Subject states topic and duration. Body: why the call matters (one sentence), agenda bullet or inline list (3 items max), two timezone-aware time slots, no calendar link unless you provide one.

4. Customer support reply

ROLE: Tier-1 support for [product].

TASK: Reply to customer email below.

CONTEXT: [paste customer message]. Known issue: [yes/no — details].

FORMAT: Acknowledge problem. Steps numbered. Sign-off with help link.

CONSTRAINTS: Never promise refund unless policy allows.

Example output description: Opens by restating their issue in their words, numbered fix steps (2–5), expected resolution time if known issue, link to docs — no marketing upsell.

5. Support escalation internal

ROLE: Support agent writing internal escalation.

TASK: Summarize ticket for engineering.

CONTEXT: [customer thread paste]

FORMAT: BLUF issue. Steps to reproduce. Customer impact. Urgency P1-P3.

Under 150 words.

Example output description: First line is the bug in one sentence. Repro steps numbered. Impact: X users / revenue at risk. Urgency tag with one-line justification.

6. Sales proposal follow-up

ROLE: Account executive.

TASK: Post-demo follow-up to [name] at [company].

CONTEXT: Demo highlights: [3 bullets]. Their stated priority: [quote].

FORMAT: Under 150 words. Recap their goal. 3 bullet next steps. Soft CTA for timeline.

Example output description: Opens with their quoted priority, mirrors three demo moments they reacted to, proposes next steps with owner on each side, asks for decision timeline without pressure language.

7. Newsletter section

ROLE: Newsletter editor for [audience].

TASK: Write one section: [topic].

FORMAT: Headline 8 words max. 2 short paragraphs. One link CTA.

Word limit: 150.

Example output description: Punchy headline, 8 words max, first paragraph problem or news, second paragraph insight plus one link CTA — scannable, no wall of text.

8. Apology / service failure

ROLE: Customer success lead.

TASK: Apologize for [specific failure]. Offer [remedy].

FORMAT: Acknowledge. What happened. What we fixed. What we offer.

Under 200 words. No legal admissions beyond provided facts.

Example output description: Names the failure specifically, timeline of fix, concrete remedy (credit, extension, process change), no deflecting to third parties.

9. Internal project update

ROLE: Project lead updating stakeholders.

TASK: Weekly update for [project].

CONTEXT: Done, blocked, next week — [bullets each].

FORMAT: Status green/yellow/red. 3 sections with bullets. One ask if blocked.

Under 250 words.

Example output description: Status emoji or label first line, Done/Blocked/Next three sections with bullets, single bold ask if yellow or red — no narrative essay.

10. Job application cover email

ROLE: Candidate for [role] at [company].

TASK: Cover email referencing attached resume.

CONTEXT: Relevant win: [achievement with metric]. Why this company: [specific reason].

FORMAT: Under 180 words. No resume repetition.

Example output description: One hook achievement with number, one sentence on why this company specifically (not generic mission praise), clear ask to review resume — no bullet list of every job.

Worked example: support reply before/after

Weak:

Reply to this angry customer about slow exports.

Output: Generic apology, suggests clearing cache (not in docs), offers to escalate without ticket number, 220 words.

Strong (template 4 filled):

ROLE: Tier-1 support for DataPipe.

TASK: Reply to customer below.

CONTEXT: Customer says CSV export stuck at 90% for 2 hours. Known issue: yes — queue backlog since 14:00 UTC, ETA fix 18:00 UTC.

FORMAT: Acknowledge. Steps numbered. Sign-off with status page link.

CONSTRAINTS: No refund promise.

Output: Restates 90% stall, confirms known queue issue with ETA, gives workaround (smaller date range export), status page URL — 95 words.

Worked example: cold outreach before/after

Weak:

Write cold email for our project management software.

Output: 300 words, lists 12 features, subject RE: Quick question, fake personalization.

Strong (template 1 filled):

ROLE: B2B writer for FlowStack.

TASK: Cold email to Engineering Manager at 50–200 person fintech about sprint planning overhead.

CONTEXT: Pain: 2-hour planning meetings every sprint. Proof: Meridian Pay cut planning to 35 minutes.

FORMAT: Under 120 words. Subject + body. One question CTA.

TONE: Peer-to-peer.

CONSTRAINTS: No prior contact claim.

Output: Subject Still running 2-hour sprint planning? Body: one pain sentence, one proof, one question about their current retro length — 98 words.

Batch variant prompt

Generate 2 alternatives: (A) 30% shorter, (B) more direct CTA. Keep facts identical.

For campaigns: paste recipient table (name, company, pain note) into Gemini 3.5 Flash with template 1 — generate body per row, human review every send.

Extra template: referral introduction

ROLE: Professional introducer connecting two peers.

TASK: Double-opt-in intro email to [Person A] and [Person B].

CONTEXT: Why they should meet: [one sentence]. A's background: [one line]. B's background: [one line].

FORMAT: Under 100 words. Subject: Intro: [A] <> [B]. Separate paragraphs per person. No pressure CTA.

TONE: Warm, efficient.

Extra template: payment / invoice reminder

ROLE: Accounts receivable.

TASK: Polite overdue invoice reminder for invoice #[number], [days] past due.

FORMAT: Under 80 words. Amount, due date, payment link. Offer to resend invoice PDF.

TONE: Firm but courteous. No threats in first reminder.

CONSTRAINTS: Do not threaten legal action unless I specify escalation level 3.

Extra template: event invitation

ROLE: Community manager for [event/brand].

TASK: Invite [audience segment] to [event name] on [date].

CONTEXT: Value prop: [what they learn or get]. Speaker or hook: [one name or topic].

FORMAT: Subject + 3 short paragraphs. Register CTA link placeholder. Under 150 words.

TONE: Excited but not spammy. No fake personal relationship.

Personalization layer (add to any template)

Before sending, append:

Add one sentence after the opening that references [specific company news / LinkedIn post / mutual connection] — use ONLY this fact: [paste fact]. If fact is thin, skip personalization rather than invent.

Prevents hollow I saw your recent post with no post attached.

Common mistakes

No word limit → model writes essay-length emails

Missing TONE → every email sounds like a SaaS marketing blast

No CONSTRAINTS → model invents prior conversations or meetings

Asking for subject line after body without linking → subject-body mismatch

Pasting customer thread without ROLE → model replies as the customer

Bulk send without human fact-check → wrong names, wrong metrics

Using write professional as the only instruction → filler openers guaranteed

Model pick

GPT-5.5: word-limit obedience, subject line variants, strict CONSTRAINTS

Claude Opus 4.8: natural tone for sensitive emails, apologies, executive comms

Gemini 3.5 Flash: bulk variants from recipient table, fast first drafts

Gemini 3.1 Pro: long thread summarization before escalation email (template 5)

Route sensitive or high-stakes emails through Claude; route volume through Gemini Flash with human review.

Quality:length and structure cheat sheet

| Email type | Target words | Subject style |

| Cold B2B | 80–120 | Outcome or question |

| Follow-up | 60–80 | Same thread, new angle |

| Support | 100–150 | Re: [ticket topic] |

| Internal update | 150–250 | [Project] — [status] |

| Apology | 120–200 | We missed [specific thing] |

Always state target in FORMAT line — models treat explicit limits as hard constraints on GPT-5.5 and Claude.

PromptMake workflow

/text → pick template number → fill brackets → Improve tightens tone → you verify facts before send.

Save your filled stack context (company name, default tone, banned phrases) as a reusable snippet for repeat email types.

FAQ

Should I paste the full email thread or summarize?

Paste full thread for support and escalation (templates 4–5). Summarize only if over 3,000 words — then require the model to quote the customer's last message verbatim before replying.

How do I stop AI telltales?

Add CONSTRAINTS: Ban these openers: I hope this finds you well, I wanted to reach out, Just circling back. Ban em dashes in every sentence. No exclamation marks in cold email.

One CTA or multiple?

One. Multiple CTAs reduce reply rate. If you need calendar link and question, make the question the CTA and put link on one word in the sign-off.

Can I generate 50 cold emails at once?

Yes with Gemini 3.5 Flash and a CSV-style recipient list — but run CONSTRAINTS on every row and human-review names and company facts. Never auto-send without review.

Which model for non-English email?

Claude Opus 4.8 and GPT-5.5 both handle major business languages. Specify OUTPUT LANGUAGE: [lang] and TONE: [local business norm] explicitly.

Should the model write HTML or plain text?

Default plain text unless you specify FORMAT: HTML with single CTA button placeholder. Plain text prompts produce cleaner copy for you to paste into any ESP.

How do I match our brand voice?

Add 2–3 example emails we have sent before as STYLE REFERENCE — not for content, for sentence length and formality level. Or link to system prompt guide for global voice.

Related articles

RTF framework — structure behind these templates

System prompt for ChatGPT — global email voice

Marketing copy AIDA/PAS — longer persuasion frameworks

Positive framing — banned words as positive constraints

Bottom line

Email prompts need role, task, format, word limit, tone, and one CTA every time. Copy, fill brackets, ban filler — AI drafts, you verify facts, you send.