wiki / Marketing / marketing-lifecycle-email-sequence-branching
advancedMarketingemail-marketingautomationlifecyclesegmentationab-testing

Design a five-email sequence with branch logic and a test plan

Builds a five-email nurture or onboarding sequence with send timing, one job per email, behavioral branch logic, and a real A/B variable per subject line.

The prompt — fill the [BRACKETS]0 copies
Design a five-email sequence for [SEQUENCE PURPOSE, E.G. TRIAL ONBOARDING, POST-PURCHASE, NURTURE AFTER A LEAD MAGNET]. Recipients enter when [TRIGGER EVENT]. The terminal conversion is [CONVERSION ACTION].

Inputs:
- Product or offer: [ONE PARAGRAPH]
- What recipients already know at entry: [WHAT THEY SIGNED UP FOR OR BOUGHT]
- Top reason people stall: [PRIMARY DROP-OFF REASON, OR "UNKNOWN"]
- Behavioral flags available in my email tool: [E.G. OPENED, CLICKED, VISITED PRICING, COMPLETED SETUP STEP]

Deliver, for each email:
1. Position and send timing (e.g. Email 2, day 3) with a one-line rationale for the gap.
2. The job of the email — the single belief or action it exists to move. If an email has no distinct job, cut it and state that the sequence should be four.
3. Two subject lines forming a genuine A/B test: they must differ on exactly one variable (length, specificity, question versus statement), and you must name the variable.
4. Preview text.
5. Body copy, 80-150 words, one CTA. Write like one person emailing another: no headers, no image slots, minimal formatting.
6. Branch logic: using only the behavioral flags listed, state who should skip this email or receive an alternate version, and write the alternate paragraph wherever the difference matters — typically emails 3 through 5.

Then add:
- A sequence-level map showing entry, branches, and exits; recipients who convert leave the sequence immediately.
- One metric per email that indicates whether it is doing its stated job.

Constraints: no fabricated customer stories, statistics, or urgency. Include a deadline only if [CONVERSION ACTION] carries a real one.
Open in Promptly Suggest an edit
Updated 2026-08-18 1 revision
Crafted with precision by MnexWeb