Onboarding: First-Time User Experience and Setup Clarity
starter-chat
Persona: pastor-new
Touchpoint: /onboard, /admin/[token] (first login)
Preconditions
- New church just completed signup and payment
- User logging in to admin dashboard for first time
Steps
| # | Action | Expected Result |
|---|---|---|
| 1 | Load admin dashboard after first signup | Dashboard loads. Not blank. Greeting with church name visible. |
| 2 | Check for onboarding wizard or tour | Optional guided tour available. Can skip or complete. Clear next steps. |
| 3 | Verify knowledge base is set up | FAQ section or default training available. AI has starter knowledge to work with. |
| 4 | Check for demo/test feature | Can test chatbot immediately. Sample conversation visible. Can try it out. |
| 5 | Verify documentation is linked | Help link present. Can access guides, tutorials, FAQ. Don't need to ask for help. |
| 6 | Check setup checklist | Visual checklist: Upload FAQ ☐, Configure name ☐, Test chatbot ☐. Clear path. |
| 7 | Verify quick-start config | Church name, service times, contact info prefilled or easy to add. Chatbot personality selectable. |
| 8 | Check support access | Can easily reach support or schedule call. Chat, email, or phone option visible. |
Known Failure Modes
- Dashboard blank or confusing — pastor doesn't know what to do
- No demo chatbot — can't verify product works
- Help docs missing — pastor gives up without trying
- Setup takes >10 mins — abandonment
References
- Playwright spec:
e2e (onboarding validation) - Code files:
Notes
Tests first-time user experience after signup. This is critical: users make go/no-go decision in first 5 minutes. Must see chatbot working, understand next steps, and not feel lost. Poor onboarding = immediate churn (7-day refund).