Skip to main content
The Financial Plan Model is a built-in data model that holds the plan a customer is working on — the adjustments they have made, the recommendation they were given, and the products involved. Because it is stored centrally rather than inside a single chatflow’s responses, the same plan can be read and updated from several chatflows and live pages.

Reading and updating the financial plan across a flow

​
Why This Matters

Before this model, everything a customer decided lived in the chatflow they happened to be in. A second flow — a follow-up conversation, an advisor’s review, a results page — started from nothing.

One plan, many flows

A customer can start a plan in one chatflow and continue it in another without re-entering anything

Advisor and customer see the same thing

The plan an advisor adjusts is the plan the customer sees on their live page

Persisted, not session-bound

Stored against the customer, so it survives a closed browser or a later visit

Referenceable like any data model

Its fields can be used in entity labels, live page blocks, and conditional logic

​
What It Holds

The model is structured around the plan the customer is building:
  • Adjustments — the changes the customer or advisor has made to the baseline situation
  • Recommendation — the recommendation produced for this customer, and the figures behind it. Pension and life insurance are held together as one Life & Pension Recommendation per person (primary and spouse), each with a retirement, death and disability strategy and a single policy configuration. The stored recommendation keeps the death and disability scenarios and each policy product’s risk coverages, so a later flow can read them back
  • Products — the specific pension policies and mortgage products the plan points at

​
Death and disability strategies

Each person’s recommendation has an optional death strategy and disability strategy. Both are chosen with a strategy type and then filled in with the fields that type needs: Leave a strategy unset and the recommendation keeps whatever the customer already has. The fields appear in the data model editor alongside the retirement strategy and can be mapped from entity responses or trigger outputs like any other field.
Version 3.9.0 renamed the recommendation sections: the separate pension and life insurance recommendations became Primary Life & Pension Recommendation and Spouse Life & Pension Recommendation. A flow that mapped onto the old section names needs its mappings re-pointed.
Product fields hold product ids, which are dynamic. Populate them from the List Policy Products and List Mortgage Products triggers rather than typing an id by hand.

​
Using It in a Flow

1

Add the model to your flow

Open the Data Models panel in the flow builder and add the financial plan model. It appears alongside your custom models.
2

Map values into it

Use the master-detail form editor to map entity responses, trigger outputs, and calculation results onto the model’s fields. Hover a field’s info icon to read what it expects.
3

Reference it elsewhere

Once populated, the model’s fields are available as resources — in entity labels, live page blocks, and conditional logic.
4

Read it back in another flow

A second chatflow or live page that includes the model reads the same stored plan for that customer.

Data Model Editor

How to map values onto a data model’s fields

Triggers & Automation

The product catalogue triggers that feed the plan’s product fields

Calculation

Where the recommendation figures come from

Live Pages

Presenting a customer’s plan on a page