Person accounts versus the legacy individual model at setup
Key Takeaway
New Agentforce Financial Services installations start on person accounts. You can't disable person accounts after you enable them, so preview the change in a sandbox first.
Agentforce Financial Services can represent a client who is a person in two ways: person accounts or the older individual model. The choice you make at setup affects migration, which features you can use, and what you can undo later.
Two ways to represent a person
A person account stores information about a person by combining certain Account and Contact fields into a single object experience. To end users, a person account record looks and works as one record.
The individual model uses the standard Account and Contact objects, coupled in a unified object view of a person. Agentforce Financial Services extends those objects with additions such as custom fields and record types.
Person accounts are the Salesforce platform solution for B2C activities. For most organizations, person accounts provide better support for B2C activities. Salesforce supports the individual model only for orgs with existing individual model implementations.
If you're setting up a trial org or a new installation...
Agentforce Financial Services enables person accounts, so the implementation starts on person accounts.
If your org already runs on the individual model...
Salesforce still supports the individual model for your org. You can also migrate your org to person accounts.
If your org already uses person accounts outside Agentforce Financial Services...
You may be able to upgrade to Agentforce Financial Services without migrating to a new org. Your account manager can confirm this option.