Study first
Review the ideas behind the questions
Review how CRM relationship data should mirror the customer relationship. Focus on contacts tied to more than one account, account hierarchy, buying committee roles, primary associations, labels, and team access.
Model the account relationship
Advanced CRM relationship work starts with deciding what the customer relationship really is, not with forcing every person into one flat account.
- A contact can have one direct account and other indirect account relationships when the business relationship is more complex.
- Relating one contact to multiple accounts can track business relationships without duplicate records.
- Separate location accounts can support ownership, hierarchy, sharing, and more granular reporting.
In Practice
Avoid duplicate people
If one buyer works with two accounts, model the relationships instead of creating two disconnected people.
Use hierarchy for the big picture
Location-specific accounts can keep local work clear while parent relationships preserve the enterprise view.
Common mistakes
Merging all branches into one global account because leadership wants one account total.
Keep separate accounts when ownership, access, reporting, or local interactions need separate context, then connect them with hierarchy.
Q&A
When is one contact tied to multiple accounts useful?
Use it when one person has real relationships with more than one account and a duplicate record would hide that context.
Why not use one global account for every location?
A single global account can make local ownership, sharing, reporting, and interaction tracking harder.
Make roles and primary links explicit
Relationship records become risky when automation or account planning assumes the wrong primary company or ignores who influences the deal.
- Associations connect CRM records and are two-way between the related records.
- A primary company can affect activity association, lifecycle syncing, segments, workflows, reports, and personalization.
- Opportunity contact roles show which contacts are involved, who is primary, and each person's role in the deal.
In Practice
Check primary before automation
If an automation or report uses the primary company, changing the primary link can change which account gets activity or lifecycle context.
Name the buying role
A deal with several stakeholders needs role context so sales knows who to contact and why.
Common mistakes
Adding every buying committee member as a note on the deal instead of relationship data.
Use contact roles or labeled relationships so the buying committee can be reviewed, filtered, and kept current.
Q&A
Why does the primary company matter?
It can be the relationship used by activity association, lifecycle syncing, reports, workflows, and personalization.
What should a buying committee review capture?
It should capture who is involved, who is primary when needed, and what role each person plays.
Govern labels before they drive work
Labels and limits can make relationship data useful, but they need governance before lists, workflows, or reports depend on them.
- Association labels describe the relationship between associated records.
- Association labels can be used in segments and workflow branches or actions.
- Association labels can have limits, including many records or a custom number of records.
In Practice
Set the limit to match the relationship
If a role should have only one active record, the relationship needs a limit or review rule before automation uses it.
Audit labels before deletion
A label that appears in records or tools should be removed from those assets before deletion.
Common mistakes
Creating a new label whenever a team wants a slightly different name.
Govern labels around real relationship decisions, because labels can drive segments, workflows, and reports.
Q&A
Why should relationship labels be governed before automation uses them?
Labels can affect which records enter segments or workflow paths, so weak labels can route work from weak relationship data.
What should happen before deleting a relationship label?
Remove it from records and tools that use it, because deleted labels cannot be restored.