Onboarding Email Sequence Audit and Rewrite Around One Activation Event

Audits an existing or planned onboarding email flow, then rewrites it around a single activation event with segmentation, timing, copy, and a measurement plan.

You get: Audit table, flow logic and email copy blocks

More like this

The prompt

onboarding-email-sequence-audit-and-rewrite-around-one-activation-event.md
Role: You are a lifecycle marketing lead who designs onboarding email programs for {product}.

Context: {brand} wants new users of {product} to reach the activation event: {activation_event}. The audience is {audience}. The job to be done is to decide which emails to keep, rewrite, add, or cut so more new users reach activation. Current emails (if any): {current_emails}.

Task: Audit the current flow or the brief, then produce a rewritten sequence with copy, timing, segmentation, and a measurement plan.

Inputs (ask for anything missing first; list assumptions separately if I tell you to proceed):
- Activation event definition and typical time to reach it: {activation_event}
- Signup sources and user segments: {segments}
- Current emails or a description of them: {current_emails}
- Brand voice: {brand_voice}
- Sending constraints (frequency caps, legal requirements, ESP features): {send_constraints}
- Known drop-off points or support questions: {dropoff_notes}

Constraints:
- One primary call to action per email.
- Triggered by behavior where possible, not only by days since signup.
- No fake urgency, invented statistics, or promised outcomes.
- Include unsubscribe and consent considerations as a checklist item; do not give legal advice.

Workflow:
1. Summarize the goal, segments, and constraints. List assumptions and missing information.
2. Audit each existing email (Email | Purpose | Problem | Keep, Rewrite, or Cut). If none exist, map the user journey from signup to activation instead.
3. Define the trigger logic: entry criteria, exit criteria (stops when activated), and branches per segment.
4. Write each email: subject line (plus one alternative), preview text, body copy under 150 words, and one CTA.
5. Add a timing table with delays and behavior triggers.
6. Define the measurement plan: primary metric (activation rate), secondary metrics (click rate, unsubscribe rate), and a first A/B test with a hypothesis.

Output format:
1. Assumptions and missing information
2. Audit table
3. Flow logic (triggers, branches, exits)
4. Email copy blocks (numbered)
5. Timing and segmentation table
6. Measurement plan and first test
7. Risks and next actions (owner role, task, timing)

Acceptance criteria:
- Every email maps to one step toward {activation_event}.
- The sequence stops for users who have already activated.
- Copy matches {brand_voice} and stays within the word limit.
- The measurement plan names metrics and a testable hypothesis.

Quality checks before you answer:
- Is there exactly one CTA per email?
- Do the segments receive meaningfully different content, or is the branching unnecessary?
- Are risks such as deliverability, over-sending, and unclear triggers addressed?

Tool notes: In ChatGPT or Claude, paste existing emails inside labeled blocks. Use Markdown tables and keep copy blocks easy to paste into an ESP such as HubSpot, Klaviyo, or Customer.io. Do not assume ESP features I have not mentioned.

Example output

AI-written example

1. Assumptions and missing information

  • Brand: Tallyfold (invoicing app for freelancers). Activation = first invoice sent within 7 days; typical time is 2 days.
  • Segments: A) imported contacts from a spreadsheet, B) started from scratch.
  • Assumed: the ESP supports event triggers and branching. No open-rate baseline is available.
  • Constraints: max 1 email/day, 4 emails total, footer unsubscribe link.

2. Audit table

EmailPurposeProblemVerdict
Welcome (Day 0)GreetFour CTAsRewrite
Feature tour (Day 2)Show featuresNot behavior-basedCut
Upgrade (Day 5)Sell paid planPremature; reaches activated usersCut

3. Flow logic

  • Entry: account created. Exit: invoice_sent, or day 10.
  • Branch on client_added: A starts at Email 2 (client exists), B starts at Email 1.
  • Skip any email if the user already completed its step.

4. Email copy

Email 1 (B, welcome)
Subject: Send your first invoice in 3 minutes (Alt: Your Tallyfold account is ready)
Preview: Start with one client.
Body: Hi {first_name}, no setup marathon needed. Add one client and you can invoice them today. Everything else can wait.
CTA: Add your first client

Email 2 (client added, no invoice, +24h)
Subject: {client_name} is ready to be invoiced (Alt: One step left)
Preview: Your first invoice is a template away.
Body: You've added {client_name}. Pick a template, enter the amount, and send. You can edit it afterward.
CTA: Create invoice

Email 3 (invoice drafted, not sent, +24h)
Subject: Your draft is waiting (Alt: Finish your invoice)
Preview: It's saved exactly as you left it.
Body: Your draft for {client_name} is saved. If payment setup is the holdup, you can send now and add it later.
CTA: Review and send

Email 4 (no activity, day 5)
Subject: Stuck? Tell us where (Alt: Can we help with your first invoice?)
Preview: A real person reads replies.
Body: Many people pause before their first invoice. If something's unclear, reply with what's blocking you and we'll point you to the answer.
C

Generated from this prompt by AI. Your results will vary.

Tips and common edits

Works for SaaS, apps, and ecommerce accounts. Define the activation event precisely before running it, since vague definitions weaken the whole flow. Have legal or compliance review final copy and consent handling.

Questions about this prompt

More in Marketing

Turns pasted links and notes into a newsletter issue with a hooking intro, three takeaway sections, and one call to action.

90-Day Lifecycle Marketing Diagnostic and Experiment Roadmap for Onboarding and Retention

Diagnoses drop-off across the customer lifecycle from your funnel data and produces a prioritized 90-day plan of messages, triggers, and experiments with metrics so teams can decide where to invest first.

Above-the-Fold Landing Page Critique with 3 Headline, Subhead, and CTA Variants

Critiques landing page copy for clarity and conversion, then rewrites the headline, subhead, and CTA in three distinct variants.

Competitor and Audience Evidence Review with Citation Table and Go/No-Go Brief

A research workflow that plans online source discovery, scores evidence, builds a citation table, and ends with a decision brief, without pretending live browsing happened.

Competitor Homepage vs Your Positioning: Overlap, White Space, and a Sharper Line

Compares competitor homepage copy with your positioning to map overlap, find unclaimed angles, and propose one sharper differentiating line.

LinkedIn Post from a Work Lesson, No Engagement Bait

Turns a work story or lesson into a LinkedIn post with a strong first line, short paragraphs, and one clear takeaway.

Positioning Statement and Messaging Hierarchy for a Product Launch

Turns product facts, audience insight, and competitor context into a positioning statement, messaging hierarchy, and proof map so a team can approve one launch angle.

Repurpose One Article into 10 Native Posts Across Four Channels

Turns one blog post or article into 10 channel-native pieces for LinkedIn, X, Instagram carousel, and newsletter.

SEO-Friendly Etsy or Gumroad Listing with 13 Tags and FAQ

Produces a complete Etsy or Gumroad listing for a digital or handmade product, with title, 13 tags, description, and FAQ.

Process Transcript to Standard Operating Procedure

Converts a pasted process description or transcript into an SOP with purpose, roles, numbered steps, checklists and common mistakes.

Codebase Tour for a Specific Task

Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.

Trending

Developmental Edit Memo for an Essay Draft With Revise-or-Cut Decisions

Gives a draft essay a structured developmental edit: thesis check, paragraph-by-paragraph audit, and a prioritized revision plan so you can decide what to keep, rewrite, or cut before line editing.