Relationship model and Compliant Data Sharing before the configuration sprints. Salesforce Financial Services Cloud for banks, wealth firms, and insurers that keep cores, custody, and policy admin as systems of record

Financial Services Cloud is the engagement layer for banking, wealth, and insurance: Household and relationship models, Compliant Data Sharing, referrals, Action Plans, next-best-action patterns, and service processes. Core banking, custody, policy admin, and ledgers usually remain systems of record. We design Salesforce to orchestrate advice and service work with honest handoffs to those cores.

Most FSC failures start with the wrong Household shape, Account-Account roles that do not match firm language, or sharing that drifts into Apex. We document Household vs Individual vs Business record types, A-AR roles, CDS participants, referral RACI, and core object mapping before Action Plans, NBA, or Agentforce topics go live.

Yes. Many programs start with an org that went live fast: wrong Household model, referrals configured but never adopted, CDS skipped for custom sharing, advisors working outside Salesforce, or Data Cloud connected without activation use cases. We run an FSC Health Assessment, prioritize, and rebuild with the same architecture discipline as greenfield.

We scope Agentforce to operations assistance: intake triage, knowledge retrieval, case summarisation, scheduling support, and internal SOP copilots. Advice outcomes, product recommendations that create obligations, credits, and contractual language stay under human approval. Topics and actions follow the same change control as integrations.

Banking emphasises branch and contact centre service, onboarding, and product servicing. Wealth emphasises Households, goals, life events, and advisor workflows. Insurance emphasises policy service, claims adjacency, and producer or broker motions. We keep one FSC spine and vary objects, journeys, and reporting to the line of business.

Usually no. Cores, policy admin, custody, and ledgers stay systems of record. Salesforce owns the client graph for authorized engagement, advice and service workflows, referrals, and many marketing or nurture journeys. Integration contracts define freshness SLAs without pretending CRM is the book of record.

Core banking or policy admin, custody and portfolio feeds, document and e-sign, telephony or CCaaS, identity providers, marketing or CDP adjacency, and sometimes claims or underwriting systems. We prefer MuleSoft or native patterns with explicit SLAs, retries, and observability.

Topics and actions are limited to approved knowledge and operational steps. Outputs that affect advice, product selection, pricing, or legal language require human confirmation. We separate client-facing agents from internal copilots and log where compliance requires it.

Phase one usually covers relationship model and CDS sign-off, a defined advise or service path, referral routing with owners, one portal or advisor surface if needed, and the first core integration contracts. We exit with pilot criteria, RACI, and a roadmap rather than a never-ending transformation slide.

Yes. SynconAI delivers architect-led Salesforce programs for financial services organisations across the USA and Australia, with the same governance method and local commercial follow-up.

Migrate when Households, Account-Account roles, Compliant Data Sharing, Referral Management with SLAs, Action Plans, and Financial Account context are part of your regulated operating model. Sales Cloud can host custom approximations, but those usually drift. We map objects and sharing before a big-bang cutover.