Use this page when you need to understand the live onboarding flow that appears before Coach, Money, and Growth are available. For embedding and token setup, use SDK integration.
Overview
Narrative SDK uses a guided onboarding flow to collect the minimum business context needed before the full product experience becomes available.What’s new in v1.5.11
v1.5.11 keeps onboarding lightweight while moving required identity capture before onboarding starts.
- New users must provide business name, first name, and last name before they continue into onboarding.
- The onboarding questionnaire no longer asks for business name as a skippable profile question.
- Optional profile enrichment remains chips-first where available, free-text optional, and skippable.
- The first journey milestone can show account connection as complete when the user reaches the post-connection onboarding experience.
- Setup and first-visit flows remain tied to the existing
onboarding_processingcompletion path.
What’s new in v1.5.10
v1.5.10 strengthens the first visit after onboarding.
- The first visit now centres on a short welcome, a goal bridge, and two or three personalised cost quick-win cards.
- Users are guided towards a light first task: review the quick-win cards and mark which ones are worth pursuing.
- The setup screen better supports a leave-and-come-back pattern when processing takes time.
- Public business information remains optional enrichment and should not block onboarding progress.
What’s new in v1.5.9
v1.5.9 clarifies the current bank connection limits and improves onboarding reliability.
- Users are guided to connect their main business bank account during the first onboarding step.
- Settings keeps the bank connect action available when no bank account is connected.
- Once a bank account is connected, Settings no longer presents an additional bank connection action.
- Settings now explains that multiple bank accounts and multi-currency support are coming later, and that current bank account support is for EUR single-currency accounts.
- The public company email follow-up after business-name entry is preserved for downstream personalisation.
- Website and social-link handling is more predictable, with clearer malformed-URL recovery and consistent optional skip behaviour.
- Onboarding prompts, chips, calls to action, and input controls remain visible and tappable on iPhone Safari and narrow viewports.
- Ambiguous country answers and off-topic sales-channel responses can trigger clarification instead of being silently accepted or skipped.
What’s new in v1.5.7
v1.5.7 makes onboarding clearer for users who are setting up the SDK for the first time.
- The website or social link step can be skipped when the user does not have a public page to share.
- Input placeholders are clearer, so users can understand what kind of answer is expected.
- Suggested chips behave more predictably between steps.
- The setup screen more clearly separates “you finished answering questions” from “the product is still preparing your insights”.
- Freshly generated Money data after onboarding is handled more reliably, so new users are less likely to see an empty or unavailable Money page immediately after setup.
- Business context is collected and reused more consistently, helping Coach, Money, and Growth produce more relevant content.
- Account creation
- Open Banking connection
- Processing
- First visit
Current user flow
1. Account creation
New users provide the required identity fields before onboarding starts: business name, first name, and last name. Existing users with stored identity data are not asked to re-enter it.
2. Connect bank
Users must accept the disclaimer and complete the bank connection before onboarding can continue. They should connect the main business bank account used for day-to-day business transactions.
3. Setting up
After optional profile enrichment completes or is skipped, the SDK shows a dedicated setup screen while downstream processing completes.
Input behaviour by step
| Step | Input pattern | Expected behaviour |
|---|---|---|
| Account creation | Required identity fields | Business name, first name, and last name are required before onboarding begins. |
| Connect bank | Button only | No text composer is shown. The page guides users to connect their main day-to-day business account. |
| Website or social page | Free text + Skip | Placeholder: Paste your website or social link |
| Public information reminder | Buttons only | If the user skips the website, the SDK may ask once whether to keep public-information enrichment on. |
| Country | Best-guess chip + chips + free text | The first chip uses partner or tenant context first, then website or business-registration signals, then a regional default. |
| Role | Chips + free text | Placeholder: Or type your role |
| Industry | Chips + free text | Placeholder: Or type your industry |
| Sales channel | Chips + free text | Placeholder: Or type how you sell |
| Primary goal | Chips + free text | Placeholder: Or type your goal |
| Biggest constraint | Chips + free text | Placeholder: Or type your constraint |
Interaction details
- Suggested chips are cleared as soon as the user answers a step.
- New chips appear only after the next question renders.
- The country step’s first chip should be the best available guess for the user.
- Industry, goal, and constraint acknowledgements are generated in a short natural sentence rather than with rigid string interpolation.
- The website step includes an explicit
Skipoption and a one-time public-information reminder when needed. - Contextual loading messages are shown per step instead of a generic
Saving your answer...message.
Business context
Onboarding is designed to gather enough context for the first generated outputs to feel relevant without blocking progress on optional profile questions. Required identity data comes from account creation. Depending on the user’s answers and available sources, optional enrichment can include public business information, website or social context, country, role, industry, sales channel, primary goal, and biggest constraint. Publicly available business information is used to improve context for insights, not as a consent-gated requirement. Users can turn it off from Settings in Business Profile or Privacy and Security. Turning it off stops further public-source processing; existing insights remain available. Users should not need technical knowledge to complete this flow. If they do not know an answer or do not have a public link, the product should keep them moving rather than blocking setup.Bank connection limits
Narrative currently supports one connected bank account for the onboarding and Settings flows. If a user has no connected bank account, Settings shows the bank connection action so they can connect one. If a user already has a connected bank account, Settings shows the account details and limitation messaging instead of offering another bank connection action. The current bank account support is for EUR single-currency accounts. Multi-account and multi-currency support are planned for a later release.Post-onboarding processing screen
After the final onboarding answer, Narrative SDK shows a dedicated setup state instead of opening the app immediately.Normal state
- Heading:
We're preparing your first briefing - Body copy explains that setup usually takes about 15 minutes
- Users are told they can close the tab and wait for the completion email
Delayed or failed state
If processing fails, is cancelled, or takes longer than expected, the setup screen switches to a delayed message.- Heading:
Setup is taking longer than expected - The support contact is shown as plain text:
support@narrativebanking.com - The message references
onboarding_processingfor troubleshooting context
Implementation notes for integrators
- Collect required business and user identity before expecting onboarding to proceed.
- Do not assume the app becomes available immediately after the last onboarding answer.
- Treat onboarding completion and onboarding processing completion as separate milestones.
- If you test integration flows manually, include at least one full onboarding run that reaches the setup screen.
- When documenting tenant support processes, account for the delayed-processing state and support email guidance.