Build a 5-email onboarding sequence that fires on activation events, not calendar days. Customize copy, timing, and CTAs for each milestone from signup through feature adoption.
Generate a 5-email onboarding sequence for {{product_name}} triggered by user activation events, not time delays. Each email should target a specific milestone and include:
1. **Trigger & Timing**: What user action fires this email? How long after the previous milestone?
2. **Subject Line**: One-liner that works on mobile. No hype.
3. **Body Copy**: 150–200 words. One job per email.
4. **CTA**: Primary action only. Link text should match the next milestone.
5. **Fallback Logic**: What happens if the user skips this milestone for 7+ days?
Context:
- Product category: {{product_category}}
- Primary user persona: {{user_persona}}
- Biggest activation blocker: {{activation_blocker}}
- Feature that signals "aha moment": {{aha_feature}}
- Typical time-to-value: {{time_to_value}}
Sequence milestones:
1. **Signup → First Login**: Reduce setup friction. Confirm they're in the right place.
2. **First Login → First Action**: Show the fastest path to the aha moment.
3. **First Action → First Collaboration/Share**: Unlock social proof or team value.
4. **Collaboration → First Integration**: Expand use case. Show ecosystem.
5. **Integration → Feature Unlock**: Celebrate progress. Introduce advanced features.
For each email, include:
- Trigger condition (e.g., "user created first project AND opened it within 24h")
- Send delay (e.g., "2 hours after trigger")
- Approval gate (e.g., "pause if user already completed milestone 3")
- Failure mode (e.g., "if user doesn't open, resend variant in 3 days")
Tone: Direct, specific, zero fluff. Assume the user is busy and skeptical.1. Fill in the {{placeholders}} with your product details. Be specific about the activation blocker—"users don't understand the value" is too vague; "users create a project but don't invite teammates" is actionable. 2. Run the prompt and get back 5 emails with triggers and timing. 3. Map each trigger to your actual product events (Segment, Amplitude, or your analytics tool). 4. Set up the sequence in your email platform (Klaviyo, HubSpot, Iterable). Use conditional logic to pause emails if the user has already completed that milestone. 5. Test with a small cohort (50–100 users). Measure open rate, CTA click rate, and time-to-next-milestone. 6. Iterate: if email 2 has <30% open rate, the trigger is wrong or the subject line is too generic. If email 3 CTA gets clicks but users don't complete the action, the copy is overselling.
Product: Notion for teams. Category: Productivity/Collaboration. Persona: Product manager, 30–45, manages 5–15 people. Activation blocker: Users create a workspace but don't invite teammates—they think it's a personal note-taking tool. Aha feature: Shared database with real-time collaboration. Time-to-value: 3–5 days (when first team member joins and edits a shared doc).
**Email 1: Signup → First Login**
Trigger: User completed signup AND opened workspace within 24h
Delay: Immediate (within 1h of first login)
Subject: Your workspace is ready. Here's what's next.
Body: Welcome to Notion. You've got a blank canvas. The fastest way to see the value: create one shared database, invite one teammate, and watch them edit it live. That's when Notion stops being a note-taking app and becomes your team's operating system. We've set up a template to get you there in 5 minutes.
CTA: Start with a template
Approval gate: Skip if user has already invited a teammate
Failure mode: If unopened after 24h, send variant with subject "3 things your team can do in Notion" at 48h
**Email 2: First Login → First Action**
Trigger: User opened workspace AND created first page/database
Delay: 2 hours after trigger
Subject: You just built something. Now share it.
Body: You created {{page_type}}. Good start. Here's the thing: Notion becomes powerful when your team uses it together. One shared database beats five separate spreadsheets. Invite your team now—they'll see updates in real-time, and you'll actually know who's doing what. Takes 30 seconds.
CTA: Invite your team
Approval gate: Skip if user has already sent invites
Failure mode: If CTA not clicked after 24h, send variant with social proof ("Teams using Notion save 5 hours/week on status updates") at 48h
**Email 3: First Action → First Collaboration**
Trigger: User invited at least one teammate AND that teammate accepted invite
Delay: 1 hour after teammate acceptance
Subject: {{teammate_name}} just joined. You're live.
Body: Your first collaborator is in. This is the moment Notion clicks. You can now see {{teammate_name}} editing in real-time, leave comments, assign tasks, and build a single source of truth for your team. No more Slack threads about what's actually due. Try editing a shared doc together right now—notice the live cursor.
CTA: Start collaborating
Approval gate: Skip if user has already collaborated (left comment, assigned task, etc.)
Failure mode: If CTA not clicked after 48h, send variant with video (30-sec demo of real-time collab) at 72h
**Email 4: Collaboration → First Integration**
Trigger: User collaborated on shared page AND completed 3+ edits
Delay: 24 hours after 3rd edit
Subject: Connect Notion to your other tools.
Body: You're using Notion as your team's hub. Now connect it to Slack, Google Calendar, or Zapier so information flows automatically. Stop copy-pasting between tools. One integration takes 2 minutes and saves your team hours every week.
CTA: Browse integrations
Approval gate: Skip if user has already enabled an integration
Failure mode: If CTA not clicked after 48h, send variant with specific integration recommendation ("Slack + Notion = no more missed updates") at 72h
**Email 5: Integration → Feature Unlock**
Trigger: User enabled first integration OR completed 10+ collaborative edits
Delay: 24 hours after trigger
Subject: You've unlocked advanced features.
Body: You're now using Notion like a pro team. Time to level up: automations, advanced permissions, and custom templates. These features are built for teams that have moved past the basics. You're there. Explore what's next.
CTA: See advanced features
Approval gate: None (this is the final email in the sequence)
Failure mode: If CTA not clicked after 72h, move user to monthly digest or nurture sequence