Emails fail on length and CTA — AI’s default is to pad both sides until the actual ask is buried in paragraph 3 and the reader skims for the verb that never arrives. These prompts cap word counts hard, force one ask per email, and replace “let me know your thoughts” with a real next step. Length matters because every extra paragraph past 150 words drops reply rates measurably for cold outreach and internal status updates alike. Pair with the tone rewrite prompts when the same email needs to feel different to two different audiences.
Best for
- Work emails
- Cold outreach
- Follow-ups
- Async updates
1. Status update under 150 words
Write a status update email to {recipient} about {project}. Structure: 1-line headline (where we are), 3 bullets (done / doing / blocked), 1-line ask. Max 150 words total.2. Cold outreach with one specific reason
For the longer workflow behind cold outreach at volume — sourcing signal data, batching, and following up — see AI cold outreach that gets a 15% reply rate.
Write a cold email to {name, role} at {company}. The reason I picked them (specific): {reason}. My one ask: {15-min ask}. Max 120 words. No "I came across your profile."3. Follow-up after no response
Write a follow-up to {name} (no response after 5 days). Goal: re-state the ask without guilt-tripping. Add 1 new useful nugget (a relevant link / a small observation). Max 80 words.4. “No, but here’s what I can do” email
Write a polite no-email declining {request} from {name}. Voice: warm, brief, honest. Offer 1 alternative I can do. Max 100 words.5. Internal “heads up” before a decision
Write an internal email giving {team} a heads-up about {upcoming decision}. Voice: matter-of-fact, includes: what’s changing, why, when, what they need to do, who to ask questions. Max 200 words.6. Apology email that doesn’t over-apologize
Write an apology email to {recipient} for {mistake}. Voice: own it without grovel. Include: what happened, what I’m doing about it, what won’t happen again. Max 120 words.7. Re-engagement email
Write a re-engagement email to {name} (last contact 3 months ago). Voice: warm, no guilt, includes 1 specific reason I’m thinking of them now. Max 100 words.8. Async decision-ask email
Write an email asking {team} for a decision on {issue}. Structure: 1 sentence context, 3 numbered options with one-line pros/cons each, my recommendation + 1 reason, deadline. Max 200 words.9. Intro email between two people
Write an intro email connecting {A} and {B}. Voice: warm but brief. Include: why each will benefit, 1 specific overlap, "take it from here." Max 80 words.10. Thank-you email after a favor
Write a thank-you email to {name} for {favor}. Voice: specific, not generic. Name what they did that mattered. End with a small return-offer if relevant. Max 80 words.11. Subject-line generator with one specific verb
For email about "{topic}" to {recipient role}, write 8 subject-line candidates. Each must start with a specific verb (review, decide, approve, share, schedule) — not "quick question" or "checking in". Mark which match urgent vs FYI tone and which are safe for cold vs internal use.12. Reply-rate audit of a draft
Below is my email draft: {paste}. Audit for reply-rate killers: (a) word count over budget, (b) more than 1 ask, (c) buried CTA, (d) generic opener ("Hope you're well"), (e) closing that doesn't commit ("let me know"), (f) no specific reason to reply by a date. Output a tightened version that fixes all flagged issues.Common mistakes
- Long emails (>250 words for most uses) — every extra paragraph past 150 words drops reply rate
- Multiple asks in one email — the reader picks the easiest or none
- Closing with “let me know your thoughts” — invites silence; replace with a specific yes/no question by a date
- Generic opener (“Hope you’re well”) that wastes the most-attention line on filler
- CTA buried in paragraph 3 — busy readers skim line 1 and the last line, nothing in between
- No date or specific time-bound ask — open-ended requests drift to the bottom of the inbox