The details that actually matter about a client end up:

The result is that preparing for a client conversation means reconstructing the relationship from scratch every time.

This is the problem the living story solves.

The living story is a single, continuously updated narrative of who the client is and where the relationship stands. Client enrichment is the process that keeps it current: Vega reads the activity already flowing into your workspace (notes, tasks, emails, meeting summaries), decides what carries durable client information, and rewrites the story with it.

You don't maintain it. It maintains itself.

Every contact and every household in Vega can have a living story.

It is written in plain prose and organized around current state and durable themes, not chronology. It is not a log of what happened, and it is not a summary of your last meeting. It is the answer to the question: what do I need to know about this client before I talk to them?

That typically includes:

A living story is capped at roughly 1,500 words, so it stays something you can actually read before a call.

The living story lives on the Activity tab of a contact or household page, next to the activity feed.

For a household, the story covers the household as a whole and is built from the activity of every member. For a contact, it covers that individual.

Both exist independently. A household story is not a merge of its members' stories.

The living story is a single record shared by everyone with access to the contact or household.

That means an email from one advisor's mailbox and a note shared by another both feed the same story that the whole team reads. This is intentional: the point is a shared understanding of the client, not a per-user view.

Access to the record still controls who can see it. If a user cannot open the contact, they cannot see its living story.

Enrichment runs in three steps. Understanding them makes it much easier to predict what will and won't end up in a story.

Notes, tasks, emails, and meeting summaries that are linked to the contact, or to a household the contact belongs to, are gathered together.

This is why linking matters. A meeting or note that is not linked to the right contact or household will not reach the living story.

Each piece of activity is evaluated on its own. Scheduling back-and-forth, confirmations, newsletters, and routine task bookkeeping are dropped. What survives is anything that carries a durable fact: a life event, a financial change, a stated preference, a decision, a piece of relationship context, or work the firm delivered.

Most activity does not clear this bar, and that is by design. The living story is meant to be dense.

What survived is turned into a short digest and handed to the model, along with the story as it exists today. The story is then rewritten in full, not appended to.

This is an important distinction. Vega reorganizes the whole narrative each time so that new information is integrated where it belongs and outdated information is corrected, rather than the story growing into a list of updates.

When two pieces of information conflict, the more recent one wins, and uncertainty is written into the prose itself ("as reported", "unconfirmed") rather than presented as fact.

There are four ways a living story gets updated.

Once a day, Vega processes the previous 24 hours of notes, tasks, and emails across the firm and updates the stories of every client with material new activity.

This is the main engine. Most stories stay current without anyone doing anything.

Notes and tasks are picked up based on when they arrived in Vega, so a delayed CRM sync is never missed. Emails are picked up based on when they were sent or received.

When Vega produces a post-meeting summary, the living stories of the contacts and household linked to that meeting are updated right away.

Meetings are deliberately excluded from the daily batch for this reason, so a meeting is never processed twice.

You can ask Vega to update a client's profile directly in a chat thread, by typing or by dictating (press and hold the space bar).

Vega will identify the client, update the living story with what you said, and, for contacts not linked to your CRM, propose updates to relevant profile fields for you to review.

This is the fastest way to record something that came up in a hallway conversation or a phone call.

You can always write or edit a living story yourself.

Click the edit icon in the top right of the living story card, make your changes, and save.

Manual edits are treated like any other version of the story. The next enrichment run reads what you wrote and builds on it, so your corrections carry forward rather than being overwritten and forgotten.

For contacts and households that are not linked to your CRM, enrichment does more than the story: it can also keep structured profile fields current: job title, marital status, financial information, background, and similar fields.

For each field, Vega either:

For contacts and households that are linked to your CRM, the living story is the only field enrichment writes. Your CRM stays the system of record for structured data, and Vega will not write structured fields behind its back.

Firms can define a preferred structure for living stories — for example, standard sections such as Household and family, Financial picture, Goals, Current work.

The template is applied at the firm level and used as a soft guide: Vega follows it where it improves readability, but will not invent content to fill an empty section or force a structure onto a story where it would hurt clarity.

Contacts and households can have different templates.

To set up a living story template for your firm, contact Vega support.

By default, a living story builds up gradually from the activity that arrives after the feature is turned on. A brand-new story on a long-standing client will feel thin at first.

If you want a story built from a client's full history instead, Vega can rebuild it from up to five years of past notes, tasks, emails, and meetings in a single pass. This is a heavier operation and is run on request, one client at a time.

Contact Vega support to have a story rebuilt.

The living story is not just something to read on the contact page. It becomes part of Vega's knowledge of the client, which means it feeds:

In practice, keeping the living story good is how you make everything else Vega produces good.

Activity = what happened

Living story = what it means, and what you need to know now

Activity is complete but unreadable. The living story is readable because it is not complete: it holds what is durable and lets the rest stay in the feed.

A good habit: