Agentforce Financial Services uses Individual Record Type Mapper custom metadata to map custom individual record types to the appropriate Account and Contact record-type architecture. This allows an organization to differentiate individual personas such as customers and independent advisors while preserving Financial Services behavior that depends on correctly identifying those records as individuals.

The administrator first creates and enables the required Person Account record types. The administrator then opens the Individual Record Type Mapper custom metadata and creates or updates the appropriate mapping records, specifying the record type used for each individual classification.

This metadata is important because Agentforce Financial Services components and processes need to know which Account record types represent individuals. Additional mapping records can be created when an organization has multiple person-oriented business roles that require different page layouts, processes, or referral behavior.

Creating custom fields does not establish record-type semantics. A Contact record type alone is insufficient because Person Accounts are represented through the Account architecture with associated Contact behavior. Likewise, a generic custom setting is not the mechanism used to distinguish the two requested Person Account types.

The correct configuration is therefore to create the necessary Person Account record types and define their corresponding Individual Record Type Mapper metadata.