By David Cockrum, Founder & CEO, Vantage Point
Financial services leaders are asking the same questions over and over right now: Can we adopt Agentforce if we're still on the FSC Managed Package? Do we have to migrate to FSC Standard first? Which templates serve customers versus employees? Which channels do they support?
This guide answers the top questions we hear from banking, wealth, and lending teams evaluating Agentforce for Financial Services templates — and explains exactly what you need to do to get started today.
TL;DR — Key Takeaways
- What is it? A library of prebuilt Salesforce Agentforce agents purpose-built for banking, wealth, lending, and collections — packaged as templates you configure, not code from scratch.
- Key benefit: Most templates work out of the box. Three are customer-facing (Agentforce Service Agent / ASA), the rest are employee-facing (Agentforce Employee Agent / AEA).
- Cost / Investment: Requires Financial Services Cloud plus the relevant Agentforce add-on SKU (Service Agent or Employee Agent) and Flex Credits for consumption. Pricing depends on volume.
- Best For: Retail banks, wealth firms, credit unions, lenders, and insurance carriers running on FSC — whether on the Managed Package or FSC Standard.
- Bottom Line: Being on the FSC Managed Package does NOT block Agentforce adoption. Migration to FSC Standard is a separate long-term workstream — not a prerequisite. Start with the templates that map to your highest-volume employee or customer workflows.
Agentforce for Financial Services is a collection of prebuilt agent templates built on top of Salesforce Financial Services Cloud (FSC) and the Einstein Trust Layer. Each template ships with subagents, actions, prompts, and data references designed for a specific FS workflow — onboarding, service, collections, advisory prep, lending, and more.
Think of the templates as starting points: you clone the template, point it at your data and channels, customize the prompts, and deploy. You're not building an agent from a blank canvas.
All templates operate within the FSC compliance framework — approvals, disclosures, and audit trails — and inherit the Einstein Trust Layer's data masking, zero-retention, and toxicity controls.
Authoritative reference: Agentforce for Financial Services overview (Salesforce Help)
No. This is the single biggest myth we hear, and we want to put it to rest:
Customers on the FSC Managed Package can get started with Agentforce for Financial Services today. Most templates work out of the box with no additional steps.
The only meaningful exception is the Financial Advisor Assistance template for the FSC Managed Package, which requires one straightforward additional step: installing an unmanaged package that bridges the template into the Managed Package data model. Setup instructions and the direct install link are documented in Salesforce's release note for the FSC Managed Package Financial Advisor Assistance Agent.
If you've been told you need to finish migrating off the Managed Package before you can even pilot Agentforce — that's incorrect.
No. Migration is not a prerequisite for Agentforce adoption. It is a separate, independent workstream and should never be positioned as a blocker for AI initiatives.
That said, a few facts worth holding in tension:
Bottom line: Don't let "we're still on the Managed Package" stall an AI pilot worth millions in advisor and service-rep productivity.
Three templates in the Agentforce for Financial Services library are deployed externally as Agentforce Service Agent (ASA) type agents — meaning your customers interact with them directly.
The most versatile template in the lineup. After securely verifying a customer's identity, it helps customers self-serve common banking requests, including:
Channels supported: WhatsApp, SMS, Experience Cloud portals, custom mobile apps, third-party websites, and Agentforce Voice (GA) — making it one of the most versatile templates in the catalog.
A customer-facing agent that guides potential borrowers through finding mortgage, auto, personal, and other loan options. It retrieves product categories, details, and programs and matches them to a borrower's needs, automates the first step of the lending funnel, and frees loan officers to focus on high-value conversions. Salesforce setup docs.
A customer-facing collections agent that handles compliant outreach, payment plan setup, hardship intake, and payment link delivery — reducing the volume of low-complexity calls reaching your collections team and lifting recovery rates.
Every other template in the Agentforce for Financial Services library is an Agentforce Employee Agent (AEA) type — designed for internal users (advisors, bankers, service reps, collectors, ops teams).
| Template | Who Uses It | What It Does |
|---|---|---|
| Banking Service Employee Assistance | Retail banking service reps | Balance inquiries, lost card reports, fee reversals, stop payments, transaction lookups — all integrated with core banking. |
| Financial Advisor Assistance | Advisors, relationship managers | Pre-meeting summaries of portfolio, goals, plans, life events; asset allocation review; wealth client summaries. Works with FSC Managed Package via unmanaged add-on. |
| Banking Relationship Assistance | Bankers, advisors, RMs | Post-meeting wrap-up: structures notes, creates interaction summaries, updates client plan objectives, generates follow-up tasks. |
| Collections Assistance | Collections specialists and managers | Talking-point generation, promise-to-pay creation, payment-link generation, call-script generation, legal-case eligibility checks. |
The pattern: prepare with Financial Advisor Assistance → conduct the client meeting → wrap up with Banking Relationship Assistance. The Banking Service Employee and Collections Assistance templates run continuously in the rep's flow of work.
The right pilot depends on where you have the most repetitive, high-volume, low-judgement work today. A simple framework we use with clients:
The wrong move: trying to deploy four templates simultaneously across all channels in a six-week sprint. Pick one workflow, prove value, then expand.
For most templates, the steps are:
FSC Managed Package customers following the Financial Advisor Assistance path add one step: install the unmanaged package documented in the Salesforce release note and apply the included permission set group.
Every Agentforce for Financial Services template runs through the Einstein Trust Layer, which provides:
Customer-facing (ASA) templates add an additional identity-verification step before any account-level action. Employee-facing (AEA) templates respect the agent user's permission set, sharing rules, and field-level security — so an agent cannot show a banker data the banker isn't allowed to see.
That said, the Trust Layer is not a substitute for a compliance review. You still need to validate prompts, disclosures, and channel usage against your firm's policies, FINRA, SEC, GLBA, state insurance regs, and any consent-management framework you operate under.
No. Migration is not a prerequisite for Agentforce adoption. The Managed Package is fully supported for most Agentforce for Financial Services templates today. Migration to FSC Standard is a worthwhile long-term conversation, but it should not be positioned as a blocker for your AI roadmap.
Three templates are deployed as Agentforce Service Agent (ASA) types and interact directly with customers: Loan Product Assistance, Banking Service Customer Assistance, and Collections and Recovery Assistance for Customers. All other templates are Agentforce Employee Agent (AEA) types intended for internal users.
Banking Service Customer Assistance is the most versatile, with documented support for WhatsApp, SMS, Experience Cloud, custom mobile apps, and Agentforce Voice (GA) — making it one of the few templates that can deliver a true omnichannel experience for retail banking customers.
Yes. There is one additional straightforward install step — an unmanaged package — documented in the Salesforce release note. After installation, the template functions against the Managed Package data model.
Agentforce Service Agent (ASA) licenses authorize agents to interact externally with customers, including across digital and voice channels. Agentforce Employee Agent (AEA) licenses authorize internal use only and respect the employee user's permission set. Many financial institutions need both to deploy customer-facing and employee-facing templates simultaneously. Consumption is metered through Flex Credits.
Yes for most templates, but Data Cloud unlocks meaningfully better grounding — especially for advisor prep, household 360, and personalized loan recommendations. We typically recommend Data Cloud as a fast-follow to the first template, not a hard prerequisite.
A focused, single-template pilot can run in 6–10 weeks when scope is disciplined: one template, one channel, one user group, one set of measurable outcomes. Scope creep is the most common reason pilots run longer.
The canonical starting points are the Agentforce for Financial Services overview, the Trailhead module on Agentforce for FSC skills, and the Banking Service Assistance setup docs.
The firms making the most progress with Agentforce for Financial Services right now share three habits:
That's the operator's view from the implementation side. The templates are good. The Trust Layer is enterprise-ready. The hardest work is still the work that's always been hard: clean data, clear scope, real change management.
If you're sitting on FSC and trying to decide which template to pilot — or whether the Managed Package is really blocking you — that's a conversation worth having before the next AI budget cycle locks in.
Vantage Point is a senior-led, AI-augmented Salesforce and HubSpot consultancy for regulated industries. We've delivered 400+ engagements for 150+ clients with a 95% retention rate and 4.71/5.0 average engagement rating.
For Agentforce for Financial Services, we help banking, wealth, lending, and insurance teams:
Book a discovery conversation →