AP-208 Salesforce Accredited Agentforce Financial Services Professional Questions and Answers

Compliant Data Sharing has specific behavior when an Opportunity is changed to Private. A private Opportunity cannot be shared through Compliant Data Sharing, so Salesforce removes the sharing entries that previously granted participant-based record access.

Salesforce documents that when an Opportunity contains Opportunity Participants with associated share-table records and the Opportunity is made Private, the share-table records are deleted. However, the Opportunity Participant records themselves remain in Salesforce.

This distinction is important because the participant record represents the business relationship or participation assignment, while the share-table record represents the actual access grant generated by Compliant Data Sharing. Setting the Opportunity to Private removes the access mechanism without automatically destroying the participant data.

Salesforce recommends removing participants before making an Opportunity private when appropriate. If an Opportunity is subsequently made shareable again, the participant may need to be recreated or toggled inactive and then active so that the required sharing entry is regenerated.

Therefore, manual deletion of the share-table entries is unnecessary. Salesforce performs that cleanup automatically, while preserving the underlying participant records.

Action Plans and Action Plan Templates are designed for repeatable, controlled business processes that contain tasks and supporting-document requirements. An Action Plan Template defines the standard sequence once, including task ownership, due dates, dependencies, and document checklist items. Each onboarding engagement can then instantiate an Action Plan from that approved template.

Salesforce positions Action Plans as a mechanism for capturing repeatable tasks and automating task sequences so that teams execute processes consistently. Action Plans can automatically assign owners and deadlines and provide reporting for monitoring progress and compliance.

The feature also supports Document Checklist Items, which is directly relevant to the KYC requirement. Action Plans and templates manage repeatable manual work, while Document Checklist Items enable reviewers to track required documentation and its approval status.

Chatter reminders provide communication but do not establish a controlled repeatable process. A custom trigger would unnecessarily duplicate declarative Financial Services capabilities and increase maintenance. Generic flow templates may automate individual operations but do not provide the same reusable combination of predefined tasks, owners, dates, document requirements, tracking, and reporting. An Action Plan Template therefore provides the appropriate standardized control for ensuring onboarding tasks are consistently performed.

Agentforce Financial Services provides purpose-built objects for modeling customer financial information beyond standard CRM records. Among these are Financial Goal, Financial Holding, and Revenue.

The Financial Goal object represents objectives such as retirement funding, purchasing a home, education planning, or other target financial outcomes. A Financial Holding represents investments or securities held within a financial account. Salesforce references Financial Holding throughout Financial Services capabilities, including financial-detail and portfolio-performance functionality that operates on Financial Account, Financial Account Role, Financial Holding, Financial Goal, and related client records.

The Revenue object is also part of the Financial Services financial model and represents revenue generated from operating a person ' s financial account or through advisory services.

These objects complement other specialized Financial Services records such as Financial Account, Assets and Liabilities, and Identification or Identity Document, allowing institutions to construct a comprehensive view of a client ' s financial position and objectives.

Billing is associated with separate financial or insurance servicing capabilities rather than being one of the client financial-information objects represented by this question. Inheritance likewise is not the corresponding packaged FSC financial object.

Current Agentforce Financial Services identity-verification architecture relies on Flows or Screen Flows and OmniStudio to guide service representatives through caller verification and integrate with verification services.

Salesforce provides identity-verification flow templates for call-center scenarios. A Verify Customer Identity flow can be added to an Engagement Interaction Lightning record page so an agent can launch a structured verification process while handling the customer ' s interaction. Salesforce also supplies Flow Screen Components for customer search and identity verification, enabling administrators to build Screen Flows tailored to the organization ' s verification requirements.

OmniStudio provides the complementary guided experience and integration architecture used throughout Agentforce Financial Services. External identity-verification requests can be initiated from a Flow or from an Integration Procedure inside an OmniScript, enabling secure orchestration with third-party identity-verification and AML providers.

Process Builder is not the appropriate current architecture for new process automation; Salesforce ' s modern implementation model centers on Flow. Discovery Framework focuses on assessments, questionnaires, and onboarding data collection rather than being the principal call-center identity-verification user experience.

Accordingly, Screen Flows and OmniStudio provide the guided interaction and integration capabilities required to build a modern identity-verification process.

Agentforce Financial Services supports localization across a number of languages, but certain packaged assets remain English-only. Two important implementation considerations are the packaged flows and the predefined reciprocal relationship roles.

Salesforce identifies Financial Services packaged flows as being available only in English. This is important during solution design because organizations operating across multiple countries may need to account for localized user guidance, labels, or alternative process experiences where packaged flows are exposed directly to users. Salesforce otherwise provides localization for multiple languages, although several packaged labels and components also have documented localization constraints.

Predefined reciprocal roles likewise use English values. Reciprocal roles are fundamental to relationship modeling because they define both sides of a relationship—for example, Spouse/Spouse, Parent/Child, or Business/Proprietor. Organizations requiring localized terminology can plan appropriate configuration rather than assuming the packaged role vocabulary automatically translates.

The other choices are overly broad. Agentforce Financial Services does support localization across many areas, and custom component labels can generally be managed through Salesforce configuration and translation mechanisms. The key design principle is to identify packaged content with language restrictions early, especially when conducting discovery for multinational implementations, so localization work can be incorporated into the implementation scope.

Interest Tags use Salesforce Topics infrastructure, but reporting begins with a custom report type whose primary object is Tag Categories. Salesforce states that Interest Tags are represented through Topics, so a report that surfaces Interest Tags must include the Topics object.

The administrator first creates a custom report type and selects Tag Categories as the Primary Object. Topics is then added as the related object. This relationship allows the report to group Interest Tags under their configured categories and display details such as the topic name, description, and the record to which the Interest Tag is assigned.

Option C reverses the required report-type relationship because Topics is not the primary object in Salesforce ' s documented Interest Tags report configuration. Option D is also inaccurate in its stated implementation. To limit results to tags assigned to a particular Salesforce object, administrators can use the record key prefix rather than simply choosing an object name from a generic filter.

This reporting architecture provides structured analysis of customer interests while retaining the Tag Category hierarchy used to organize Interest Tags. Therefore, the correct considerations are to report through Topics and make Tag Categories the primary object in the custom report type.

Interaction Summary is designed specifically for structured client and partner meeting documentation in Agentforce Financial Services. It enables bankers and advisors to record detailed meeting information, capture attendees, specify confidentiality, document next steps, and selectively share sensitive notes with the appropriate stakeholders.

Salesforce describes Interaction Summaries as providing structured note-taking together with compliant, role-based data sharing. Users can create an interaction summary associated with an interaction, while the Interaction Attendees capability allows attendees to be viewed and managed.

When creating an Interaction Summary, bankers and financial advisors can take detailed meeting notes, define the confidentiality level, add action items or next steps, and ensure that notes containing confidential information are shared only with relevant stakeholders. The underlying data model includes Interaction for the meeting itself, Interaction Attendee for participating people, Interaction Summary for the notes and confidentiality information, and Interaction Summary Participant for sharing.

A normal Event is primarily a calendar or activity construct, while standard Notes do not provide the complete Financial Services interaction and compliant-sharing model. Interaction Summary therefore directly aligns with every element of the requirement.

A transformation from the individual account model to Person Accounts is a significant data-model change and must be approached with strong data-protection controls. The implementation team should therefore prioritize a complete data backup before changing or converting existing customer records.

Salesforce ' s conversion guidance includes performing a backup as a core prerequisite in the transformation sequence. The process ultimately changes individual Account and Contact records into Person Account records, and Salesforce emphasizes that the transformation must first be tested carefully because the Person Account model cannot simply be disabled after it has been enabled.

Salesforce also recommends creating a sandbox to assess how Person Accounts affect the organization ' s technical architecture, integrations, automation, components, reports, and customizations. However, from a migration-risk perspective, preservation of the existing production data is fundamental before irreversible data transformation activities are performed.

Subsequent implementation activities include enabling Person Accounts, enabling them for Agentforce Financial Services, configuring record types through the Individual Record Type Mapper, validating source records, and executing the conversion. These activities depend on careful preparation. A reliable backup provides the implementation team with an authoritative pre-migration data state and should therefore be treated as a top planning priority.

This quoting process requires three distinct capabilities: guided data collection, business-rule execution, and server-side orchestration. OmniScripts, Business Rules Engine, and Integration Procedures provide those capabilities declaratively.

An OmniScript supplies the guided web experience. It can collect contact information, address details, driver age, vehicle model, vehicle year, and other inputs through a structured multi-step interface. OmniScripts are specifically designed for interactive, guided business processes.

Business Rules Engine performs the insurance rating logic. User characteristics can be passed to an expression set and decision matrix; the rules locate applicable rating factors, perform calculations, and return the resulting premium quote.

An Integration Procedure orchestrates server-side processing. It can receive values from the OmniScript, invoke Business Rules Engine components, interact with external services when necessary, and create or update Salesforce records without requiring multiple client-server round trips. Salesforce supports calling expression sets and decision matrices from both OmniScripts and Integration Procedures.

FlexCards are primarily used to display contextual information rather than to implement the complete quoting workflow. Custom Apex is unnecessary where the required capabilities are available declaratively through OmniStudio and BRE.

An External ID provides the correct mechanism for matching Salesforce records with identifiers maintained by another application. It is a custom field marked with the External ID attribute and typically stores the unique identifier assigned to a record by a core banking system, ERP platform, policy system, loan-origination system, or another external data source.

Salesforce import tools can use External IDs to identify existing records. When a record in an incoming file contains an External ID that matches an existing Salesforce record, the import process can treat the records as corresponding records rather than blindly inserting another copy.

External IDs are also fundamental to upsert operations. The integration supplies the External ID, Salesforce searches for a matching value, and the operation updates the matching record or creates a new record when no match exists. For the strongest duplicate control, the field can additionally be configured as Unique, ensuring that the same external identifier cannot be stored on multiple records.

User ID, Org ID, and Data Load ID do not provide the required source-system record-matching mechanism. External ID is therefore the appropriate integration identifier.

A Financial Services household can have only one Primary Member. Both Oliver and Macie have Primary Member enabled, which violates this household-modeling rule and causes the configuration error.

Salesforce household guidance states that designating a primary member is optional, but a household can have only one primary member. The primary member commonly represents the principal client or primary relationship within the household. Other members receive roles that describe their relationship to that primary member, such as Spouse or Dependent.

The other settings shown are valid. Multiple members can designate the same household as their Primary Group. Primary Group identifies the household to which a person ' s qualifying records and activities should roll up. A spouse can be a valid relationship role, and multiple household members can have their eligible activities and financial information summarized to the same primary household.

The advisor should therefore retain one individual—typically the principal client—as Primary Member and clear Primary Member for the spouse while leaving the appropriate relationship and Primary Group settings in place.

Agentforce Financial Services group-level record rollups aggregate qualifying records belonging to members of a Primary Group so advisors can see consolidated household information. Salesforce ' s supported-object matrix includes Tasks, Financial Accounts, and Opportunities.

Financial Accounts are surfaced through financial-account components at the group level. Once group rollups are enabled and the financial account is associated with a member of the Primary Group, the household-level experience can present the aggregated account information.

Tasks are displayed within the Activities related list at the group level. This enables advisors to review relevant work and interaction activity across household members from the household context.

Opportunities are also supported and appear in the Household Opportunities related list. Opportunities can require additional configuration in managed-package implementations, such as adding the appropriate value to the Rollup__c field on Account Contact Relationship.

Alerts and Action Plans are not included in the documented group-level record-rollup object set tested here. They have their own data structures and visibility mechanisms.

Thus, the supported choices are Tasks, Financial Accounts, and Opportunities.

Relationships between two business accounts are modeled through Account-Account Relationships, with reciprocal relationship definitions specifying the role each account plays relative to the other. Therefore, the administrator should create the appropriate Account Reciprocal Role rather than simply adding an arbitrary value to a relationship-object picklist.

Salesforce Financial Services relationship modeling supports connections among households, businesses, trusts, professional organizations, and other entities. Reciprocal roles describe the meaning of each side of a relationship—for example, Proprietor and Business, or another organization-specific pair. Salesforce provides commonly used reciprocal role records and permits administrators to configure additional roles when the packaged options do not represent the organization ' s business relationships.

The Account-Account Relationship object is the structural record that relates business accounts, while the relationship-role definition supplies the semantics of that relationship.

Account-Contact and Contact reciprocal roles apply to relationships involving contacts or individuals, so they do not satisfy a two-business-account requirement. The proper configuration is therefore a new Account Reciprocal Role.

The bank should replace spreadsheet-driven processing with Salesforce ' s standard mortgage flow templates and use Flow Builder to customize the mortgage journey according to the bank ' s requirements.

Salesforce installs mortgage flows as standard Flow templates. Administrators can create a new Flow based on a standard mortgage template, customize its screens and processing logic in Flow Builder, save the resulting implementation, and activate it for users. Mortgage templates support borrower information, assets and liabilities, and related mortgage processes.

This approach moves data capture into a controlled Salesforce process rather than repeatedly importing spreadsheets. Guided flows can collect borrower information consistently, enforce required fields, perform validation, invoke automation, and write information directly to the supported mortgage data model.

Creating a new custom Mortgage Application object is unnecessary because Agentforce Financial Services already provides dedicated mortgage application capabilities and associated data structures. Building duplicate custom objects would increase maintenance and complicate integration with standard Financial Services functionality. Similarly, Data Import Wizard merely transfers existing spreadsheet information into Salesforce and would leave the underlying manual collection process largely unchanged.

Combining standard mortgage templates with Flow Builder gives the organization a reusable, maintainable, and declarative solution that improves efficiency while retaining flexibility to customize the mortgage process.

Salesforce defines strict prerequisites for converting the Individual Account model to Person Accounts because the transformation changes the underlying representation of the customer.

Each Account being converted can have only one Contact record through a single direct Account Contact Relationship. Salesforce also requires that the Account must not be the parent of any other Account. The Parent Account field must be blank, and no other Account can reference the converting Account as its parent.

Additional prerequisites include matching Account and Contact owners, matching currency values where applicable, a blank Reports To field on the Contact, and ensuring no other Contact reports to the converting Contact. These controls prevent relationship structures that cannot be represented correctly after the Account and Contact become a Person Account.

The conversion must also be thoroughly tested in a sandbox. Salesforce recommends previewing how Person Accounts affect technical architecture and customizations and instructs organizations to execute the transformation in a sandbox first because migration to Person Accounts is effectively irreversible.

Neither a blank Account Phone field nor Opportunity ownership reassignment is a documented conversion prerequisite. Therefore, the required preparations represented here are C, D, and E.

The appropriate object is Identity Document. Drivers ' licenses and passports are formal identity credentials and should be represented using a structured identity-document model rather than as generic checklist or received-document records.

Salesforce uses Identity Document terminology throughout its identity-document processing capabilities. Intelligent Document Reader and related onboarding capabilities can extract structured information from uploaded passports and driver ' s licenses by treating them as identity documents.

Modeling identity credentials explicitly allows an implementation to distinguish personally identifying documentation from ordinary supporting documents used in onboarding, underwriting, servicing, or compliance workflows. Identity-document information can then participate in identity verification, KYC, onboarding, and related Financial Services processes.

A Document Checklist Item serves a different purpose: it tracks whether a required document has been requested, received, reviewed, or otherwise processed as part of a checklist. It does not itself represent the customer ' s identity credential as the principal identity-data entity. Similarly, generic received or resolved document structures address document workflow rather than the semantic representation of the identity credential.

Therefore, when migrating customer information associated with passports and driver ' s licenses, Identity Document is the Financial Services object aligned to the identity-document use case.

The correct design uses Salesforce ' s Organization-Wide Defaults to establish different baseline visibility for customer records and sensitive financial records.

Person Accounts should have Public Read Only visibility so that users who have the required object-level permissions can view customer records throughout the organization. Public Read Only allows records to be viewed broadly while preventing unrestricted modification.

Financial Accounts contain sensitive information such as deposit accounts, investment accounts, loans, mortgages, credit cards, and other financial relationships. Their OWD should therefore be Private. With Private sharing, users do not automatically gain access merely because they can access the Financial Account object. Access can subsequently be expanded only to authorized users through record ownership, role hierarchy where appropriate, sharing rules, teams, manual sharing, Compliant Data Sharing, or other approved mechanisms.

Setting Financial Accounts to Public Read Only would expose them broadly and directly contradict the privacy requirement. Likewise, removing a Financial Accounts tab or component from a Lightning page is not a security mechanism. A user who retains record access could still retrieve the information through reports, search, APIs, related lists, or another Salesforce interface.

Therefore, Public Read Only for Person Accounts and Private for Financial Accounts provides the appropriate least-privilege foundation.

Chatter components in Lightning App Builder depend on Feed Tracking being enabled for the underlying object. Therefore, if the administrator edits the Action Plan Lightning record page before enabling feed tracking for Action Plan, Chatter-related components are not presented as available components.

Salesforce guidance states that Chatter Publisher, Chatter Feed, and Chatter components can be absent from Lightning App Builder when Feed Tracking is not enabled for the object. Once the administrator enables Feed Tracking through Setup, Feed Tracking, the Chatter components become available for placement on the object ' s Lightning record page.

Feed tracking serves two related purposes. It enables users to follow activity associated with a record, and it provides the object-level capability required for the Lightning Chatter feed experience. Salesforce supports configuring feed tracking for custom and managed-package objects where the feature is available.

This is independent of whether the administrator personally has the Action Plans permission set. The absence of the component in Lightning App Builder is a configuration issue rather than a user entitlement issue. Nor is there a separate Action Plan-specific Chatter switch that replaces standard Feed Tracking. Once Feed Tracking is enabled for Action Plan, the administrator can return to Lightning App Builder and add the required Chatter component.

Actionable Relationship Center supports object-specific related lists so users can inspect relevant information without leaving the relationship graph. For the Account object, supported lists include Client Financial Goals, Household Financial Accounts, and Cases, making A, C, and D correct.

Salesforce ' s ARC documentation lists supported Account-related lists that include Household Financial Accounts, Household Financial Goals, Household Opportunities, Household Referrals, Financial Account Primary Owner, Client Financial Goals, Household Assets and Liabilities, Client Assets and Liabilities, Related Leads, Opportunities, and Cases.

The distinction between Account and other ARC-supported objects is important. Financial Holdings appears as a related-list option for the Financial Account object, not Account. Similarly, Notes and Attachments is supported for objects such as Contact, Lead or Referral, Opportunity, Asset and Liability, and Financial Holding, but it is not listed among the supported Account related lists in the ARC configuration matrix.

ARC can display up to ten related lists that have appropriate compact-layout configuration, and their display order follows the associated object ' s page-layout arrangement. This allows financial advisors to move from a high-level relationship visualization directly into relevant client financial goals, household account holdings, service cases, and other supported records.

The Life Events experience is intended to turn significant customer events into actionable advisor workflows rather than merely display historical information. Within the supplied Financial Services curriculum, the advisor actions represented are Create Lead and Referral, Request Record Approval, and Create Opportunity.

Salesforce ' s Events and Milestones architecture implements this behavior through contextual actions. Administrators can create actions on the Person Life Event object and expose those actions in the expanded event card. This allows an advisor to act immediately when a life event indicates a new service need, sales opportunity, referral opportunity, or internal process requirement.

For example, a life event can signal a need that should become an Opportunity, a requirement that should be routed to another line of business through a Lead or Referral, or an internal decision that requires an approval action. The action is launched in the context of the customer and the life event, helping maintain traceability between the event and the resulting business process.

The exact available actions can be tailored by the organization through configuration. The core design principle is that Life Events should translate customer insight into timely, trackable advisor actions rather than remain passive informational records.

The consultant should use the packaged Insurance Flow Templates and associated guided insurance service processes rather than creating a custom user interface from scratch. Salesforce ' s insurance capabilities provide prebuilt guided processes that standardize common policy-servicing activities and reduce the amount of manual navigation and data entry required by service representatives.

Current Agentforce Financial Services documentation continues this architecture through prebuilt insurance service-process templates. These templates provide ready-made process attributes, intake forms, and fulfillment flows and are intended to accelerate insurance service delivery across assisted and self-service channels.

Premium-payment servicing is a concrete example. Salesforce supplies guided processes in which an agent selects the active policy, reviews the current premium due date and frequency, selects the new payment frequency and effective date, and submits the change through an OmniScript. Insurance policy processes similarly use OmniScripts to guide users through payment-plan information and payment-frequency selection.

This packaged approach is preferable to custom Lightning web components because it reduces development and maintenance while enforcing consistent data capture. An Action Plan manages tasks and deadlines but does not replace a guided data-entry process for updating beneficiary or premium-payment information.

Compliant Data Sharing is designed for financial-services organizations that must provide narrowly controlled record access based on business participation, regulatory responsibilities, or compliance requirements. It enables a record owner or appropriately authorized participant to grant access to individual internal users without broadly relaxing the organization ' s normal sharing model.

A CDS participant is an internal user assigned a Participant Role for a specific record. The Participant Role determines that user ' s access level. This allows organizations to grant access to legal counsel, compliance personnel, specialists, or deal-team members only when they are involved in a particular record.

This model directly addresses the scenario because a legal or compliance user may not normally have access through Account ownership, role hierarchy, or routine business engagement. CDS creates the required exception on the relevant record while leaving the overall sharing architecture restrictive.

Traditional sharing rules generally grant access based on broader owner- or criteria-based populations and are less suitable for ad hoc participant-specific regulatory access. Business Rules Engine evaluates business logic rather than record security. Interaction Summaries capture client-interaction information. Therefore, Compliant Data Sharing is the Financial Services capability that directly satisfies the security requirement.

Salesforce Insurance Claims Management supports the complete post-loss claims lifecycle, including reserve management, payment processing, and automated adjudication. These processes operate after a covered loss has occurred and are central to evaluating, funding, and settling a claim.

Reserve Management enables adjusters to establish and modify reserves representing expected future claim exposure. The claim workspace consolidates coverages, reserves, loss items, expense items, and other claim financial information so adjusters can assess current and projected financial exposure.

Payment is another core Claims Management process. Adjusters can create payment details and issue payments while Salesforce validates applicable policy limits and updates the corresponding claim-financial records.

Auto Adjudication applies configured rules and policy information to automate claim-processing decisions where appropriate. This reduces manual handling for qualifying claims and supports straight-through processing.

Quoting belongs to the pre-policy acquisition process, while underwriting evaluates risk before coverage is issued. Those functions are part of other insurance lifecycle capabilities rather than Claims Management. Claims Management therefore centers on Reserve Management, Payment, and Auto Adjudication.

A Custom Relationship Group is the appropriate construct when several people or organizations participate in a meaningful business grouping that is not accurately represented as a permanent household or a single legal business entity.

Agentforce Financial Services groups are designed to represent a customer ' s broader financial circle and can aggregate information across participating members. The group model can be extended through custom group record types when the standard Household model does not match the business requirement.

In this scenario, the farmers continue to operate independently but collaborate seasonally or for a limited period. Representing the collaboration as one Business Account would incorrectly imply that they constitute a single organization. A standard Household is also inappropriate because the collaboration is commercial rather than a family unit. Contact-Contact Relationship can model a direct relationship between two people but does not provide the group-level construct required for several cooperating farms and farmers.

A customized relationship group can therefore represent the temporary collaborative business operation while keeping each farmer and farm independently modeled and related to the group. This preserves each party ' s identity and financial relationships while allowing advisors to understand and service the collaborative arrangement as a meaningful business grouping.

The Mortgage Data Model connects the prospective borrower, financial position, and sales pipeline through Account, Assets and Liabilities, and Opportunity. These objects collectively provide the core CRM context required when Salesforce integrates with external loan-origination and onboarding platforms.

The Account represents the borrower or customer relationship and provides the customer context against which mortgage activity is tracked. Assets and Liabilities capture the applicant ' s financial position, including assets, debts, and other obligations, which is critical during mortgage qualification and underwriting. Opportunity represents the commercial pipeline component. Financial Services uses standard Leads and Opportunities to represent prospects and opportunities to provide customers with financial products.

Using Opportunity allows mortgage activity to participate in normal pipeline tracking, stages, reporting, and forecasting while the dedicated mortgage objects maintain detailed application information. Financial Account represents an established financial product relationship rather than the primary pre-origination pipeline object. Case is intended for service and support management.

Consequently, Account, Assets and Liabilities, and Opportunity provide the appropriate surrounding objects for integrating mortgage origination and onboarding while accurately tracking prospective business through the pipeline.

Actionable Relationship Center is designed specifically to help Agentforce Financial Services users understand complex relationships among customers, households, businesses, trusts, contacts, and other related entities.

ARC presents these connections through an interactive relationship graph rather than requiring the wealth manager to interpret separate related lists manually. It can connect business accounts, Person Accounts, and Contacts and display relevant relationship information in the graph.

The Addams scenario is an ideal use case. The wealth manager needs to understand the wife ' s membership in the Addams Household, her spouse relationship, their shared connection to the Addams Charitable Trust, and her separate connection to the Symonds Household. ARC can visualize these multi-party relationships through Account Contact Relationship, Account Account Relationship, and Contact Contact Relationship junction objects.

ARC also supports configurable custom relationship graphs, record actions, node display fields, details panels, highlights panels, and preconfigured Financial Services templates.

Tableau and Marketing Cloud Intelligence provide analytics and visualization capabilities but are not designed to present the operational Financial Services relationship graph directly within the advisor workflow. ARC provides the relationship context needed to understand spheres of influence, recognize connections, and identify potential service or business opportunities.

An Action Plan is the appropriate Agentforce Financial Services capability when an organization has a standardized sequence of activities that must occur at defined intervals and needs those activities to remain visible and reportable in Salesforce. Action Plan Templates define repeatable tasks, task ownership, sequencing, and date offsets. When an Action Plan is instantiated, those template items become operational tasks that relationship managers can complete and track.

In this scenario, the meaningful business event is the customer ' s transition to an established Customer state after opening the first banking relationship. That event should initiate an Action Plan containing follow-up tasks scheduled at the required 2-day, 2-week, and 2-month offsets. This accurately aligns the operational workflow with the point at which the individual becomes a customer.

Simple email notifications do not provide the same task lifecycle, completion status, ownership, reporting, and dashboard capabilities. Similarly, triggering the plan at initial Account creation or lead conversion could occur before the required customer milestone. Salesforce specifically positions Action Plans for repeatable engagements such as account openings and allows task deadlines and ownership to be standardized while supporting reports and dashboards for progress monitoring and compliance.

Agentforce Financial Services supports this requirement through Unique event types. Events and Milestones provide advisors with an at-a-glance view of significant customer life events and business milestones so that they can understand changing client needs and identify timely engagement opportunities.

For an event that should logically occur only once for a customer, the administrator can mark its Event Type as Unique. Salesforce specifically states that this setting is intended to prevent users from accidentally creating more than one occurrence of the same unique event type.

The configuration is performed on the Person Life Event object ' s Event Type field. The administrator edits the relevant picklist value and selects Unique. Business milestones can be configured similarly by working with the appropriate milestone type. Salesforce also supports activating or deactivating event types, hiding sensitive events, defining contextual actions, changing icons, and controlling the details displayed when users interact with an event or milestone.

Once-in-a-Lifetime, Special, and Single are not the Salesforce configuration designation tested here. The supported mechanism is explicitly the Unique setting.

Interest Tags enable Financial Services users to categorize customer interests and associate those interests with supported records, including Interaction Summaries. Access is controlled through specific Financial Services permissions rather than being universally included in every Financial Services permission set.

Salesforce identifies Financial Services Cloud Extension and Financial Services Cloud Foundations as permission sets that provide the relevant Interest Tags capabilities. Current Salesforce documentation lists these permission sets among those used in Financial Services for access to Interest Tags functionality.

Salesforce also states that users who add Interest Tags to Interaction Summaries require appropriate Financial Services access, including Financial Services Cloud Extension or Financial Services Cloud Foundations, depending on the product configuration. Before users can work with the feature, administrators must also enable Topics and Interest Tags and configure the relevant object for Topics.

Cloning one of these permission sets provides an appropriate baseline when an organization needs a specialized permission set while retaining the required Interest Tags permission. The Financial Services Cloud Standard and Basic permission sets serve other user-access patterns and do not constitute the specified source permission sets for this capability. Therefore, Extension and Foundations are the appropriate permission-set templates.

Flow Orchestration structures complex, multi-user business processes by organizing work into Stages and Steps, with Work Items representing the executable assignments created for interactive steps. A Stage groups related work into a logical phase and controls when the orchestration can progress to the next phase. Steps reside within stages and can execute sequentially or concurrently depending on the process design. Salesforce supports interactive, background, and MuleSoft steps.

When an interactive step becomes active, Salesforce creates an Orchestration Work Item and assigns it to the designated user, group, or queue. The assignee completes the associated Screen Flow through the Orchestration Work Guide. Work Items therefore operationalize the human work represented by interactive steps and provide assignment, completion, and tracking information.

Current Salesforce terminology formally describes Stages and Steps as the building blocks of an orchestration, while Work Items are generated during orchestration runtime. The terminology in this question uses the broader architecture in which Steps, Stages, and Work Items constitute the three operational elements being tested. Processes and Blocks are not defined Flow Orchestration structural elements.