Technical integration
Embed Coach in your app, connect customer data and link it to your products and team. Your developers work with our SDK and integration guides.
Embed and sign in
Coach loads in a place you choose in your web app, such as the business account overview. Customers sign in to your app as usual. Your backend issues a short-lived signed token for that customer, and Narrative verifies it before starting a session limited to your institution and that customer, so there is no separate Narrative login.
- The signing secret stays on your backend. It is never sent to the browser or the app.
- Your app needs a place for Coach. A page or panel where Coach can render, and a backend route that issues sign-in tokens.
- Native mobile apps are scoped separately. Coach works in current browsers and common web frameworks, including React, Vue and Angular. For a native app, we scope the approach with your team before work starts.
Connect data
Owners connect their business bank accounts through Open Banking, with their consent, including accounts held with other providers. They can also connect supported accounting and commerce services, such as Xero, QuickBooks Online and Shopify. Each connection is a separate permission the owner can withdraw. If you want Coach to use data from your own systems, we agree the fields, mapping and permissions with you.
Configure the experience
Colours, typography, email branding and Coach’s tone are set for your institution. You decide which products Coach may mention, the product information and referral wording it uses, the journey links that take owners into your own applications, and where customer requests go. That destination, such as your CRM or a team inbox, is agreed during set-up.
Test and launch
Before launch we test together: sign-in and token issuing, onboarding through to the first briefing, account connections, Coach loading under your security policy, and requests reaching your team. You then open Coach to an agreed group of customers and widen it as you review use and results. Support responsibilities are set out below.
Who does what
| Area | Your team | Narrative |
|---|---|---|
| Embed and sign in | The host page and where Coach sits; the backend route that issues sign-in tokens; security policy settings for Coach’s hosted address | Connected App credentials, the hosted SDK and token verification |
| Connect data | Agreement on any data from your own systems | Onboarding, Open Banking and supported accounting and commerce connections |
| Configure | Product information, journey links and the destination for requests | Branding and product configuration |
| Test and launch | Test users, sign-off, the customer rollout and the requests that reach your team | Support through testing and launch; hosting, monitoring, releases and reporting on use |
Documentation
Developer guides for the Narrative SDK cover the quickstart, integration, authentication, configuration, white-labelling and release notes. We walk your team through the parts that apply to you.
Plan an integration with us.
Bring your product, technology and risk colleagues. We’ll show you Coach and answer your integration and governance questions.