Salesforce · Financial Services Cloud · Wealth

Enhance Wealth Management with Financial Services Cloud: The Advisor Workflow Guide

Buying Financial Services Cloud is the easy part. The value comes from how you set up households, review cycles, onboarding, meeting notes, custodian data and AI around the way your advisors actually work. This guide walks through each one, with what to configure and what to avoid.

Key Takeaways

  • Financial Services Cloud enhances wealth management when it is set up around six advisor workflows: households, the review cycle, onboarding, meeting notes, custodian data and AI assistance.
  • Salesforce recommends implementing it on the core platform; the managed package is now the exception, needed mainly for ISV dependencies.
  • The household model is the decision everything else depends on: rollups, reports, sharing and AI meeting prep all read from it.
  • Compliant Data Sharing is off by default, and managers can see their team's Interaction Summaries unless you configure otherwise. Design sharing before go-live.
  • Agentic Advisor features such as Meeting Concierge and Run My Day reached general availability in mid-2026. They are only as good as the client and portfolio data underneath them.

Financial Services Cloud advisor workflows are the day-to-day processes a wealth firm runs inside Salesforce Financial Services Cloud (FSC): building households, preparing and running client reviews, onboarding new clients, recording meetings, pulling in custodian data and, increasingly, letting AI agents do the preparation. We first published this article in June 2024 as a feature overview. This version is a practical setup guide: for each workflow, what FSC provides, what you need to configure, and where firms go wrong.

It is written for wealth management leaders, operations heads and Salesforce admins at growing and mid-market firms, such as registered investment advisers, broker-dealers, private banks and multi-family offices, that have chosen FSC or already run it. If you are still deciding whether FSC is right for you, start with our Financial Services Cloud evaluation guide for wealth management, which covers fit, cost and alternatives.

Section 01 · Short Answer

How Does Financial Services Cloud Enhance Wealth Management?

Financial Services Cloud gives advisors one record of each client and household, with their accounts, goals, life events, meetings and tasks attached. On top of that it adds repeatable workflows for reviews and onboarding, sharing rules built for regulated firms, and AI that prepares meetings. The gain comes from configuring those pieces around your advisors' real week, not from switching them on.

Salesforce Financial Services Cloud logo: the Salesforce cloud above the words financial services cloud
Advisor jobFSC capabilityWhat you configure
Know the whole familyPerson accounts, households, the Actionable Relationship CenterHousehold rules, relationship types, primary groups
See total wealthFinancial accounts, holdings and financial summary rollupsAccount types, custodian feeds, rollup schedule
Run reviews on timeAction plans, life events and milestones, financial goalsReview templates, task owners, due-date rules
Onboard without paper chaseDiscovery Framework, the KYC data model, Intelligent Document AutomationIntake questions, document lists, KYC risk rules
Record meetings safelyInteraction Summaries, Compliant Data Sharing, ShieldConfidentiality levels, participant roles, audit fields
Prepare fasterAgentforce for Financial Services and the Agentic Advisor featuresData 360, agent actions, human review steps

A note on naming: Salesforce Help now documents the product as Agentforce Financial Services (formerly Financial Services Cloud), while Salesforce's current pricing page sells Financial Services Cloud Core, Advanced and Max editions. Both names refer to the same product, and you will see both in your org.

Section 02 · Foundation

Should You Build on Core FSC or the Managed Package?

Build on core unless something forces the managed package. Salesforce calls the core platform "the default and recommended approach," and since Winter '23 and Summer '24 financial goals, the financial account data model, groups and households, and rollups have all been standard features. The managed package is for exceptions, such as an ISV product that depends on it.

Core fits when you are starting fresh or rebuilding, your third-party apps support the standard objects, and you want new features without a push upgrade every release. The standard FinancialAccount object needs API version 61.0 or later and the Financial Account Management Standard Objects setting turned on.

The managed package stays when a custodian feed, planning tool or other ISV app you rely on is built on its objects, or when an existing org has years of automation on them. Some AI actions, such as Get Client Life Events, are also documented as managed-package features, so check each one you plan to use.

If you inherited a managed-package org, don't migrate for its own sake. Inventory which package objects your integrations, reports and automations use, check what your ISVs support, and plan the move as its own project. Our Financial Services Cloud services cover both new builds and that kind of data migration.

Section 03 · Data Model

How Should You Model Households and Client Relationships in FSC?

Model each client as a person account and each household as a business account linked to a party relationship group of type Household. A client can belong to several groups but has exactly one primary group, and that primary group is where their accounts roll up. Decide those rules before loading data, because rollups, reports and sharing all depend on them.

Salesforce's FSC data model documentation makes person accounts the default for new installations; the older individual model is supported only for orgs already using it. The Trailhead households module shows how the New Group flow creates the household account, the group and every member relationship in one step.

Real-world situationHow it maps in FSC
A married couple with joint and individual accountsTwo person accounts in one household; each financial account carries its owners as financial account parties
An adult child who is also a clientTheir own household as primary group, plus membership in the parents' group so the relationship stays visible
The family's attorney or accountantA contact-to-contact relationship with a reciprocal role (Salesforce's own example is client and attorney)
A trust, family company or foundationA business account related to the household members, shown on the relationship graph
Total household wealthFinancial summary rollups, calculated by eight predefined Data Processing Engine definitions and stored on the Account Financial Summary object

The Actionable Relationship Center (ARC) draws those relationships as a graph that advisors can also edit from. The new ARC lets you build custom graphs from standard and custom objects; the original ARC offers preconfigured graphs only. For activity history, record rollups surface a member's tasks and events at household level, and in managed-package orgs group-level rollups stamp a Household__c field that Salesforce says you must not change.

Household drift. Divorces, deaths and children leaving home change the primary group. Without a defined process, rollups quietly count the wrong accounts.
Duplicate people. One client loaded twice from two custodians becomes two people in two households. De-duplicate before you build groups, not after.
Business entities as people. Trusts and family companies stored as person accounts break reporting on clients versus entities.
Section 04 · Reviews

How Do You Run a Repeatable Client Review Cycle in FSC?

Use action plan templates for each type of review, triggered by the calendar or by a life event. Each task in an action plan has a priority, a deadline in days and an owner. Salesforce's own wealth example is a financial plan review: schedule the meeting, collect documents, review them. That turns a review from an advisor's memory into a tracked, reportable process.

Action plans support prerequisite tasks, so "review documents" can't start until "collect documents" is done. Tasks can be assigned to a team role, such as the client service associate on the account team, or to a queue, so templates keep working when people change. Pair them with life events and milestones: a retirement date, a new grandchild or a business sale should start the right plan, not wait for the next annual meeting.

1. Trigger.
→ An annual or semi-annual date per household tier, or a recorded life event, starts the review action plan.
2. Prepare.
→ The associate books the meeting and requests updated documents; the advisor reviews goals, holdings and open tasks.
3. Meet.
→ The advisor records decisions, attendees and follow-ups in an Interaction Summary.
4. Follow up.
→ Action items become tasks with owners; financial goals are updated.
5. Report.
→ Leadership sees overdue reviews by advisor and tier, instead of finding out at audit time.

One caution from Salesforce's life events documentation: you can mark an event type as unique, such as a birth, but bulk data loads can still create duplicates. Clean life events after every migration load, or one event will trigger two review plans.

Section 05 · Onboarding

How Do You Automate Client Onboarding in Financial Services Cloud?

FSC onboarding combines three parts: Discovery Framework for intake questions and digital forms, the KYC data model for identity checks and risk ratings, and Intelligent Document Automation for reading uploaded documents. An action plan ties them together, so every new household follows the same steps and nobody has to chase a missing form by email.

Discovery Framework

Assessment questions and digital forms capture what you need to know about a new client, such as goals and household details. A document matrix generates the list of files each client must provide.

KYC and Screening

A KYC data model stores identity checks and risk ratings. The Data Consumption Framework calls third-party screening services from inside the flow.

Document Automation

Uploaded PDF, JPG and PNG files are read by OCR in the background and the extracted values mapped to Salesforce fields.

Salesforce's integrated onboarding guide covers the setup. Two limits in the Intelligent Document Automation documentation catch firms out: extracted data maps only to Default record types, and fillable PDF form fields are not read. If your new-account paperwork is mostly fillable PDFs, plan a different capture path for those fields.

Section 06 · Compliance

How Do You Keep Advisor Notes and Client Data Compliant in FSC?

Record client meetings as Interaction Summaries with a confidentiality level, control who sees them with Compliant Data Sharing, and keep an audit trail with Salesforce Shield where your regulators expect one. None of this is automatic. Compliant Data Sharing is off by default, and the role hierarchy grants managers access to their team's summaries unless you design around it.

Interaction Summaries keep notes, attendees, action items and files in one record, can link to several records at once, and work on mobile. Unlike standard notes, which inherit the sharing of their parent record, they carry their own confidentiality setting. Compliant Data Sharing then grants access through participant roles and groups, so a record is shared with the people on the relationship rather than everyone above them in the hierarchy.

1. Hierarchy access you can't switch off. Grant Access Using Hierarchies is always on for Interaction Summary in org-wide defaults. If managers must not read every advisor's notes, design your roles and confidentiality levels for that.
2. Permission sets missing the feature. Compliant Data Sharing is disabled by default in the FSC permission sets. Turning it on in setup is not enough.
3. Field history that doesn't last. Standard field history is limited. Shield's Field Audit Trail keeps up to 10 years of history on up to 200 fields per object.
4. No record of who looked. Shield Event Monitoring logs more than 70 types of user and system events, which is how you answer "who viewed this client?"

See Salesforce's Shield overview for the full set, including Platform Encryption and Data Detect. Data Detect is also included in the FSC Advanced edition. One principle to hold on to: FSC gives you the controls, but it does not make a firm compliant. Your compliance team still decides what is retained, who sees what, and how it is reviewed.

Section 07 · Integration

How Do You Get Custodian and Portfolio Data Into FSC?

FSC is not a portfolio accounting system, so account, holding and balance data has to come from your custodians and portfolio tools. Salesforce describes three routes: Data 360 with its financial services data model and connectors, a custom or MuleSoft integration, or a partner app from AppExchange. Most firms combine a nightly feed for balances and holdings with event-driven updates for new accounts.

Layer 1 · Sources

Custodians, Planning and Portfolio Systems

Account, position and transaction files from each custodian, plus your planning and portfolio management tools.

↓ feeds, APIs or connectors ↓
Layer 2 · Integration

Matching, Mapping and Scheduling

Match each account to the right client, map it to financial accounts and holdings, and decide what loads nightly and what loads in real time.

↓ clean, owned records ↓
Layer 3 · FSC

Financial Accounts, Rollups and Advisor Views

Rollups total household wealth; the asset allocation component, goals and reviews read from the same records.

Salesforce's Agentic Advisor module says portfolio data from different custodians arrives "through connectors or custom integrations," and Data 360 for financial services ships prebuilt mappings and streams. A prebuilt Connector Library for custodians has been announced but is listed as coming soon, so plan around what exists today.

The hard part is usually layer 2: one client with accounts at two custodians, or account numbers formatted differently in each feed. We build those integrations with MuleSoft and other platforms, and design Data 360 on top when the firm needs it.

Section 08 · AI

What Does Agentforce Add for Wealth Advisors in 2026?

Agentforce for Financial Services prepares and follows up on client meetings. Its Agentic Advisor features summarise a client's portfolio, goals, life events and open tasks before a meeting, plan the advisor's day, and draft follow-ups, all inside a human-in-the-loop framework and within existing permissions. Several features became generally available in mid-2026; others are still announced as coming soon.

FeatureWhat it doesStatus (per Salesforce)
Meeting ConciergePrepares the advisor with client context, captures the meeting, and drafts summaries for advisor approval, with tasks assigned afterwardsGA June 2026
Run My DayA daily workspace that puts time-sensitive tasks first, surfaces at-risk clients and prioritises opportunitiesGA July/August 2026
Enhanced Client DetailsOne view of a client and their household: accounts, holdings, relationships, life events, goals and activityGA July/August 2026
Client Meeting PreparationAn agent subagent that summarises client data, portfolio performance, goals, life events and pending tasksDocumented in Help
Connector Library, Book of Business Insights, Anywhere AdvisorPrebuilt custodian and system connectors, trends across the whole book, and the advisor experience in Slack, Microsoft Teams and moreComing soon

Sources: Salesforce's Agentic Advisor announcement and the financial advisor agent reference. Salesforce's Agentforce for Financial Services announcement put advisors' share of time on direct client engagement at 39%, which is the time these features aim to give back.

Two practical points. First, licensing: Agentic Advisor is included in Agentforce for Financial Services and in Agentforce 1 Edition for Financial Services, and some actions, such as Get Client Life Events, need a per-user add-on. Second, data: a meeting brief is only as accurate as the households, holdings and life events it reads. If sections 3 to 7 aren't in order, start there. Our Agentforce readiness assessment checks exactly that before you commit.

Section 09 · Rollout

In What Order Should You Roll Out FSC Advisor Workflows?

Start with the data model and sharing, then the workflows advisors touch every week, then AI. Each layer depends on the one before it: reviews need correct households, reports need consistent reviews, and agents need all of it. Going in this order lets you show value to advisors early without building on records you will have to restructure later.

1. Decide the model.
→ Core or managed package, household and primary-group rules, how entities and trusts are represented.
2. Design sharing.
→ Participant roles, confidentiality levels and audit requirements, agreed with compliance before data arrives.
3. Connect custodian data.
→ De-duplicate clients, match accounts and schedule feeds; confirm rollups against custodian statements.
4. Launch reviews and onboarding.
→ One action plan template per review type and one onboarding path, piloted with a small advisor team.
5. Add AI.
→ Switch on meeting preparation for the pilot team, measure preparation time, then extend.

Existing orgs usually need clean-up before step 4. In one published project, our audit of a US mid-market financial services firm's FSC and Pardot org migrated 100% of its Process Builder automations to tested Flows, consolidated two overlapping reminder journeys into one under a single suppression rule, and took SMS reminder failures to zero. That firm's issues were specific to its org, so read it as an example of the clean-up pattern, not a benchmark.

Section 10 · Bottom Line

The Bottom Line

Financial Services Cloud enhances wealth management when it mirrors how your advisors work: who belongs to which household, when reviews happen, what onboarding requires, who may read which notes, and where portfolio data comes from. Get those right and the AI features released in 2026 have something reliable to work with. Get them wrong and you have an expensive contact list.

  1. 1

    Build on core FSC unless an ISV dependency requires the managed package.

  2. 2

    Agree household and primary-group rules before loading any data.

  3. 3

    Turn reviews and onboarding into action plan templates with owners and deadlines.

  4. 4

    Design Compliant Data Sharing and Interaction Summary confidentiality with compliance, before go-live.

  5. 5

    Treat custodian integration as its own workstream, then add Agentforce on top of clean data.

Ready to Start

Get Your FSC Advisor Workflows Right the First Time

On a 30-minute discovery call, a Twopir Salesforce architect will review your household model, custodian data and sharing design, and tell you what to fix or build first.

Schedule a Discovery Call

FAQ

Frequently Asked Questions

A household is a business account linked to a party relationship group of type Household, with each member as a person account. A client can belong to several groups but has one primary group, which is where their financial accounts roll up. Financial summary rollups then total the household's investments, liabilities and deposits.

Usually not. Salesforce recommends implementing FSC on the core platform, where households, financial accounts, goals and rollups are standard features. The managed package is needed only for specific cases, such as an ISV app built on its objects, and it requires a push upgrade each release.

Yes, but through integration rather than out of the box. Salesforce says custodian portfolio data arrives through connectors or custom integrations, using Data 360, MuleSoft or AppExchange partner apps. Its prebuilt Connector Library for custodians is announced but listed as coming soon.

Partly. Salesforce lists Meeting Concierge as generally available from June 2026 and Run My Day and the Enhanced Client Details page from July or August 2026. The Connector Library, Book of Business Insights and Anywhere Advisor are listed as coming soon. Check availability in your own org before planning around them.

Record meetings as Interaction Summaries, which carry their own confidentiality level, and enable Compliant Data Sharing so access follows participant roles. Note that Grant Access Using Hierarchies cannot be turned off for Interaction Summary, so managers can see their team's summaries unless roles are designed for it.

It depends on your audit and retention requirements. Shield adds Field Audit Trail, which keeps up to 10 years of field history on up to 200 fields per object, Event Monitoring for user activity, Platform Encryption and Data Detect. Firms that must prove who changed or viewed client data usually need it.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Financial Services Cloud, custodian integrations and Agentforce on Salesforce, for 500+ clients over 12+ years.