Person accounts versus the individual model for individual clients
Key Takeaway
In a new Agentforce Financial Services org, model individual clients as person accounts, not with the individual model.
Agentforce Financial Services can represent an individual client in two ways: as a person account or through the individual model. A person account presents each person as one record and is the model for new orgs. The individual model pairs a standard Account with a standard Contact. Salesforce supports the individual model only for orgs that already use it. Your choice affects how you link people to households and to each other, which tools your users can use, and whether you need to plan a migration.
Two ways to represent a person
Salesforce's default setup is built for business-to-business (B2B) work. Organizations are tracked as Accounts, and the people you engage are tracked as Contacts. The individual model grows out of that default setup. Financial institutions deal with both organizations and individuals, so they need a different data model.
| Person accounts | Individual model | |
|---|---|---|
| Objects used | Certain Account and Contact fields, combined into a single object experience | The standard Account and Contact objects, used together |
| What end users see | One record | A unified object view of a person |
In the individual model, the standard Account and Contact objects are extended with items such as custom fields and record types.