Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.narrativebanking.com/llms.txt

Use this file to discover all available pages before exploring further.

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. For provider-specific connection flows, use Integrations guide.

​
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.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.
The current onboarding sequence has 10 user-visible steps:
  1. Connect bank
  2. Business name
  3. Public info consent
  4. Website or social page
  5. Country
  6. Role
  7. Industry
  8. Sales channel
  9. Primary goal
  10. Biggest constraint
A small Step X of 10 counter is shown in the onboarding header so users can see progress without leaving the chat flow.

​
Current user flow

1

1. Connect bank

Users must accept the disclaimer and complete the bank connection before onboarding can continue.
2

2. Business context collection

The flow then collects business name, public-information consent, website, country, role, industry, sales channel, primary goal, and biggest constraint.
3

3. Setting up

After the final onboarding answer, the SDK shows a dedicated setup screen while downstream processing completes.
4

4. Product access unlocks after processing

Coach, Money, and Growth remain blocked until onboarding processing succeeds.

​
Input behaviour by step

StepInput patternExpected behaviour
Connect bankButton onlyNo text composer is shown.
Business nameFree textPlaceholder: e.g. Acme Trading Ltd
Public info consentButtons onlyUse public info is the primary action and Not now is the ghost action.
Website or social pageFree text + SkipPlaceholder: e.g. https://yoursite.com
CountryChips + free textPlaceholder: Or type your country
RoleChips + free textPlaceholder: Or type your role
IndustryChips + free textPlaceholder: Or type your industry
Sales channelChips + free textPlaceholder: Or type how you sell
Primary goalChips + free textPlaceholder: Or type your goal
Biggest constraintChips + free textPlaceholder: 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 intentionally skips a conversational acknowledgement and moves straight to the next question.
  • Industry, goal, and constraint acknowledgements are generated in a short natural sentence rather than with rigid string interpolation.
  • The website step includes an explicit Skip option.
  • 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. Depending on the user’s answers and available sources, this can include the business name, public business information, website or social context, country, role, industry, sales channel, primary goal, and biggest constraint. 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.

​
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 setting up your insights
  • 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: This is taking longer than expected
  • The support contact is shown as plain text: support@narrativebanking.com
  • The message references onboarding_processing for troubleshooting context

​
Implementation notes for integrators

  • 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.