Most AI-written emails fail on the same two things: they run long and they bury the ask. Left to its defaults, a chatbot pads the opener, pads the close, and the actual request ends up in paragraph three where a busy reader never reaches it. The 12 prompts below cap word counts hard, force one ask per email, and replace “let me know your thoughts” with a specific next step tied to a date.
Length is not a style preference; it is measurable. In cold outreach, the sweet spot is roughly 50–125 words, where reply rates peak around 8%, while emails over 200 words drop to about 3.9% (as of June 2026, per Overloop’s outreach length study). The same instinct toward brevity helps internal mail, where the reader is scanning for a verb and a deadline. When one email needs to land differently for two audiences, pair these with the tone rewrite prompts.
TL;DR
- Cap every email at a hard word count in the prompt; the model obeys a number far better than “keep it short.”
- One email, one ask. The reader picks the easiest request or none.
- Replace soft closes (“let me know”) with a yes/no question and a date.
- For cold outreach, lead with one specific, verifiable reason you picked this person; generic templates sit under 1% reply, personalized ones reach 15–18%.
- Follow-ups are not optional. The first follow-up alone can lift replies by 22–66%, and roughly 55–65% of all replies arrive after the first send.
Which model to run these on
Any current chat model handles these well because the task is short and structured. As of June 2026:
- ChatGPT (Free $0 with GPT-5.5, Plus $20): strong at matching a word cap and a numbered structure. The free tier is enough for occasional drafting.
- Claude (Free, Pro $20): Sonnet 4.6 tends to write warmer, less corporate prose, which suits apologies, intros, and thank-you notes. See ChatGPT vs Claude vs Gemini.
- Gemini 3.1 Pro (Google AI Pro $19.99): convenient if you draft inside Gmail and Workspace.
The prompts use [value] placeholders. Replace each bracketed item with your own detail before sending.
Best for
- Internal status and decision emails
- Cold outreach at low volume
- Follow-ups and re-engagement
- Apologies, intros, thank-you notes, and polite declines
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 full workflow behind cold outreach at volume — sourcing signal data, batching sends, and sequencing follow-ups — see AI cold outreach that gets a 15% reply rate.
Write a cold email to [name, role] at [company]. The specific reason I picked them: [reason]. My one ask: [15-min ask]. Max 120 words. No "I came across your profile" and no "Hope this finds you well."3. Follow-up after no response
Write a follow-up to [name] (no response after 4 days). Goal: re-state the ask without guilt-tripping. Add 1 new useful nugget (a relevant link or 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 actually 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. Include: what is changing, why, when, what they need to do, and 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 grovelling. Include: what happened, what I am doing about it, and 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. Include 1 specific reason I am 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 of context, 3 numbered options with one-line pros/cons each, my recommendation plus 1 reason, and a deadline. Max 200 words.9. Intro email between two people
Write an intro email connecting [person A] and [person B]. Voice: warm but brief. Include: why each will benefit, 1 specific overlap, and a "take it from here" handoff. 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 actually mattered. End with a small return-offer if relevant. Max 80 words.11. Subject-line generator with one specific verb
For an 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". Keep each under 50 characters so it survives a mobile inbox. Mark which match urgent vs FYI tone and which are safe for cold vs internal use.Keep subject lines short on purpose: 4–7 words (roughly 30–50 characters) lands the highest open rates, and the most important words should sit in the first 33 characters because that is all most phones display.
12. Reply-rate audit of a draft
Below is my email draft: [paste draft]. 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 every flagged issue.Word-count cheat sheet
Hand the model a number, not an adjective. These caps reflect where replies and opens hold up best as of June 2026.
| Email type | Hard cap | Why |
|---|---|---|
| Cold outreach | 120 words | 50–125 words peaks around 8% reply; over 200 words falls to ~3.9% |
| Follow-up | 80 words | The reader already has context; restate the ask and add one nugget |
| Internal status | 150 words | Headline + done/doing/blocked + one ask fits comfortably |
| Decision ask | 200 words | Options and trade-offs need room, but not a wall of text |
| Apology / intro / thank-you | 80–120 words | Short reads as sincere; long reads as defensive |
| Subject line | 30–50 chars | 4–7 words wins on opens; first 33 chars show on mobile |
Common mistakes
- Over 250 words for routine mail. Past the cap, every extra paragraph shaves reply rate; the reader skims and bails.
- More than one ask. Faced with two requests, the reader does the easy one or neither.
- Closing with “let me know your thoughts.” It invites silence. Replace it with a specific yes/no question and a date.
- A generic opener (“Hope you’re well”). That first line gets the most attention; do not spend it on filler.
- Burying the CTA in paragraph three. Busy readers see line one and the last line. Put the ask where the eyes land.
- No deadline. Open-ended requests drift to the bottom of the inbox and never resurface.
- Skipping the follow-up. Most replies arrive after the first send, so a one-and-done cold email leaves the majority of responses on the table.
FAQ
How long should a cold email actually be? Aim for 50–125 words, with a hard cap of 120 in the prompt. That band peaks around an 8% reply rate; emails over 200 words drop to roughly 3.9% (as of June 2026). Under 50 words can read as a templated blast, so keep one specific, human reason in there.
Does AI-written email hurt my reply rate? Not if you personalize it. The penalty comes from sending the same generic body to everyone. Generic cold emails reply under 1%, while emails with real personalization beyond the first name reach 15–18%. Use the model for structure and tightening, then drop in one verifiable detail only you would know.
How many follow-ups should I send? Three to five touches over 10–14 days is the practical range. The first follow-up does the heavy lifting (it can lift replies by 22–66%), and 55–65% of all replies land after the initial send. Send the first follow-up 3–4 days out; waiting past 5 days measurably lowers your odds.
Why force a word count in the prompt instead of saying “keep it short”? Models hold to a number far more reliably than to a vague adjective. “Max 120 words” produces a consistent, scannable draft; “keep it short” produces something that is still too long about half the time.
Should the subject line and body be generated together? Generate them separately. Write the body first, then run prompt 11 against the finished email so the subject reflects the actual ask. A subject written before the body tends to promise something the email does not deliver.