Context Slice Context Validation
Before generating onboarding content, validate you have the required context. Check 
Customer Success Context Profile first, then prompt for gaps.
| Content Type | Required | Nice to Have |
|---|---|---|
| Onboarding Plan | Segment, timeline, product complexity | Stakeholder names, integration list |
| Feedback Summary | Feedback source, time period | Segment filter, sample size |
| Best Practices | Industry, deal size | Specific questions, comparison companies |
Validation prompts by content type:
- Onboarding Plan: "What customer segment is this for? What's your typical onboarding timeline for this segment?"
- Feedback Summary: "What feedback are you summarizing—survey responses, call notes, or something else? What time period does it cover?"
- Best Practices: "What's your typical deal size and onboarding model? Any specific practices you want me to research?"
If the user provides partial context, generate with what you have and mark gaps with [TK: missing item]. For example: [TK: typical timeline for this segment].
Onboarding Plan Template
Required context:
- Customer type or segment (e.g., enterprise, mid-market, SMB)
- Product complexity (features to enable, integrations needed)
- Typical timeline (30/60/90 days or custom)
- Key stakeholders involved
Structure:
# Onboarding Plan: [Customer Type]
## Overview
- **Timeline:** [X weeks]
- **Goal:** [Primary success milestone]
- **Stakeholders:** [Roles involved on both sides]
## Week-by-Week Breakdown
| Week | Milestone | Tasks | Owner | Success Criteria |
|------|-----------|-------|-------|------------------|
| 1 | Kickoff & Setup | • Kickoff call with stakeholders | CSM | Kickoff complete, access granted |
| | | • Technical setup / integrations | Customer + Tech | System connected |
| | | • Define success metrics | CSM + Sponsor | Metrics documented |
| 2 | Core Configuration | • Configure primary use case | Customer | Core feature enabled |
| | | • Initial training session | CSM | Team trained |
| 3 | Adoption Push | • First value milestone check | CSM | [Metric] achieved |
| | | • Address blockers | CSM + Support | Issues resolved |
| 4 | Handoff & Expand | • Transition to steady-state | CSM | Handoff complete |
| | | • Identify expansion opportunities | CSM | Next phase scoped |
## Risks & Mitigations
- **Risk:** [Common risk for this segment]
- **Mitigation:** [Proactive action]
## Success Metrics
- [ ] [Primary adoption metric]
- [ ] [Secondary engagement metric]
- [ ] [Stakeholder satisfaction check]Rules:
- Keep milestones achievable—don't overload week 1
- Assign clear owners for every task
- Include at least one hard metric per phase
- Build in a "first value" moment early (week 2-3)
- End with clear handoff criteria
Onboarding Feedback Summary
Required context:
- Feedback source: survey responses, call notes, or direct quotes
- Customer segment (if analyzing by segment)
- Time period covered
Structure:
# Onboarding Feedback Summary
**Period:** [Date range] | **Segment:** [If applicable] | **Sample Size:** [N customers]
## Key Themes
### Wins
[2-3 sentences summarizing what customers loved about onboarding]
- "[Direct quote if available]"
- [Supporting data point]
### Blockers
[2-3 sentences on friction points or delays]
- "[Direct quote if available]"
- [Impact: how many customers affected]
### Suggestions
[2-3 sentences on improvement ideas from customers]
- "[Direct quote if available]"
- [Feasibility note if relevant]
## Recommended Actions
1. [Action tied to blocker or suggestion]
2. [Action tied to blocker or suggestion]
3. [Action to amplify wins]Rules:
- One paragraph per theme maximum—keep it scannable
- Include direct quotes when impactful
- Quantify where possible (X of Y customers mentioned...)
- End with actionable recommendations, not just observations
- If data is sparse, say so—don't over-extrapolate
Onboarding Best Practices Research
Required context:
- Company context: your industry, deal size, onboarding model
- Focus areas: specific questions or comparison points
Structure:
# High-Touch Onboarding Best Practices
## Research Focus
[1-2 sentences on what you're benchmarking and why]
## Key Findings
### 1. [Tactic Name]
**Used by:** [Company examples]
**How it works:** [2-3 sentences]
**Why it matters:** [Outcome or benefit]
**Source:** [Link or reference]
### 2. [Tactic Name]
**Used by:** [Company examples]
**How it works:** [2-3 sentences]
**Why it matters:** [Outcome or benefit]
**Source:** [Link or reference]
### 3. [Tactic Name]
**Used by:** [Company examples]
**How it works:** [2-3 sentences]
**Why it matters:** [Outcome or benefit]
**Source:** [Link or reference]
## Applicability to [Your Company]
- **Adopt:** [Tactic] because [reason]
- **Adapt:** [Tactic] with modification [detail]
- **Skip:** [Tactic] because [reason]Rules:
- Focus on companies with similar ACV or complexity
- Include concrete examples, not generic advice
- Always cite sources
- End with applicability assessment—research without action is noise