Actionable Relationship Center in FSC: A Practical Guide for Banking

The Actionable Relationship Center — ARC — is the most powerful and most consistently underused feature in Salesforce Financial Services Cloud. It is installed in nearly every FSC org. It is properly configured in a small fraction of them.

This guide explains how ARC actually works, what it takes to configure it properly for a banking context, and why most implementations get it wrong.

What ARC Is (And Isn't)

ARC is a visual relationship intelligence component that renders in the advisor's view of any Account or Financial Account record. It displays an interactive graph showing the client, their related individuals and entities, their financial accounts, and configurable action buttons.

ARC is not a reporting tool. It's not a data visualization dashboard. It's an operational interface — designed to be used during an advisor-client conversation, not in a weekly reporting meeting. This distinction matters for how you configure it.

When ARC works correctly, an advisor opening a client record sees:

• The client as a central node, with household members (spouse, dependents) branching out
• Each household member's financial accounts visible as child nodes
• Business relationships (if the client has business accounts) as separate clusters
• Related advisors, beneficiaries, and external contacts as peripheral nodes
• Action buttons on each node — 'Log Interaction', 'Create Referral', 'Open Account'
• Hover cards with key data for each node — balance summary, open referrals, last contact date

ARC requires the Financial Services Cloud Einstein license tier or above. If your org is on the older FSC base license, ARC may not be available. Check in Setup → Installed Packages → Financial Services Cloud.

The Data Foundation ARC Requires

ARC renders what exists in your data model. Before you configure a single ARC setting, the underlying data needs to be correct. This is where most implementations fail — teams configure ARC beautifully and then wonder why advisors see empty graphs.

Relationship Groups

Every household and business relationship that should appear in ARC must have a corresponding Relationship Group record. This does not happen automatically when you import Account records. If you migrated 50,000 client accounts from your core banking system and did not create Relationship Group records, ARC will show individual clients with no household connections.

Creating Relationship Groups for existing clients requires: identifying household relationships in your source data (typically a household ID field in core banking), creating a Relationship Group record per household, and creating Relationship Group Member records connecting each individual Account to their Relationship Group with the correct role (Primary, Joint, Minor Dependent, etc.).

Financial Account Role Records

Financial Account Role records connect an Account (person or entity) to a Financial Account in a specific role. Primary Owner, Joint Owner, Beneficiary, Power of Attorney, Trustee. Without these records, ARC has no edges to draw between clients and their accounts.

This is typically part of the core banking integration: when a Financial Account record is created in Salesforce, the integration should also create Financial Account Role records for every account holder. If the integration only creates the Financial Account record, you'll have accounts floating without visible owners in ARC.

ARC Configuration: The Technical Setup

ARC configuration lives in Setup → Actionable Relationship Center. The key configuration decisions:

Node Types

Which object types appear as nodes in the graph? For a retail banking context, the standard set is: Account (Individual), Account (Business), Financial Account, Relationship Group. For wealth management, add Financial Holdings or Financial Goals. For commercial banking, add Lead and Opportunity.

Resist the temptation to add every object. ARC becomes unusable when there are too many node types. Start with the minimum set advisors need during a client conversation.

Relationship Types

Which relationships create edges in the graph? The FSC-native relationships are: Household Member (via Relationship Group Member), Financial Account Owner (via Financial Account Role), and Advisor-Client (via the FSC relationship object). Custom relationship types can be added, but each one adds cognitive load to the graph.

Cards

Each node type has an associated card — a popup with configurable fields that appears when the advisor hovers or clicks on a node. Configure cards to show only what the advisor needs in the moment: for an Individual Account node, show Name, Last Contact Date, Primary Advisor, and Total AUM. Not 20 fields.

Actions

Actions appear as buttons on each node. These are the 'actionable' part of Actionable Relationship Center. Standard useful actions: Log Interaction (on any Account node), Create Referral (on Individual Account), Open Account (on Relationship Group), Schedule Meeting (on Individual Account).

Actions can trigger Flows, open related record quick actions, or navigate to record creation forms. The key design principle: every action in ARC should be something an advisor would want to do during a live client conversation. If it's a back-office action, it doesn't belong here.

ARC for Specific Banking Contexts

Retail Banking

Focus on household completeness. The primary value of ARC for retail banking is seeing the complete household financial picture — all accounts, all family members, all products. Configure the Relationship Group node prominently with a card showing total household deposits, total loans, and number of products.

Wealth Management

Add Financial Goals as a node type. Wealth advisors want to see client goals alongside portfolio holdings — are the accounts structured to support the stated goals? Include AUM data in the Financial Account card and a 'Review Goal' action.

Commercial Banking

Business Account structure is more complex. Include the business entity hierarchy — parent company, subsidiaries, related entities. Add a 'Business Account' node type with revenue, industry, and primary contact visible in the card. The relationship between a business and its principals (officers, major shareholders) is often critical to commercial advisor context.

Why Advisors Don't Use It (And How to Fix That)

Even when ARC is technically correct, adoption can fail. The common reasons:

• Load time: ARC with large relationship graphs (100+ nodes) can load slowly on older hardware. If it takes 8 seconds to render, advisors stop clicking on it. Limit node count with display limits in configuration.
• Data quality: advisors quickly learn that ARC shows incomplete data if household records were never properly migrated. One check with stale or missing data destroys trust in the feature.
• Training that shows features, not workflows: advisors trained to 'here's what ARC shows' rather than 'here's how to start your client conversation with ARC' don't integrate it into their practice.
• Actions that don't work: if the 'Log Interaction' action in ARC takes 5 form fields vs. a native 2-field quick action, advisors will use the quick action. Every ARC action must be faster than the alternative.

In our remediation work, orgs that properly configure ARC and address data quality issues see advisor adoption rates above 75% within 60 days of re-launch — versus near-zero usage with an unconfigured ARC that was technically deployed.

The Configuration Checklist

1. 1.Relationship Group records exist for all household and business relationships — not just new post-go-live records.
2. 2.Financial Account Role records connect every client to their accounts.
3. 3.ARC node types are limited to what's needed in an advisor conversation (typically 4–5 max).
4. 4.Cards for each node type show 4–6 fields — no more.
5. 5.Actions are tested end-to-end for each node type and require fewer steps than the non-ARC equivalent.
6. 6.Load time tested with the largest relationship graph in your production org.
7. 7.ARC is on the default page layout for Account — not buried in a tab that advisors have to navigate to.
8. 8.Display limits set on nodes to prevent performance issues with very large households or commercial relationship trees.

ARC is worth getting right. When an advisor can open a client record and immediately see the complete financial picture — who's in the household, what they own, when they were last contacted, what referrals are open — that's the kind of tool that changes how they work. Not a nice-to-have dashboard, but a live operational tool that makes the advisor's job meaningfully easier.

That outcome is available in every FSC org. Most just haven't been configured to deliver it.