Compare the operating models
In this fictional example, Ada purchases for A and advises B. Duplicating Ada splits communications and requires two edits when her phone changes. A and B still need different role context.
| Business requirement | Contact per company | One contact with affiliations |
|---|---|---|
| Identity | Two conflicting copies possible | One Ada profile |
| Role | Hidden in record name | A/buyer; B/adviser |
| Deal participation | Staff guess which copy | Choose matching affiliation |
Work through the chosen model
Affiliations store person, company, role and supplied active period. Deals select the relevant organisation and contact link. Ending Ada’s A role does not end her B role; a person-wide phone update remains one update.
- Identify Ada once
- Record each supplied affiliation
- Use the right link on work
Affiliations need a usable role picker. Check how the selected CRM lets staff choose the affiliation on a deal.
One contact has two affiliations. A’s deal uses buyer-Ada, B’s project uses adviser-Ada. Neither creates another person.
When the other model fits
Two different people named Ada share an inbox. Should they merge?
Show the worked answer
No. Shared name/email is not person identity; retain separate people.