FindingcurrentGTM data

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.

Check your setup read-only

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

If it fails: changes to make later (not part of the check)
  1. 01Collect candidate pairs by same name and same account with no shared identifier.
  2. 02Judge each pair from the activity and people around both records, not from the two records alone.
  3. 03Merge automatically above a high confidence bar. Route lower scores to a person.
  4. 04Store "keep separate" verdicts so the same pair isn't judged again.
  5. 05Keep every merge reversible.
Applies ifYour dedupe or enrichment matches people across CRM, calendar and email sources by name and domain, where many records lack an email or id.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.