Salesforce Financial Services Cloud for Insurance: A Guide for Carriers and Brokers
Financial Services Cloud now has two separate insurance products: Digital Insurance for carriers that write and service policies, and Insurance Brokerages for brokers and agencies. This guide explains which one fits your business, how the policy and claims data model works, what Agentforce adds, what compliance still needs from you, and what it costs.
Key Takeaways
- Financial Services Cloud (FSC) is Salesforce's industry CRM for banking, wealth and insurance. Salesforce Help has called it Agentforce Financial Services since late 2025; it is the same product.
- Insurance comes in two products: Digital Insurance for carriers (policy administration, claims, group benefits) and Insurance Brokerages for brokers (commissions, agency billing, policy servicing).
- The data model starts with the Insurance Policy object, with participants, coverages, insured assets, claims and producers around it.
- Compliance features exist, but they must be configured. FSC does not track regulatory change for you, and Shield encryption and audit trail are a paid add-on.
- Most brokers keep their agency management system (AMS) as the policy system of record and connect it to Salesforce; carriers can run policy administration inside Digital Insurance.
Salesforce Financial Services Cloud for insurance gives carriers, brokers and agencies one place to manage policyholders, policies, claims and producers, on a data model built for insurance rather than for generic sales. Used well, it shows an agent every policy a household holds before a renewal call, routes a first notice of loss to the right adjuster, and calculates producer commissions without a spreadsheet.
This guide is for operations, distribution and IT leaders at growing and mid-market companies in insurance, from regional carriers to independent brokerages, and it applies to enterprise insurers too. It replaces our earlier overview with what Salesforce actually ships today, product by product, with links to the official documentation behind each point.
What Is Salesforce Financial Services Cloud for Insurance?
It is Salesforce's financial services CRM with insurance-specific objects, consoles and add-on products. Financial Services Cloud is built on the Salesforce Platform and serves banking, wealth management, lending and insurance. For insurers it adds policy, coverage, claim and producer records, an Insurance Producer console, and two insurance products: Digital Insurance for carriers and Insurance Brokerages for brokers.
A note on the name: Salesforce Help and Trailhead have described the product as "Agentforce Financial Services (formerly Financial Services Cloud)" since late 2025, while the salesforce.com product page and pricing pages use Financial Services Cloud. Both names refer to the same product, and you will see both in documentation for a while.
Since 2019, Salesforce has delivered FSC features on the standard platform rather than in a managed package, and recommends the core platform for new implementations. That matters for insurers: the insurance objects are standard objects, so they work with Flow, reporting, sharing and Agentforce like any other Salesforce record.
Which FSC Insurance Products Do Carriers and Brokers Need?
Carriers need Digital Insurance; brokers and agencies need Insurance Brokerages. Salesforce separates them because the jobs differ: carriers underwrite, issue and manage policies, while brokers compare carrier options, advise clients and earn commission. Each product carries the features for its side of that work.
Digital Insurance
CarriersBest for: Insurers that write and service their own policies, in property and casualty, life and annuity, or group benefits.
Digital Insurance has four feature groups. Foundations defines products, coverages, terms and configuration rules. Policy Administration runs quoting, underwriting, issuance, endorsements, cancellations, reinstatements and renewals, including bulk renewals. Claims Management covers intake, adjudication, reserves and payments. Group Benefits handles group quoting, census data, enrollment and renewal. Health insurers can use Digital Health Insurance with Agentforce Health instead.
Insurance Brokerages
Brokers and agenciesBest for: Brokerages and agencies selling employee benefits, commercial property and casualty, and personal lines across several carriers.
Launched in October 2024, it covers client account management, employee benefits servicing, P&C policy servicing, commissions and revenue, and agency billing. Its named tools include a Broker of Record Tracker, a Policy Lifecycle Manager and a Producer Split Manager. It is included with FSC Advanced and Max editions.
| If you are… | Start with | Usually also need |
|---|---|---|
| A carrier replacing or modernizing policy and claims administration | FSC + Digital Insurance with Policy Administration and Claims Management | Omnistudio, Experience Cloud, MuleSoft |
| A carrier keeping its core policy system but improving service and distribution | FSC (Service or Sales) on the insurance data model | Integration to the core system |
| A group benefits carrier | Digital Insurance + Group Benefits | Experience Cloud for employer portals |
| A brokerage or independent agency on Applied Epic, AMS360 or another AMS | FSC Advanced with Insurance Brokerages, or a lighter CRM connected to the AMS | AMS integration |
How Does Financial Services Cloud Model Policies, Coverages and Claims?
Everything hangs off the Insurance Policy object. Salesforce calls it the root object in the insurance data model. It holds the policy number, type, insured, effective dates and premium. Participants, coverages, insured assets, transactions and claims all relate to it, and each policy belongs to one account.
| Object | What it holds | Example |
|---|---|---|
| Insurance Policy | The policy itself: number, type, insured, dates, premium, writing and billing carrier | A household's auto policy |
| Insurance Policy Participant | People with a role on the policy | Owner, named driver, beneficiary |
| Insurance Policy Coverage | Coverages, limits and deductibles, for the policy, a participant or an asset | Collision coverage with a deductible |
| Insurance Policy Asset | The insured item | A vehicle or a property |
| Insurance Policy Transaction | Changes over the policy's life | An endorsement or a renewal |
| Claim, Claim Participant, Claim Coverage, Claim Item | The loss, the people involved, the coverage it draws on, and the damaged items | A windshield claim on the auto policy |
| Producer, Producer Commission, Producer Split Arrangement | Agents and agencies, and how commission is earned and shared | A 60/40 split between two producers |
| Broker of Record, Commission Statement | Brokerage authority and carrier commission statements | A commercial client moving its BoR |
| Group Census, Group Class | Employee data and classes for group benefits | An employer's annual census upload |
Sources: the FSC object reference and the Salesforce insurance data model.
People, households and products
Individual policyholders are usually modeled as Person Accounts, which combine account and contact fields in one record, and grouped into households so an agent sees every policy a family holds. On the carrier side, products are defined with specifications for coverages, insured parties and insured items, and every coverage, asset and participant ties back to one. Life policies can link to securities holdings, and billing uses financial transactions, payment methods and billing statements.
What Can Insurers Do With Financial Services Cloud?
Six things matter most: run the policy lifecycle, handle claims from first notice of loss, pay producers correctly, bill clients, see the whole household, and give customers and partners self-service. Some come with FSC itself; others need Digital Insurance or Insurance Brokerages, as noted on each card.
Policy lifecycle
Quote, issue, endorse, cancel, reinstate and renew policies, including out-of-sequence endorsements and bulk renewals. Digital Insurance: Policy Administration.
Claims from FNOL
Dynamic first notice of loss intake, peril-specific adjudication rules, a single adjuster view of claim and financial data, and routed approvals for payments. Digital Insurance: Claims Management.
Commissions and splits
Direct-bill commission tracking, producer split rules, expected revenue, and reallocation when a producer leaves. Insurance Brokerages.
Agency billing
Payment terms for renewals and endorsements with premium, tax and fees, invoices, collections and general ledger tracking. Insurance Brokerages.
Household and relationship view
The Insurance Producer console, the Actionable Relationship Center to map households and businesses, Interaction Summaries for meeting notes, and Action Plans for repeatable tasks. FSC.
Portals and guided journeys
Experience Cloud sites for policyholders, agents and partners, and Omnistudio guided flows for quoting, FNOL and renewals. Companion products.
Details: Digital Insurance feature list, Claims Management developer guide, Insurance Brokerage on Trailhead and FSC workspaces and automation.
How Does Agentforce Work for Insurance in Financial Services Cloud?
Agentforce for Financial Services adds prebuilt, role-based AI agents and skills on top of FSC, and three are aimed at insurance work. They answer policy, billing and coverage questions for service reps, capture first notice of loss details, and let policyholders start a claim by voice at any hour. All of them depend on clean policy data and Data 360.
| Agent template | Who uses it | What it does |
|---|---|---|
| Insurance Service Assistance | Service reps | Answers policy, billing and coverage questions and guides reps through common transactions |
| Claims Service Employee Assistance | Claims staff | Captures FNOL data for auto, home, medical and other lines |
| Claims Voice Assistance | Policyholders | Lets policyholders start a first notice of loss by voice, 24/7 |
Salesforce marks these insurance agent use cases as capabilities that may not yet be available everywhere, so confirm availability for your edition and region before you plan around them. Two prerequisites apply to every Agentforce project:
- Data 360 must be on. Data Cloud was renamed Data 360 in October 2025, and it must be provisioned and enabled before any Agentforce feature works.
- The policy data must be trustworthy. An agent that summarizes a policy is only as good as the participants, coverages and claims behind it. Fix the data model first; pilot one agent second.
Agentforce for Financial Services works within the Trust Layer and FSC's compliance features; Salesforce describes the Trust Layer as providing zero data retention by external AI models, automatic PII masking and an audit trail of every agent action. Our Agentforce AI agent development team scopes these pilots.
What Does FSC Handle for Insurance Compliance, and What Stays With You?
FSC gives you tools to control and audit access to sensitive records; it does not make you compliant on its own. Compliant Data Sharing, Shield and Process Compliance Navigator each need configuration or a separate license, and your compliance team still owns the rules. Claims that FSC "tracks regulatory changes" for you are not supported by Salesforce documentation.
What Salesforce provides: Compliant Data Sharing to grant access by participant role and audit who can see a record and why; Shield for encryption at rest, up to 10 years of field history and event monitoring; Process Compliance Navigator for compliance controls and reporting.
What stays with you: deciding who may see which policies and claims, configuring sharing (role-hierarchy sharing may need to be switched off), buying and setting up Shield, testing reports on encrypted fields, and keeping processes in line with your regulators. None of it is automatic.
Does Financial Services Cloud Replace a Policy Admin System or AMS?
For carriers it can, with Digital Insurance Policy Administration. For most brokers and agencies it should not. A brokerage's agency management system already holds the policy of record, carrier downloads and accounting. The usual design keeps the AMS for that, and makes Salesforce the relationship, pipeline and service layer, connected in both directions.
Salesforce FSC: households, pipeline, service, producers
Agents, account managers and service teams work here: renewals, cross-sell, cases, tasks and interaction notes.
AMS or core policy system: policies, billing, carrier data
Applied Epic, AMS360 or a carrier's core platform keeps the policy of record, unless a carrier moves policy administration into Digital Insurance.
Salesforce's MuleSoft Accelerator for Financial Services includes insurance use cases, among them one to unlock AMS policy data for brokers and one to orchestrate address changes across insurance systems. Where no built-in connector exists, Salesforce's pricing FAQ points to MuleSoft, integration partners or apps on AgentExchange. We build exactly this pattern on our insurance agency CRM projects: Salesforce or HubSpot for producers and marketing, connected to Applied Epic, AMS360 or another AMS that keeps the policy of record. See also our integration services and MuleSoft integration best practices.
How Much Does Financial Services Cloud Cost for Insurance?
FSC is priced per user, from $325 to $700 per user per month at US list prices, billed annually. Insurance Brokerages is included in the Advanced and Max editions. Digital Insurance for carriers is priced per org at $180,000 a year, with usage-based add-ons for policy administration, claims and group benefits.
| Item | US list price (billed annually) | What's included |
|---|---|---|
| FSC Core (Sales or Service) | $325 per user per month | Industry data models built on Sales Cloud or Service Cloud Core Edition |
| FSC Advanced | $500 per user per month | Adds Full Sandbox, Backup & Recovery, Data Detect, Security Center; includes Insurance Brokerages |
| FSC Max | $700 per user per month | Full Agentforce for Industries suite; includes the Digital Insurance add-on |
| Digital Insurance | $180,000 per org per year | Add-on for Core and Advanced; base includes 1 FSC user, Policy Administration up to $1M gross written premium, 10K claims credits, 500K group benefits credits |
| Policy Administration add-on | $75,000 per $5M gross written premium | Requires Digital Insurance |
| Claims Management add-on | $50,000 per 50K credits | Requires Digital Insurance |
| Group Benefits add-on | $60,000 per 3M credits | Requires Digital Insurance |
Sources: Financial Services Cloud pricing and Digital Insurance pricing, checked October 2026. Salesforce lists these prices for information only and they can change. Salesforce has also announced Core, Advanced and Max Industry Editions with new pricing due "later this fall", so confirm current figures with Salesforce before you budget. Total cost also includes implementation, integration, and Shield or MuleSoft if you need them.
How Do You Implement Financial Services Cloud for Insurance?
Decide the system of record first, model the data second, and add automation and AI last. Most troubled insurance CRM projects skip the first step: two systems both believe they own the policy, and every later feature inherits that conflict. The seven steps below keep the order right.
- 1
Pick the scope and the system of record. Carrier or broker? Which system owns policies, billing and claims: the AMS, a core policy system, or Digital Insurance? Write it down per object.
- 2
Map your lines of business to the data model. Model policies, participants, coverages and insured assets on the standard insurance objects, and households on Person Accounts, before you create any custom object.
- 3
Design access and security. Set up Compliant Data Sharing roles for agents, adjusters and underwriters, and decide whether you need Shield encryption and Field Audit Trail.
- 4
Plan the integrations. Connect the AMS or core system, carrier data, payment gateways and documents, using MuleSoft, an iPaaS or APIs, with error handling that operations can see.
- 5
Build the journeys. Use Omnistudio or Flow for quoting, FNOL intake and renewals, Action Plans for repeatable servicing tasks, and Experience Cloud for customer and agent portals.
- 6
Migrate and test with real policies. Load a representative set of households, policies and claims, then test the consoles, sharing and reports with the people who will use them.
- 7
Add Agentforce on a clean base. Enable Data 360, pilot one insurance agent template on one team, measure it, then expand.
Our Financial Services Cloud services cover each step, from strategy and configuration to data migration, integration and training.
Is Financial Services Cloud the Right Fit for Your Insurance Business?
It fits when relationships span several policies, lines or people, and when you need insurance objects rather than custom ones. A small agency with one line of business and a simple pipeline may be better served by Sales Cloud or HubSpot connected to its AMS. A multi-line brokerage or carrier usually gets more from FSC's household and policy model.
Strong fit: multi-line brokerages, carriers modernizing service or claims, group benefits providers, and any insurer that needs auditable, role-based access to policy and claim data.
Think twice: single-line agencies with a simple pipeline, teams without an admin to own the data model, or projects that expect FSC to replace an AMS without an integration plan.
The Bottom Line
Financial Services Cloud can genuinely elevate insurance management, but only when you buy the right insurance product and design around a clear system of record. Carriers should look at Digital Insurance; brokers at Insurance Brokerages plus an AMS integration. Configure compliance deliberately, and add Agentforce once the policy data is clean.
- 1
Choose Digital Insurance (carriers) or Insurance Brokerages (brokers), not "FSC" in general.
- 2
Name the system of record for policies, billing and claims before you build.
- 3
Use the standard insurance objects before creating custom ones.
- 4
Treat Compliant Data Sharing and Shield as design work, not switches.
- 5
Enable Data 360 and pilot one Agentforce insurance agent at a time.
Plan Your Financial Services Cloud Rollout
On a 30-minute discovery call, a Twopir Salesforce consultant will review how policies, claims and producer data move through your systems today, and recommend which FSC insurance products and integrations fit your business.
Schedule a Discovery CallFrequently Asked Questions
Yes. Financial Services Cloud includes an insurance data model built around the Insurance Policy object, with participants, coverages, insured assets, claims and producers, plus an Insurance Producer console. Carriers add Digital Insurance for policy administration, claims and group benefits, and brokers use Insurance Brokerages for commissions, agency billing and policy servicing.
Digital Insurance is for carriers that write their own policies: it covers product definition, quoting, policy administration, claims management and group benefits. Insurance Brokerages is for brokers and agencies that place business with several carriers: it covers client servicing, commissions and producer splits, broker of record tracking and agency billing.
At US list prices billed annually, FSC Core costs $325, Advanced $500 and Max $700 per user per month, and Insurance Brokerages is included in Advanced and Max. Digital Insurance costs $180,000 per org per year, with usage-based add-ons for policy administration, claims and group benefits. Salesforce has announced new edition pricing, so confirm current figures.
Usually not. Most brokerages keep their AMS, such as Applied Epic or AMS360, as the policy system of record and connect it to Salesforce, which becomes the relationship, pipeline and service layer. Carriers are different: they can run policy administration inside Digital Insurance, or keep their core policy system and integrate it.
Yes. Salesforce Help and Trailhead have called the product Agentforce Financial Services since late 2025, while the salesforce.com product and pricing pages use Financial Services Cloud. Both names refer to the same product. Agentforce for Financial Services is the related set of AI agents and skills that runs on top of it.
FSC Core is built on Sales Cloud Core Edition and adds insurance and household data models. Choose FSC when clients hold several policies or lines, or when you need commissions and policy servicing. A single-line agency focused on producer pipeline can often start with Sales Cloud or HubSpot connected to its AMS.
Yes. Salesforce states that Data 360, formerly Data Cloud, must be provisioned and enabled for all Agentforce use. For insurance agents to give useful answers, the policy, coverage, participant and claim records they read must also be complete and accurate, so clean the data before you switch agents on.
