mailhyve
Guides·7 min·

ChatGPT email prompts that actually work

Why one-line prompts produce generic emails — and the five-input structure that gets a usable draft on the first try. Before-and-after examples included.

By The MailHyve Team

The most common ChatGPT email prompt is "write me a follow-up email". The most common result is a generic, fill-in-the-blanks template that you spend more time editing than you would have spent writing it from scratch. The fault isn't ChatGPT's — it's the prompt. Vague inputs produce safe, generic outputs.

This is the practical guide to writing ChatGPT email prompts that produce a usable draft on the first try. Five principles, with before-and-after examples, and the prompt structure that works across every modern LLM.

Why one-line ChatGPT prompts produce generic emails

Large language models are pattern matchers. When you give ChatGPT a vague prompt, it falls back to the safest, most average pattern it has seen. "Write a sales follow-up" matches thousands of bland sales-follow-up emails in the training data, so you get a bland one back.

The fix is specificity. The prompt that produces a usable email names the goal, the relationship, the context, the desired outcome, and the constraints. Each of those inputs narrows the pattern space the model is matching against, which shifts the output away from generic averages toward something fitted to your actual situation.

The five inputs every email prompt needs

The prompt structure that consistently produces usable email output across ChatGPT, Claude, and Gemini has five components:

1. Purpose / goal

Name the specific email type. Cold outreach is different from sales follow-up is different from customer support reply is different from rejection. Each has a different shape: a different opener, a different middle, a different close. Be specific about which one you're writing.

2. Sender context

Who you are, where you work, what your role is. The LLM uses this to match the voice and register of the email to the sender. "Alex, head of growth at a Series-B B2B SaaS" produces a different email than "Alex, founder of a two-person consultancy".

3. Recipient context

Who is receiving the email and what your relationship is. A cold email to a VP at a Fortune 500 reads differently than a follow-up to a friend-of-a-friend. Name the recipient's role, the relationship history, and any context the LLM should preserve (e.g., "we met briefly at SaaStr last month").

4. Desired outcome

What you specifically want the email to achieve. "Get them to agree to a 15-minute intro call" is a different prompt than "Share a piece of research with no ask attached". The outcome shapes everything from the email's structure to its call to action.

5. Constraints

The optional but high-leverage field. Include any rules you want the LLM to enforce: no emoji, include a calendar link placeholder, keep it under 80 words, don't reference the previous email, write in British English. Each constraint narrows the output toward what you actually want.

Before and after: a cold outreach email

Bad prompt:

Write a cold email to a VP of Marketing about our product.

What you get: A four-paragraph email opening with "I hope this email finds you well," a generic description of "our innovative solution," and a request for a 30-minute call. Unusable as-is, would require a full rewrite.

Better prompt:

Write a cold email in English with these specifications:

PURPOSE: Open a conversation with a specific observation about the recipient. State the value-prop in one line. Close with a low-friction ask — a yes/no question or a short call.

TONE: Professional but human. No exclamation marks. No "hope this finds you well."

LENGTH: 80–100 words. Two paragraphs maximum.

SENDER: Alex, head of growth at Northwind (a B2B SaaS that helps marketing teams automate campaign reporting).

RECIPIENT: VP of Marketing at a Series-B SaaS company. We haven't spoken before.

OUTCOME: Get them to agree to a 15-minute intro call next week.

CONSTRAINTS: Don't use the phrase "quick question." Include a placeholder for a calendar link.

OUTPUT FORMAT: Return only the email — subject on the first line prefixed with "Subject:", blank line, body. No commentary.

What you get: A targeted cold email with a specific opener, a clear value-prop, an 80-word body, and a single actionable ask. Usable with one or two edits.

Tone is the single hardest input to get right

Without explicit tone guidance, ChatGPT defaults to a corporate-friendly register: polite, slightly formal, no personality. For most professional email this is fine; for cold outreach, customer support, or internal team email it's flat.

The trick is to be specific about what tone means. "Casual" on its own is ambiguous. "Conversational. Write like you'd talk. Short sentences. Skip the corporate scaffolding." tells the model exactly what to do.

Useful tone specifications:

  • Professional: Polished and competent. No slang, no exclamation marks, no overly casual openers.
  • Friendly: Warm and human. Contractions are fine. One light personal touch is welcome but not required.
  • Persuasive: Confident and benefit-led. Lead with what the recipient gets. Avoid hedging language like "just wondering" or "sorry to bother."
  • Concise: Strip every line that doesn't earn its place. Two sentences over three. Skip pleasantries.

Length enforcement actually works

ChatGPT and other LLMs default to medium-length output (roughly 180–250 words) almost regardless of context. That's often too long for cold outreach (where 80 words is the sweet spot) and too short for support replies with technical detail (which might need 300+ words).

Explicit word-count ranges in the prompt are respected reliably. "60–90 words. Two short paragraphs maximum." produces a noticeably tighter email than no length spec. "200–300 words with three sections." produces a meatier one when the context calls for it.

The output format spec

End every email prompt with an explicit output format. Without it, ChatGPT often returns the email wrapped in commentary ("Sure, here's a cold email…") or offers three alternatives. Both waste your time and clipboard.

The simple instruction that works:

OUTPUT FORMAT: Return only the email — subject line on the first line prefixed with "Subject:", blank line, then the body. Do not include commentary, alternatives, or explanation.

The tool

Building these prompts manually every time is a real time cost. Our ChatGPT email prompt generator wraps the structure into a four-field form: sender context, recipient context, desired outcome, optional constraints. Pick a goal, tone, and length. Copy the prompt or click "Open in ChatGPT" to launch the chat with the prompt pre-filled.

The prompt structure works on any modern LLM — ChatGPT, Claude, Gemini, Llama, Mistral. The structure is model-agnostic. What changes is the quality of the output; the prompt that gets you a usable email from ChatGPT will get you a usable email from any of them.

The pattern that works in practice: generate the email, read it once, replace the two or three sentences that don't feel right, send. Two to three minutes for a draft that takes 15 minutes to write by hand.

Keep reading