Salesforce Accredited Agentforce Financial Services Professional Study Guide
- Platform Administrator
- Platform App Builder
- Platform Foundations
- Platform Developer
- Platform Administrator II
- Agentforce Sales Consultant
- Agentforce Service Consultant
- Platform Data Architect
- Platform Development Lifecycle and Deployment Architect
- Platform Identity and Access Management Architect
- Platform Integration Architect
- Platform Sharing and Visibility Architect
- Heroku Architect
- B2C Solution Architect
- Experience Cloud Consultant
- Agentforce Field Service and Operations Consultant
- Agentforce Nonprofit Consultant
- Data 360 Consultant
- Omnistudio Consultant
- CRM Analytics and Einstein Discovery Consultant
- Platform User Experience Designer
- Platform Strategy Designer
- B2C Commerce Developer
- JavaScript Developer
- Omnistudio Developer
- Platform Developer II
- Marketing Cloud Engagement Administrator
- Marketing Cloud Engagement Specialist
- Marketing Cloud Engagement Consultant
- Marketing Cloud Account Engagement Specialist
- Marketing Cloud Next Consultant
- Agentforce Sales Foundations
- Business Analyst
- Marketing Cloud Engagement Developer
- Marketing Cloud Engagement Foundations
- Agentforce Specialist
- Agentforce Life Sciences Consultant
- B2B Commerce Administrator AP
- B2B Commerce Developer AP
- Agentforce Communications AP
- Agentforce Consumer Goods AP
- Agentforce Financial Services AP
- Agentforce Health AP
- Agentforce Manufacturing AP
- Public Sector Solutions AP
- Revenue Cloud Consultant
- MuleSoft Integration Foundations
- MuleSoft Developer
- MuleSoft Developer II
- MuleSoft Platform Integration Architect
- MuleSoft Platform Architect
- Tableau Desktop Foundations
- Tableau Data Analyst
- Tableau Consultant
- Tableau Server Administrator
- Tableau Next Consultant
- Tableau Architect
- Slack Administrator
- Slack Consultant
- Slack Developer
Checklist progressProgress
0/190Learned
Checklist progressProgress
0/190Learned
Given a scenario in which a customer wants an Agentforce Financial Services solution, document the business needs, value, and vision of the customer to support their desired business outcomes
0/8
Given a set of existing business processes and flows, understand the current state of business architecture and determine how to leverage Agentforce Financial Services capabilities
0/8
- Building and validating the current-state process map
- Existing Salesforce environment review for opportunities and constraints
- Integrated Onboarding capabilities for current onboarding pain points
- Relationship management pain points and delivered client insight features
- Actionable Segmentation for targeted client and prospect outreach
- Service request pain points and delivered service capabilities
- Digital Insurance Platform feature groups mapped to insurer pain points and operations
- Delivered flow templates versus rebuilding existing automations
Given the business needs of a customer, identify different business processes and outline encompassing system flows based on the existing environment
0/7
- Identifying business processes by input and outcome
- Mapping technique, audience and level of detail
- Prospect-to-client system flow from lead to onboarded client
- Digital Origination scope and process stages for account opening and lending
- Stage-gated processes with external checks and Stage Management
- Service request intake-to-fulfillment flows with Service Process Studio
- Systems of record and integration touchpoints in financial services system flows
- Person accounts versus the individual model for individual clients
- Household representation with business accounts and Party Relationship Group
- Households versus other group types and primary group membership
- Account Contact, Contact Contact and Account Account relationship selection
- Party role relationships for reciprocal relationship roles
- Financial account ownership roles with Financial Account Party
- Financial account child objects for transactions, holdings, balances and cards
- Record types for client segments and financial account product lines
- Client profile and held-away financial details beyond financial accounts
- Financial plans, financial goals and asset allocation for wealth clients
- Business clients, key people and ownership structures
- Insurance policy objects for household coverage views
- Leads and opportunities in the financial services data model
- Lending data model for applications, applicants, loan products and collateral
- Financial Deal Management objects for deal parties and deal teams
- Branch Management data model for bank branch networks
- Complaint and transaction dispute models that extend Case
- Standard features versus the managed package in a new implementation
- Adoption path for existing managed package customers
- Fit-gap against delivered capabilities before customizing
- Matching subvertical solutions to a firm's lines of business
- Implementation planning for org strategy, licensing and limitations
- Enabling Agentforce Financial Services features through Salesforce Go
- Timeline for a chronological view of client history
- Flexible Hierarchies versus ARC and account hierarchies for business structures
- Life Events and Business Milestones for client engagement planning
- Interest Tags for capturing client needs and interests
- Record Alerts and contextual alerts for client issues that need attention
- Integrated onboarding with Discovery Framework and the KYC data model
- Service Process Automation for standardized banking service requests
- Experience Cloud sites and portal templates for client and partner self-service
- Document generation, tear sheets and e-signature for client documents
- Salesforce Scheduler and Virtual Calls for client appointments
- Interaction Summaries for client meeting notes
- Financial Deal Management enablement, settings and user access
- Claims Management across the insurance claim lifecycle
- Integration tooling for core systems and legacy data
- Future-state process scope by input and outcome
- Choosing the first process to map
- Process map governance and adoption standards
- Moving from current-state maps to a validated future-state design
- Shared versus business-line-specific lifecycles with record types and business processes
- Security requirements from regulations, critical assets and threat models
- Object, field and record-level access layers for client data
- Persona-based permission sets and field-level security for sensitive client fields
- Record-level sharing baseline and mechanisms for client data
- Access inheritance across person accounts, households and financial accounts
- Shield Platform Encryption versus Classic Encryption for client data
- Event Monitoring and Field Audit Trail for regulatory oversight
- Consent Management for client data use and contact preferences
- Identity Verification before disclosing client financial data
- Territory management versus the role hierarchy for geographic coverage
- Territory model building blocks and setup sequence
- Territory model states, previews and activation
- Territory user access levels and parent-child inheritance
- Territory assignment rules for client accounts and leads
- Manual versus filter-based opportunity territory assignment
- Enabling multiple currencies and its org-wide impact
- Advanced Currency Management and dated exchange rates
- Multi-currency limitations in Agentforce Financial Services components
- Multi-language design with Translation Workbench and user language settings
- INVEST checks before prioritising and sizing stories
- Backlog refinement and team review of work-ready stories
- Product backlog prioritisation by business value and MVP scope
- Sizing, estimating and splitting user stories for sprints
- Sequencing dependent Agentforce Financial Services stories across sprints
- Sprint planning and sprint backlog selection by priority and capacity
- Legacy system landscape assessment and source-to-target mapping
- Historical data scope and migrate-versus-integrate decisions
- Data cleansing and deduplication before migration
- Choosing a data load tool for Agentforce Financial Services migrations
- External IDs and upsert for preserving record relationships
- Agentforce Financial Services Data Loader upload sequence
- Household records and individual-to-household relationships in data loads
- Transforming the individual model to person accounts
- Managed package to standard data model migration planning
- Protecting rollup and calculated fields during financial data loads
- Large data volume load preparation and performance
- Trial loads, validation and reconciliation of migrated data
- When to use Financial Services Initial Setup in Salesforce Go
- Managed package installation and unmanaged extension packages
- Person accounts versus the legacy individual model at setup
- Recommended next steps after Financial Services Initial Setup
- Household member roles on the Account Contact Relationship
- Redirecting account and contact links to individual and group profiles
- Opportunity Stage values for tracking client opportunities
- Document Tracking and Approvals setup with document checklist items
- Profiles versus permission sets for default settings and access
- Permission set licenses for Agentforce Financial Services users
- Persona-based user provisioning with profiles and permission sets
- Profile record type defaults and field-level security for advisor personas
- Permission set groups and user access policies for persona access at scale
- Omnistudio designer, runtime and site user permissions
- Lightning record pages and apps tailored to financial services personas
- Page layouts and global actions for client and household records
- Org-wide defaults and role hierarchy as the baseline for client data
- Owner-based versus criteria-based sharing rules
- Compliant Data Sharing versus core sharing mechanisms
- Org setup to turn on Compliant Data Sharing for an object
- Configure versus Use Compliant Data Sharing permissions
- Participant roles and the access levels they grant
- Sharing a record through Account and Opportunity Participant records
- Participant groups for teams that share a record role
- Compliant Data Sharing on custom objects and mixed public and private records
- Deactivating users who hold Compliant Data Sharing assignments
- Confidential Interaction Summaries and restricted sharing
- Managed package versus standard Financial Account objects
- Enabling Financial Account Management standard objects for users
- Balance and address records in the standard financial account model
- Varying financial account details by account type without record types
- Transitioning from managed package to standard Financial Account objects
- Extending the delivered data model versus building custom objects
- Identity verification process definitions and flow templates
- Intelligent Form Reader setup, document templates and field mapping
- Choosing an integration option for external financial data
- Dedicated integration users per external system
- Salesforce Integration user license and API-only profile
- Extending integration user access with permission set licenses and permission sets
- Integration user access to Financial Account standard objects
- Integration field mapping for required fields, data types and picklist values
- External ID fields for matching integrated records
- Translating user story success criteria into report requirements
- Matching report metrics to stated business outcomes
- Prebuilt reports and dashboards from extension packages and dashboard packs
- Prebuilt analytics apps and dashboards for financial services personas
- Custom report types for Agentforce Financial Services objects
- Report formats and summary formulas for success criteria metrics
- Dashboard components for tracking progress against targets
- Dashboard running user versus dynamic dashboards and filters
- Report and dashboard folder sharing versus record-level access
- Rolling out dashboards to stakeholders and validating success criteria
- Salesforce Flow toolset selection for approvals, integrations and recommendations
- Choosing a flow type and trigger for a business event
- Flow planning and design best practices for maintainable automation
- Record-triggered Flow versus Apex for complex or high-volume automation
- Flow versus Flow Orchestration for multi-team financial processes
- Flow Orchestration stages, steps, conditions and work item assignment
- Migrating Workflow Rules and Process Builder to Flow
- Omnistudio component selection for a delivered design
- Omnistudio Omniscripts versus Screen Flows for guided forms
- Integration Procedures and Integration Definitions in automated processes
- Business Rules Engine decisioning within automation
- Data Processing Engine and Batch Management for high-volume processing
- Action plan templates for repeatable client task sequences
- Choosing a household data model and setup approach
- Reciprocal roles and inverse relationship records
- Party Relationship Group for non-household client groups
- New ARC versus Original ARC for relationship graphs
- ARC permission set and user access setup
- Building ARC graphs from templates and node relationship types
- ARC node names, display fields and actions
- Placing ARC components on record and Experience Cloud pages
- Household visualization with Relationship Map or ARC household graph
- Financial account ownership and flags that drive household rollup totals
- Record Rollups versus Record Rollup Definitions
- Record rollup definition source, target and join path design
- Rollup By Lookup rules versus Financial Summary Rollup
- Custom household aggregates with delivered rollup tooling
- Lead record types for financial services prospect segments
- Lead Status values and Lead Processes for financial services pipelines
- Lead queues for advisor teams that share prospect workloads
- Lead assignment rule entries, evaluation order and fallback owner
- Lead capture channels and when assignment rules apply
- Referral management on the Lead object
- Assigning leads to sales territories
- Converting qualified leads into Individual client records
- Mapping custom lead fields for lead conversion
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Salesforce Accredited Agentforce Financial Services Professional studiers. 757 members and growing.
Pick a concept to study
Select any concept from the checklist to read its explainer, sources, and practice question.