Plan a Lifecycle Email Sequence: Welcome, Activation and Win-back
Write distinct messages, define entry and exit events, simulate consent and suppression, then review HTML, text and EML drafts before a provider handoff. No email is sent by the skill.
Fastest way
Ask your AI to do it
Paste this into the AI agent you already use:
Use Email Lifecycle Studio to prepare an authored welcome, activation or win-back sequence. Confirm actual product facts, entry and exit events, then simulate consent, suppression and completion at message time. Inspect HTML, text and EML drafts, preserve separate provider checks and send no mail.
What does a lifecycle email skill produce?
Email Lifecycle Studio v1.0.0 turns authored welcome, activation and win-back plans into responsive HTML, plain-text and multipart EML drafts, plus a local routing simulation and provider handoff. Python 3.10+ standard-library tools run offline without an API key. They do not connect to a provider, schedule delivery or send mail.
Give each message a useful job and a stop condition
- Start with the actual product, audience, entry event, success event and one primary CTA per message. Write distinct subject alternatives and complementary preview text. Do not invent recipient stories, discounts, urgency or achieved conversion.
- Read references/input.md. Supply 2–12 messages per sequence with elapsed-hour delays, required/excluded events and HTTPS CTA/preference links. Enter 1–20 fictional profiles to exercise consent, suppression, missing entry and goal completion.
- Treat fixture consent as test input, not a send authorization. The simulation fixes consent and suppression for the whole fixture, uses the first entry event and does not model timezone scheduling or business-day delivery.
Compare three complete practice journeys
After installing the package and reviewing its instructions, run from the package folder. This creates a workspace from the three included fictional plans; each journey retains its own editable input, email files and simulation. Use a new output directory for every generation.
Review Email Lifecycle Studio setup and examples
python3 scripts/build-workspace.py --input examples/activation.json --input examples/welcome.json --input examples/winback.json --output ./practice-email
python3 -m http.server 5373 --bind 127.0.0.1 --directory ./practice-emailReview the routing decisions and actual message files
Open http://127.0.0.1:5373/ and switch journeys, messages, Desktop/Phone and subject variants. Stop the local server with Ctrl+C when done. Browser switching previews an alternative subject; exported EML still uses subject A until you edit the plan and regenerate.
Inspect the current example output → — Compare the visible result with the exported files and checks described in this section.
| Fixture state | Expected decision | Evidence to inspect |
|---|---|---|
| No consent or suppressed | Skip, even when behavior matches | Per-profile decision in simulation.json |
| Entry event absent | Do not enter the journey | Recorded entry time and reason |
| Goal occurs at or before the scheduled message | Skip that message and later reminders | Event times, elapsed delay and simulation.csv |
| Conditions match without an exit | Eligible draft only | HTML/text/EML content and actual CTA |
What remains before real email delivery?
Compare the downloaded HTML, plain text and EML with the authored plan, including preview text, unsubscribe destination and campaign UTM values. EML deliberately contains no sender or recipient headers. A browser preview cannot establish Gmail/Outlook rendering, domain authentication, inbox placement or delivery.
Read handoff.md. A provider integration must reapply current consent, suppression, deduplication, recipient-local timing and exit checks at send time. Coordinate with other campaigns and test the actual provider separately when authorized. Preserve drafts until those checks pass.