Agentforce Financial Services models referrals through the Lead object, so a requirement for another referral variation should be implemented by creating an additional Lead record type rather than introducing a separate custom Referral object.
The administrator creates a new Lead record type using Referral as the basis, assigns an appropriate Lead Process, activates the record type, and makes it available to the required users. This allows the organization to define different required fields, page layouts, or referral experiences for the new type while remaining within the standard Financial Services referral architecture.
The administrator must then configure Referral Record Type Mapper custom metadata. The mapper connects the new Lead record type to Financial Services referral functionality by identifying the referral record type and enabling the packaged referral components to recognize it.
Assigning the record type to the relevant users is essential because users must have access to the new record type before they can select it during Lead or Referral creation. Updating a page layout may subsequently be useful, but it is not one of the three core configuration steps identified by the referral record-type procedure.
The correct implementation therefore uses the existing Lead and referral architecture: create the Lead record type, assign it to users, and create the corresponding Referral Record Type Mapper record.
