Four Emails, Four Jobs: A Prompt That Keeps ChatGPT From Writing Template Sequences

TL;DR: AI email sequences sound generic because every email tries to do everything. Give each email one job, name the reader’s main objection, and add a few plain-language rules. The draft gets much more human.

Why most AI sequences fall flat

The usual request is “write me a 5-part welcome sequence.” ChatGPT has no idea who the reader is, what they doubt, or what each email should accomplish. So every message introduces the brand, hints at the offer, adds a benefit list, and ends with a vague nudge. Readers can feel that. Opens and replies drop. By email three, many people have already learned they can skip you, because they know exactly what is coming.

A Redditor in r/PromptEngineering shared a structured prompt that fixes this by giving the model three things up front: the offer, the reader, and the biggest objection. Think of it as a short creative brief. A human freelancer would refuse to start without one, and the model deserves the same courtesy.

The breakdown

  1. Context comes first. You state the product and its main outcome in one sentence, who is on the list and what problem they’re solving, and the number one reason they hesitate. That last piece is the most useful. It tells the model what the sequence is actually fighting against. A practical tip: pull the objection from real life. Check support replies, sales call notes, or the “why didn’t you buy” survey answers. “It’s too expensive” is usually a surface answer, so dig for the real one, like “I don’t have time to learn another tool.”
  2. Every email gets a distinct role.
    • Email 1: a relatable situation plus a simple mechanism for solving it
    • Email 2: a myth or mistake breakdown that challenges a common shortcut
    • Email 3: proof, through a specific example or scenario
    • Email 4: a direct offer that handles the objection, with a low-friction next step

    The roles work because they do not overlap. If email 2 starts pitching, you have lost the point of the structure. When a draft drifts, tell the model which email broke its role and ask for a rewrite of that one only.

  3. Constraints keep the voice human. Short, curiosity-driven subject lines with no clickbait emojis or all caps. No robotic AI phrases or corporate buzzwords. Short paragraphs and plain, conversational language. A good subject line example is “The mistake behind most slow mornings” rather than “Unlock Your Best Morning Routine Today.” If you have a list of words you hate seeing, such as “delve,” “unlock,” or “game-changer,” add them to the rules and the model will usually avoid them.
  4. You still edit. The author keeps the structure and rewrites the opening lines and examples so it sounds like one person writing to one reader. That’s the right split. The prompt builds the skeleton, and you add the voice. Read each email out loud before sending. If you stumble on a sentence, or it sounds like a brochure, rewrite it the way you would say it to a friend.

What the community added

The comments had good tweaks:

  • One person swapped the myth breakdown in email 2 for a “failed attempt” story. It felt less like a lecture and worked better with skeptical readers.
  • Another replaced the proof email with a before-and-after story: one line of struggle, one line of relief.
  • A third pointed out that the call to action is usually where the editing time goes. If the next step isn’t named, “low-friction” turns into a generic “learn more.”

That last point is worth taking seriously. Be specific in your prompt about what the reader should do, such as reply with one word, click a particular link, or book a 10-minute call. Replies also help deliverability, so a one-word reply ask can quietly improve how your later emails land in the inbox.

Use cases

  • Welcome sequences for a new newsletter list
  • Launch or pre-launch emails for a small product
  • Re-engagement emails for subscribers who went quiet
  • Short nurture sequences after a lead magnet download

Prompt of the Day 📧

Act as a direct-response email strategist and conversion copywriter.

Context:

  • Product / Offer: [what you sell and the main outcome in 1 sentence]
  • Target Reader: [who is on the list and what problem they are trying to solve]
  • Main Objection: [the #1 reason readers hesitate to buy or take action]

Task: Create a 4-email sequence where each email has a distinct role:

  1. Email 1 (Relatable Situation + Mechanism): Connect with a real problem and introduce a clear way to think about solving it.
  2. Email 2 (Myth / Mistake Breakdown): Challenge a common shortcut that wastes time or hurts results.
  3. Email 3 (Proof / Specific Example): Show a concrete scenario or breakdown of how the approach works in practice.
  4. Email 4 (Direct Offer + Low-Friction Next Step): Address the main objection clearly and invite action without hype.

Rules: Keep subject lines short, specific, and curiosity-driven (no clickbait emojis or all-caps). Avoid robotic AI phrases and corporate buzzwords. Use short paragraphs and plain, conversational language.

My suggested addition: name the exact next step you want in Email 4, so the call to action can’t turn vague.

Call to action

Run this on your next sequence and note where you end up editing the most: subject lines, transitions, or the call to action. That tells you which rule to tighten in the prompt next time. Keep a simple note of each change you make, because after two or three runs the pattern becomes obvious and you can bake it into the prompt. Share what you find with the crew, because your tweak might be the one that helps the next captain.

Frequently Asked Questions

Q: Should I swap the myth breakdown in email 2 for a failed attempt story?

One reader swapped the myth breakdown for a failed attempt story and found it felt more human and less like a lecture. That tends to work well with skeptical readers, who often tune out when they feel told what they’re doing wrong. Keep the story short and honest, then point to the approach that actually worked for you. If most of your list has already been burned by shortcuts, this swap is worth testing.

Q: Should email 3 be a proof example or a before-and-after story?

Some people keep a concrete example or breakdown here because it shows exactly how the approach works in practice. Others use a before-and-after story, one line of struggle and one line of relief, because it reads as more human than proof. Test whichever fits your readers and watch replies and clicks instead of guessing. Either way, keep the example specific enough that a reader can picture doing it themselves.

Q: How do I make the call to action in email 4 more specific?

The CTA usually needs the most work, because a low-friction ask can slide into a generic ‘learn more’ if the next step is never named. Spell out exactly what happens when they click or reply, like ‘reply with your biggest bottleneck’ or ‘grab the 10-minute checklist.’ Keep it to one action so the reader knows what to do next. Plain and specific beats clever here.

The structured prompt I use so ChatGPT writes email sequences that don’t sound like generic AI templates
by u/CreatorFlowH in PromptEngineering

Scroll to Top