v1.8.2

​

Release overview

v1.8.2 makes the refreshed Narrative SDK experience more dependable after users start acting on recommendations. The main improvements are clearer Money Action decisions, stronger Coach continuity across current highlights and action context, and better handling for the first-use, session, attachment, and account-data paths that support those workflows. The release also continues the v1.8 move toward concise, evidence-led product surfaces. Users see less system-facing language, more useful action detail, cleaner financial context, and smoother recovery when a source or session needs attention. Breaking changes: None. Deprecations: None.

​

What changed at a glance

​

Money Actions

Money Actions are easier to compare and act on. Detail panels now lead with the evidence-backed finding, show the expected benefit in the metadata, explain why acting matters, present concrete next steps, keep useful context in a separate Worth knowing section, and leave deeper workings and sources collapsed at the end. The action list is also more coherent. Recommendation batches are deduplicated and prioritised from completed research, with more varied verb-led titles so the list does not read like repeated copies of the same instruction. Supplier-related actions can include current-supplier context and credible alternatives when source evidence supports them, while avoiding unsupported claims when a transaction descriptor cannot be tied to one public company. Money can also surface relevant public-support opportunities, such as grants, tax reliefs, or public finance programmes, as supplementary actions after the ranked Money Action list. These actions use the same card, detail, questionnaire, snooze, and dismissal controls as other Money Actions.

​

Coach

Coach now keeps the current action context more consistently. The Coach home surface can show a current Money Action, Growth opportunity, and active Project as the user’s latest highlights, and successful login opens to the current Coach surface instead of automatically restoring an old conversation. If a user has no active Projects yet, the highlights stay useful by showing additional Growth options rather than leaving the briefing thin. When a user opens Coach from a Money Action, the conversation remains grounded in that exact action, including its plan, questions, answers, evidence, assumptions, and status. In normal Chat, users can also ask about current, historical, or named Money Actions, with clearer handling when a match is ambiguous or unavailable. Coach answers are more reliable and more user-facing. Qualitative finance questions use data-led guidance without sounding like regulated financial advice, category-level spending questions answer in plain language, and generated chat titles are based on the user’s actual question instead of a repeated greeting. Temporary answer-preparation failures are handled more smoothly, so users are less likely to hit a dead end during an otherwise recoverable Chat request. Coach Chat also supports richer file input. Users can attach supported business documents, including text-based PDFs and modern Word documents, and can send multiple supported files in one message. Validation messages explain unsupported formats, size limits, password protection, unreadable content, and other recoverable issues before Coach uses the files.

​

Growth and Projects

Growth and Project handoffs are steadier. Opening a Growth card from Coach now preserves the selected opportunity, and Project context passed back into Coach includes more of the Project plan and opportunity background so follow-up answers stay grounded in the item the user selected. Project generation is more execution-ready. Generated Projects are shorter, clearer, and less repetitive; step counts are easier to work through; project cards avoid duplicate titles; and active Projects stay ordered by the most recent meaningful change so newly created or recently updated work is easier to find. Growth content is also more consistent. Opportunity copy uses clearer labels and timing, avoids language-mixing in generated Project content, and is more tolerant of valid lower-volume opportunity output during onboarding, so users are not blocked when the system has enough quality material to proceed.

​

Onboarding and account experience

First-use flows are more resilient. Onboarding can import up to the latest 12 months of available bank transactions by default, uses a simpler header, and keeps account connection and processing progress clearer. Website and business-context capture is more careful about validation, recovery, and reusing trusted information instead of repeatedly asking users for details already provided. Account and session recovery are also stronger. Long-lived sessions keep the user’s profile identity stable, action panels remain openable after the app has been left running, explicit logout targets the right account flow, and connected-account completion states recover more reliably when callbacks are delayed or nested.

​

Financial data and reporting

Financial context is more consistent across Money and Coach. Balance trends now handle accounts from the point where reliable balance data is available, reducing misleading historical movement when an account first appears part-way through a reporting window. Shared financial calculations and transaction enrichment also keep Money metrics, Coach answers, reports, and recommendation evidence aligned around the same underlying figures. Money reporting is easier to consume. The default Money financial report can be generated and refreshed as part of the Money experience, and report content is more concise, with clearer fields and presentation that better match the rest of the product.

​

Compatibility

This release remains compatible with existing v1.8 hosted integrations. No partner migration is required for standard embedded integrations. Some capabilities depend on tenant configuration, supported connected data, or enabled Coach Action settings before users see them. Existing Coach, Money, Growth, onboarding, Settings, and embedded authentication routes continue to work with the current integration model.

​

Support

Questions about this release or integration: support@narrativebanking.com SDK documentation: docs.narrativebanking.com