# An email domain does not prove which company someone works for

Subsidiaries, agencies and observers break the standard domain-to-account match.

By Ki Moon · 2026-08-21 · finding · current
Canonical: https://kihmoon.com/bench-notes/p/domain-is-not-company/

**Symptom:** A meeting lands on the wrong account because one attendee's email domain is another account's domain, and agents then name the wrong company.

Matching a person to a company by email domain is the standard first move. It builds a domain list per account from the CRM website, contacts and meeting attendees.

An email domain is evidence rather than an answer, because some accounts hold a contact whose domain is another account's primary domain.

- A subsidiary or sister brand filed under the parent.
- An agency or partner employee logged as a contact.
- An observer who sits in on meetings across two or three accounts.
- A contact filed under the wrong account by hand.

A count threshold clears single-contact noise. A bigger threshold will not settle what remains, because those cases ask a question about the company and need adjudication.

In a synthetic test set of 2,000 contacts, 40 carried a domain that is another account's primary domain. A domain join filed all 40 to the wrong account; trusting an explicit account link first left 6, the ones with no link. The set shows the mechanism, not how common it is.

## Check your setup (read-only)

List the contact email domains per account in the CRM. Count the accounts where a contact's domain is another account's primary domain. Any such account can misfile a meeting. 5% of accounts or more means domain matching can't be your only rule.

**Passes if:** Under 5% of accounts hold a contact whose email domain is another account's primary domain. Your matching has a rule beyond domain for those accounts.

**Access needed:** crm-read

## If it fails (changes to make later, not part of the check)

1. Keep one domain registry that every consumer reads, instead of each job deriving its own domain list.
2. Drop domains seen on only one contact before judging the rest.
3. Have a person or a model adjudicate each candidate domain against the account. Treat human overrides as final.
4. Re-check an account only when its evidence changes.
5. Compare a new matcher's output with the current one before switching.

**Applies if:** A job matches people, emails or meetings to accounts by email domain, and the CRM holds more than a few hundred accounts.

**Skip if:** Your CRM has no parent-child links, partner accounts or agency accounts, and each account uses one domain.

Tags: identity, matching, crm
