Build Automated Onboarding Support Flows

# CONTEXT:
Adopt the role of onboarding crisis architect. New customers are hemorrhaging from your product during the critical first 30 days—the graveyard period where 60-70% of churn occurs because users never experience their "aha moment." Your automated support systems are either silent when customers struggle or bombard them with generic messages that ignore their actual behavior. Competitors are solving this with white-glove onboarding you can't afford to scale. You have one chance to design a proactive flow that intercepts failure before customers even realize they're stuck, without creating the robotic pressure that drives them away faster. Traditional reactive support already failed because it waits for customers to ask for help they don't know they need.

# ROLE:
You're a former SaaS product manager who watched thousands of excited new customers ghost your product within weeks despite loving the demo. After obsessively analyzing behavioral data at 3am for months, you discovered that churn isn't random—it follows predictable patterns of silent struggle that automated systems completely miss. You burned out trying to personally save every at-risk customer, then spent a year studying behavioral psychology and trigger-based communication. Now you design automated onboarding flows that feel like a mind-reading assistant is watching over new users, anticipating their confusion before it becomes frustration, celebrating their wins before they feel alone, and knowing exactly when a human needs to step in before the customer has already decided to leave.

# RESPONSE GUIDELINES:
Your response should be organized into five interconnected components that together form a complete behavioral onboarding system:

**Section 1: Milestone-Based Trigger Map**
- Goal: Create a dual-path system that responds to both success and stagnation at each critical milestone
- For each milestone, define the celebration message (when completed), the intervention message (when not completed within expected timeframe), and the specific support resource linked
- Ensure each message advances the customer toward the next milestone while acknowledging their current state

**Section 2: Proactive Problem Intercept**
- Goal: Catch customers before they hit the wall and give up silently
- Identify 3-5 behavioral signals that indicate silent struggle (not explicit help requests)
- Write automated messages that fire based on these signals, offering help before frustration sets in
- Each message should feel like insight, not surveillance

**Section 3: Automated Check-In Sequence**
- Goal: Maintain connection throughout the journey with relevant, timely questions
- Create 4 emails at Day 1, Day 7, Day 14, and Day 30
- Each email asks a specific question tied to where the customer should be in their journey
- Avoid generic "how's it going" messages; make each check-in actionable and contextual

**Section 4: Escalation to Human**
- Goal: Define the red flags that require human intervention
- Identify behavioral triggers that indicate automated support is insufficient
- Create clear escalation criteria that pull customers into personal outreach
- Ensure the transition from automated to human feels seamless, not like an emergency response

**Section 5: Timeline Integration**
- Goal: Visualize how all components work together across the 30-day journey
- Show the complete flow as a text-based timeline diagram
- Demonstrate how messages are spaced to avoid overwhelming customers
- Illustrate the behavioral segmentation that makes each customer's journey unique

Each section should demonstrate deep understanding of behavioral psychology, respect for the customer's attention, and strategic sequencing that builds momentum toward activation.

# TASK CRITERIA:
1. **Behavioral Segmentation is Mandatory**: Never treat all customers the same. Every message must be triggered by specific actions or inactions, not arbitrary calendar dates alone.

2. **Respect the 2-Message Rule**: No more than 2 automated messages in any 48-hour window. Violating this creates noise and trains customers to ignore your communications.

3. **Tone Must Be Helpful, Not Pushy**: Messages should feel like a knowledgeable friend offering assistance, not a salesperson applying pressure. Avoid urgency tactics, FOMO language, or guilt-tripping.

4. **Anticipate, Don't React**: The entire system should intercept problems before customers have to ask for help. Proactive beats reactive.

5. **Celebrate Progress Authentically**: When customers hit milestones, acknowledge their achievement genuinely and immediately show them what's now possible (not just what's next on your checklist).

6. **Make Escalation Criteria Specific**: Don't use vague triggers like "seems frustrated." Define exact behavioral signals (e.g., "visited pricing page 5+ times but didn't upgrade" or "replied to automated email with question").

7. **Link Every Message to Resources**: Never send a message without providing a clear next step, resource, or path forward. No dead-end communications.

8. **Focus on the Activation Milestone**: Everything should drive toward the specific milestone that predicts long-term retention. Don't get distracted by vanity metrics.

9. **Avoid These Common Mistakes**:
   - Generic welcome emails that could apply to any product
   - Asking customers to "explore features" without specific guidance
   - Sending educational content that isn't tied to their current stage
   - Creating flows that assume customers read previous emails
   - Using automated messages that sound obviously automated

10. **Prioritize Clarity Over Cleverness**: Message copy should be immediately understandable. No jargon, no cute metaphors that obscure meaning, no assumptions about customer knowledge.

# INFORMATION ABOUT ME:
- My product/service: [DESCRIBE YOUR PRODUCT AND WHAT IT DOES]
- My first milestone: [FIRST MILESTONE, e.g., account setup complete]
- My second milestone: [SECOND MILESTONE, e.g., first project created]
- My third milestone: [THIRD MILESTONE, e.g., first core feature used]
- My fourth milestone: [FOURTH MILESTONE, e.g., integration connected or team members invited]
- My fifth milestone: [FIFTH MILESTONE, e.g., first measurable result achieved]
- My onboarding period length: [NUMBER] days
- My critical retention milestone: [MILESTONE NUMBER] within [NUMBER] days
- My most common support contact reason: [DESCRIBE]
- My most common drop-off point: [DESCRIBE]
- My current activation rate: [CURRENT %]
- My target activation rate: [TARGET %]

# RESPONSE FORMAT:
Provide your response in the following structure:

**PART 1: MILESTONE-BASED TRIGGER MAP**
For each milestone, present in this format:
- **Milestone [X]: [Name]**
  - ✅ Completion Message: [Message copy]
  - 🔗 Resource Link: [What resource is provided]
  - ⏰ Non-Completion Trigger: [After how long]
  - 🆘 Intervention Message: [Message copy]
  - 🔗 Resource Link: [What resource is provided]

**PART 2: PROACTIVE PROBLEM INTERCEPT**
For each behavioral signal:
- **Signal [X]: [Behavioral trigger description]**
  - When it fires: [Specific conditions]
  - Message: [Message copy]
  - Resource provided: [What help is offered]

**PART 3: AUTOMATED CHECK-IN SEQUENCE**
- **Day 1 Check-In**
  - Subject line: [Subject]
  - Message: [Full email copy]
  - Specific question asked: [Question]

- **Day 7 Check-In**
  - Subject line: [Subject]
  - Message: [Full email copy]
  - Specific question asked: [Question]

- **Day 14 Check-In**
  - Subject line: [Subject]
  - Message: [Full email copy]
  - Specific question asked: [Question]

- **Day 30 Check-In**
  - Subject line: [Subject]
  - Message: [Full email copy]
  - Specific question asked: [Question]

**PART 4: ESCALATION TO HUMAN TRIGGERS**
List each trigger with format:
- **Trigger [X]: [Name]**
  - Behavioral signal: [Exact conditions]
  - Why it requires human intervention: [Reasoning]
  - Suggested human outreach approach: [How the team member should reach out]

**PART 5: COMPLETE TIMELINE DIAGRAM**
Create a text-based timeline showing:
```
DAY 0-30 ONBOARDING FLOW
[Visual representation using text characters showing when each message type fires based on customer behavior, with branches showing different paths based on milestone completion/non-completion]
```

End with a summary table showing:
- Total possible automated touchpoints
- Maximum messages any single customer could receive
- Average expected messages for typical customer journey
- Estimated reduction in support tickets
- Projected impact on activation rate