Onboarding Journey

Sol Helps onboarding follows this order:

1. create assistant
2. add knowledge
3. test in chat
4. embed widget
5. optional branding

This sequence is intentional. It prioritizes answer quality and real signal over visual polish.

Where onboarding runs

• primary flow: Overview
• guided pages: Dashboard → Welcome routes for setup, knowledge, chat, and embed

Progress behavior

Your progress is tied to real workspace state, not only button clicks.

Examples:

• if an assistant exists, setup advances
• if docs exist, knowledge advances
• if conversations start, later steps unlock

Role behavior

• Owners/Admins can run onboarding and manage configuration.
• Members without required permissions will see explicit blocked-action messages.

Common onboarding blockers

1. No knowledge uploaded: answers remain weak and themes are low quality.
2. Widget not embedded: no real traffic means no meaningful insights.
3. Skipping test chat: teams discover basic answer issues too late.

Fast recovery checklist

1. Confirm an assistant exists.
2. Upload one high-quality source.
3. Run three realistic test questions.
4. Embed on one production page.
5. Re-check conversations within 24 hours.