Considerations for Household Naming and Greetings

Which Household Members Are Evaluated

Household Naming evaluates only members whose Account Contact Relationship is on an account that has a Party Relationship Group where Type is Household. Household Naming includes an Account Contact Relationship in a household's mapped naming fields only if the record also has these settings.

• Select Active (IsActive).
• Don’t select Exclude From Household Automatic Naming (IsExclFrHshldAutoNaming).
• Select Included in Group (IsIncludedInGroup).

How Members Are Ordered in a Household Name

Household Naming orders the members in a household name in this priority.

• The member whose Account Contact Relationship has Primary Member (IsPrimaryMember) selected comes first, unless you exclude that member.
• Household Naming orders the remaining members according to the value in the Household Automatic Naming Sequence (HouseholdAutoNamingSequence) field on the Account Contact Relationship. This field overrides how names appear for a household.
• If the sequence is blank, Household Naming orders members by CreatedDate, from oldest first.

Ways to Exclude Members or Opt Out a Household

Default exclusions

Household Naming excludes any member whose Account Contact Relationship has Exclude From Household Automatic Naming (IsExclFrHshldAutoNaming) selected. It also excludes any member whose contact or person account has a value in the Deceased Date (DeceasedDate) field.

Exclusion formula

To exclude members based on your own criteria, complete the Exclusion Formula section of a naming or greeting template.

Whole-household opt-out

To opt an entire household account out of future naming updates, select Exclude From Household Automatic Naming (IsExclFrHshldAutoNaming) on the household's Party Relationship Group record.

Note Add the Exclude From Household Automatic Naming field to the page layouts for Account Contact Relationship and Party Relationship Group. If you use the Agentforce Financial Services New Household feature, add the field to the household configuration's list of available fields.

Field Access Requirements

To make sure that household naming works as expected, give users a minimum of read access to these fields.

Give users write access to any destination field that's mapped in an active Household Naming template. For example, give write access to the Account Name field or to a mapped custom field.

Considerations

• Changing the API value of, or deleting, a field that's referenced in a custom naming pattern or a template's Exclusion Formula can cause downstream errors.
• Turning on Household Naming and creating templates doesn't update existing households. To backfill household names, create an automation that calls the Recalculate Household Names invocable action.
• Automatic Household Creation uses a default name format if either of these is true. You didn't turn on Automatic Household Naming. You don't have an active household naming template that sets the Account.Name field as the destination. In these cases, the auto-generated household name format is {LastName} Household.