Choosing a household data model and setup approach
Key Takeaway
Households for Agentic Advisor works on both data models, lets users start a household with just the primary member, and creates inverse relationship records automatically. Without it or the managed package, you use the standard New Group flow, the ARC Relationship Graph component, and Financial Summary Rollups.
A household groups related clients, such as a family, so advisors can understand and serve them together. In Agentforce Financial Services you make two choices. The first is the data model: the managed package data model or the standard data model. The second is the setup approach: the existing Groups and Households setup or the configuration-driven Households for Agentic Advisor. Together, these choices decide which records represent a household, how relationship records get created, and how much setup work admins and users face.
When you need households
If your work focuses on individual clients, the Person Account object alone is enough. Households matter for services like wealth management, where understanding family relationships is critical. Groups and Households organizes customers into financial circles, household structures, and professional connections.
A household involves two kinds of people. Household members are part of the household, such as a spouse. Related contacts are outside the household but have a relationship with it, such as a client's attorney.