Same name, same account, no shared id: one person or two?
No deterministic rule settles these pairs, so judge them and keep merges reversible.
Symptom2 contact records have the same name at 1 account and no shared email or id. Agents either count the person twice or blend 2 people.
Dedup usually rests on a shared identifier, such as an email, a phone or a CRM id. Two records with the same name at the same account and none of those leave the rule with nothing to go on.
No deterministic rule exists for this case. Joining on name and account blends two colleagues who share a name, and refusing leaves real duplicates in place.
So have a model judge each candidate pair. Give it both records' neighbourhoods, the meetings, messages and people around each one, rather than the two records alone.
Have the model return a confidence instead of a yes. Above a high confidence bar the pair merges automatically, and below it the pair goes to a person. Remember a "keep separate" verdict, and keep every merge undoable.
List pairs of contacts at the same account with matching names and no shared email, phone or external id. Count the pairs. Look for a recorded reason on the 20 most recent pairs your dedup joined. More than 1 of 20 joined with no record of why is a gap.
Passes if19 or more of 20 sampled same-name pairs your dedup joined carry a recorded reason. Each join can be undone.
Access needed:crm-readlocal-config
- 01Collect candidate pairs by same name and same account with no shared identifier.
- 02Judge each pair from the activity and people around both records, not from the two records alone.
- 03Merge automatically above a high confidence bar. Route lower scores to a person.
- 04Store "keep separate" verdicts so the same pair isn't judged again.
- 05Keep every merge reversible.