Back to all articlesContact identity

Distinguish People With the Same Name Before Combining Their Records

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

In a hypothetical duplicate-review scenario, two records named Alex Morgan appear together. Both mention the same company, and one has a phone number the other lacks. Combining them might look like routine cleanup. But they could represent different employees, a former employee and a replacement, or people attached to the same shared inbox.

For CRM contacts with identical names, keep the records separate until evidence connects them to the same person. Compare person-specific evidence, investigate differences, and distinguish an individual identifier from a channel used by several people. If identity remains uncertain, improve the display labels rather than inventing details or forcing a merge.

The worksheet below turns that approach into a repeatable review. All illustrative people, organisations, identifiers, dates, and events in this article are fictional and hypothetical, not Alactic customer results.

1. Separate candidate similarities from identity evidence

A name match answers one question: do these records contain the same name? It does not establish whether they describe the same individual. A company name, office address, and switchboard number may all describe one workplace rather than one person.

Sort the information into distinct categories before making a decision:

  • Candidate similarities: matching names, organisations, roles, or shared channels that explain why the records were compared but do not connect them to one individual.
  • Same-person corroboration: evidence connecting both records to one individual, such as an existing verified individual account reference whose meaning and association with both records have been checked.
  • Distinct-person evidence: evidence supporting separate people, such as an authorised account administrator confirming that the records represent two different employees.
  • Unresolved differences: conflicting affiliations, addresses, or other details whose meaning has not been established.
  • Unknowns: missing facts or unanswered questions relevant to the decision.

“None established” is a valid entry for either evidence category. Do not promote a similarity into same-person corroboration just to fill the worksheet. Likewise, different organisations do not establish different people: one person may have changed jobs or hold multiple affiliations.

A missing field is not a contradiction. Different email addresses may belong to one person, while one shared inbox may serve several people. Ask what each field establishes, how current it is, and whether apparently independent facts were copied from one source.

2. Build a review entry that another person can use

Use one worksheet entry per pair. Preserve the source records during review. If review notes cannot be stored alongside the records, use an access-controlled log linked by record reference. This is a recommended operating design, not a claim that a particular product provides these controls.

Each entry should contain:

  • Record references: the exact records being compared.
  • Known affiliations: organisation and function, with source and confirmation date where available.
  • Confirmed identifiers: existing references or contact details, what they identify, and how their association was confirmed.
  • Candidate similarities, same-person corroboration, and distinct-person evidence: separate fields, not one combined evidence list.
  • Unresolved differences and unknowns: conflicting details and missing answers, without assumptions presented as facts.
  • Decision and reason: keep separate as confirmed namesakes, hold separately pending verification, or refer for authorised merge review.
  • Display labels and follow-up: useful selection labels, the next action, and its owner.

Distinguish confirmed to exist from confirmed to belong to this person. An email copied from a spreadsheet may exist without its connection to the contact being verified. An internal CRM record ID identifies a database entry, not necessarily a unique individual.

3. Filled namesake review worksheet

This fictional worked example shows how to complete the reusable fields. The identifiers represent existing business references; they are not a recommendation to collect sensitive identifiers.

Pair A: same name and organisation, separate people

  • Records: C-104 and C-219; both named Alex Morgan.
  • Known affiliations: purchasing and facilities contacts respectively at Cedar Works, confirmed by its account administrator on 8 April.
  • Confirmed identifiers: CW-P17 and CW-F28. The administrator confirmed that these identify separate staff members, not two accounts for one person.
  • Candidate similarities: identical name, same organisation, and the same office switchboard number.
  • Same-person corroboration: None established.
  • Distinct-person evidence: administrator confirmation that the references identify two different employees.
  • Unresolved differences: None affecting this decision; the different functions are explained by the confirmed separate identities.
  • Unknowns: direct phone numbers are unavailable and unnecessary to resolve this pair.
  • Decision and reason: KEEP SEPARATE — confirmed namesakes. Do not combine their histories or communication preferences.
  • Display labels: Alex Morgan — Cedar Works / Purchasing; Alex Morgan — Cedar Works / Facilities.
  • Follow-up: data steward records the decision and checks whether staff can distinguish the contacts during selection.

Pair B: same name, unresolved affiliation difference

  • Records: C-330 and C-481; both named Jordan Lee.
  • Known affiliations: C-330 lists Bay Studio, confirmed in existing business correspondence on 12 March. C-481 lists Northline Supply from an import without a verification note.
  • Confirmed identifiers: C-330 has individual business account reference BS-42, confirmed in its account history. No person-specific identifier is confirmed for C-481.
  • Candidate similarities: identical name only.
  • Same-person corroboration: None established. BS-42 is associated with only one of the records.
  • Distinct-person evidence: None established.
  • Unresolved differences: different listed organisations, with unequal source quality and insufficient timing information.
  • Unknowns: whether one person changed employers and whether the imported affiliation is accurate.
  • Decision and reason: KEEP SEPARATE PENDING VERIFICATION — identity unresolved, not confirmed namesakes.
  • Display labels: Jordan Lee — Bay Studio; Jordan Lee — affiliation unverified / C-481.
  • Follow-up: record owner checks existing account correspondence for evidence resolving the affiliation difference before considering new outreach.

Pair C: same name and shared inbox, separate people

  • Records: C-512 and C-519; both named Sam Patel.
  • Known affiliations: both work with Willow Services. Existing account notes identify service-desk and billing functions.
  • Confirmed identifiers: on 9 April, the account administrator confirmed that WS-S8 and WS-B6 identify separate people. The email on both records was confirmed as a shared departmental inbox.
  • Candidate similarities: same name, organisation, and shared email address.
  • Same-person corroboration: None established.
  • Distinct-person evidence: administrator confirmation that the references represent two people using the shared channel.
  • Unresolved differences: None affecting the identity decision.
  • Unknowns: who will read a particular message sent to the inbox.
  • Decision and reason: KEEP SEPARATE — confirmed namesakes sharing a communication channel.
  • Display labels: Sam Patel — Willow Services / Service desk; Sam Patel — Willow Services / Billing.
  • Follow-up: data steward notes that the inbox is shared; the sender verifies the intended recipient before using person-specific context.

The worked decisions produce two confirmed-namesake outcomes and one unresolved hold. All three pairs remain separate, but only Pair B needs further identity verification. This distinction prevents an unresolved case from being mistaken for a completed investigation.

4. Investigate the question that would change the decision

Write down an unexplained difference before choosing an explanation. Different account references might identify separate people or separate accounts belonging to one person. A changed affiliation might reflect a job move, simultaneous roles, or namesakes.

Use the narrowest verification question that could settle the uncertainty. For Pair A, the useful question is whether the references identify different employees. Collecting additional personal information would not address that question more directly.

  1. Check existing source material and its date.
  2. Identify whether each relevant field describes a person, organisation, account, or communication channel.
  3. Ask an authorised record owner or appropriate existing business contact to clarify the specific ambiguity.
  4. Record the answer, its source, and what it does not establish.
  5. Leave identity unresolved if the answer is insufficient.

For Pair B, finding a second copy of the original import would not independently verify the affiliation. A useful next finding would need to explain how the two records relate to an individual. Do not substitute guessed middle names, inferred ages, photographs, or sensitive identifiers for that missing connection.

5. Add useful labels without changing the recorded name

A disambiguating label should help a colleague select the right record without pretending to be part of the person’s name. Keep the name separate from organisation, function, review status, and internal reference wherever the available fields allow it.

A practical convention is Name — confirmed organisation / confirmed function. If ambiguity remains, add a stable record reference for internal use. If an affiliation is unverified, label that uncertainty rather than presenting the affiliation as settled.

  • Useful: Alex Morgan — Cedar Works / Facilities.
  • Useful with limited evidence: Jordan Lee — affiliation unverified / C-481.
  • Misleading: Alex Morgan Senior, unless Senior is genuinely part of the recorded name.
  • Unhelpful: Sam Patel 2, which gives no reason to choose that record.

Function-based labels are readable but can become stale. Record references are stable but less meaningful to staff. Combine them when necessary and update labels when supporting facts change.

Check where labels travel: an internal review phrase should not become a greeting or recipient-facing name. Verify field availability and behaviour in the current workspace and plan before adopting a convention; do not assume the same behaviour across CRM, communications products, web interfaces, and Android apps.

6. Separate identity from permission to communicate

Selecting the correct record does not establish the correct message destination. In Pair C, keeping the people separate protects their histories, but it does not make the shared inbox person-specific.

Before sending, check both the intended individual and whether the channel is suitable for the content. Do not transfer permission records, opt-out states, or private conversation context between namesakes merely because their names or contact details match.

For WhatsApp, recipient permission matters and opt-outs must be honoured. Identity review does not replace these checks. Approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window, which opens or resets with a user message. Template approval does not guarantee delivery. Check the current official policy for precise requirements.

Avoid outreach solely to tidy the database when existing material can resolve the issue. If verification outreach is appropriate and authorised, ask only what is needed, without exposing another person’s account details.

7. Preserve decisions and handle mistaken merges carefully

A keep-separate decision helps only if the next reviewer can find it. Record the pair references, reason, evidence source, decision date, and reviewer. Distinguish confirmed namesakes from temporary holds so unresolved work retains an owner.

If the pair reappears, assess new evidence rather than repeating the investigation. Do not suppress every future comparison involving either contact: a confirmed namesake can still have a genuine duplicate elsewhere.

After a mistaken merge, pause edits and communications involving the disputed history. Preserve available source references and change history. An authorised owner should establish which activities, affiliations, and channels belong to each person before repair.

Check what the workspace supports before attempting reversal. Creating another contact does not necessarily restore the original relationships. If reliable reversal is unavailable, plan a controlled reconstruction and leave uncertain activity attribution unresolved rather than guessing.

8. Check whether the review improves everyday selection

For a hypothetical first exercise, review ten same-name pairs without changing the records. Ask a second reviewer to explain each decision using only the worksheet. If they need unwritten background, improve the entry before acting.

Track observable outcomes:

  • Pairs confirmed as distinct people versus pairs awaiting verification.
  • Decisions missing a source, reason, owner, or next action.
  • Selections that still require staff to open both records.
  • Previously reviewed pairs returning without their decision context.
  • Shared channels still mistaken for person-specific destinations.

Respond to the actual failure. Missing evidence calls for better notes; repeated selection errors call for clearer labels. Unresolved pairs need a specific verification question, not a more confident guess. The useful result is that staff can choose the intended person and explain why the records remain separate—not simply that the duplicate queue is smaller.

Contact identityCRM data qualityDuplicate reviewContact management

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications