Link a Contact’s Alternate Numbers Without Creating Duplicate People
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
Hypothetical scenario: A customer supplies a work number during an ongoing enquiry. One staff member creates a new contact; another replaces the customer’s personal number. The first action splits the history. The second removes a contact point that may still be valid.
The safer approach separates the person from their contact points. First establish whether the number belongs with the existing person. Then record its context. Retire an earlier number only when there is evidence that it has been replaced. A different number does not, by itself, mean a different person.
This workflow addresses identity continuity in a CRM. It does not establish messaging permission, choose which number to message, or validate number formatting. Correctly linking a number answers none of those separate questions.
1. Make two decisions instead of one
A single phone field can hide two distinct questions:
- Identity: Is there enough evidence to associate this number with the existing person?
- Relationship: Is it additional, a replacement for a particular earlier number, or a shared contact point?
An explicit statement from someone whose identity is already established can support both decisions. A spreadsheet row containing the same name and a different number cannot reliably do so.
Use clear working statuses: confirmed additional, confirmed replacement, unconfirmed, and retired. Keep context separate: personal, work, shared office, or unknown. These are recommended operating labels, not claims about available CRM fields.
Avoid a vague label such as verified. It leaves colleagues wondering whether someone checked identity, ownership, or formatting. Instead, record that the existing contact confirmed an additional work number and that their personal number remains current. Describe what was established, not a broader assurance.
2. Gather evidence without treating a match as proof
Start with the existing record and the source of the new information. Search for the incoming number and relevant records before changing anything. Search results reveal possible conflicts; they do not automatically justify linking or merging records.
Useful evidence may include an explicit statement during an interaction where identity has already been established, or confirmation through an established contact route. Choose a method appropriate to the sensitivity of the record and your organisation’s identity-checking process.
Weaker clues can locate a candidate but should not settle the decision:
- A matching name, employer, address, or household.
- An incoming message repeating information available elsewhere.
- A number imported beside an existing contact’s name.
- A colleague’s assumption that the newest number must be current.
Do not disclose existing contact history to someone using an unfamiliar number merely to establish a match. If the association cannot be confirmed safely, leave it unconfirmed and assign a review owner.
Distinguish association from exclusive control. A shared reception number may be relevant to someone’s work without uniquely identifying them. Record that limitation so a later reviewer does not combine colleagues’ records simply because they share a telephone line.
3. Capture the decision before changing the record
An endpoint is a contact point, such as a phone number, rather than the person. Use one worksheet entry per proposed endpoint change. Keep the original submission distinguishable from the reviewed decision, and reference relevant evidence rather than copying entire conversations into a broadly accessible note.
- Person: Existing record reference and distinguishing context.
- Incoming number and source: What was supplied, where it came from, and its claimed context.
- Identity evidence: Why the association is supported, with an interaction reference where appropriate.
- Earlier-number statement: Whether earlier numbers remain current, are replaced, or were not discussed.
- Conflict check: Other people or shared entities associated with the number.
- Decision: Additional, replacement, unconfirmed, or no link.
- Record action: What changes and what must remain unchanged.
- Owner and follow-up: Who resolves uncertainty and what triggers review.
- Application record: Applied or not applied; actor, application event, prior state, and resulting state.
The application record matters because a decision is not proof that an edit occurred. Separate proposed, reviewed, and applied changes. An entry awaiting review must say not applied, rather than leaving colleagues to infer its status.
This worksheet is a recommended design, not evidence of a product control. Check the workspace and current plan for available fields, related records, notes, and change history. Use only authorised staff for edits; a worksheet decision does not itself grant permission to change a record.
4. Worked example: a completed endpoint-change worksheet
Fictional worked example: All people, identifiers, number labels, and events below are hypothetical. Number labels are placeholders, not dialable details. Maya Chen’s existing record is H-104. Elena is the authorised case owner; Sam is the data steward. The initial state contains PERSONAL-A as Maya’s current personal number.
Entry A: Confirm the existing personal number
- Person: Maya Chen, H-104, existing service enquiry.
- Number, source, context: PERSONAL-A, already recorded; personal.
- Evidence: In identity-established interaction E-101, Maya confirms it remains hers and current.
- Earlier-number statement: PERSONAL-A remains current; no replacement requested.
- Conflict check: No conflicting association found in the reviewed records.
- Decision and action: Retain PERSONAL-A; add the confirmation reference without changing the number.
- Owner and follow-up: Elena; complete, with no unresolved identity question.
- Application record: Applied by Elena after review of E-101, event CHANGE-101. Prior state: PERSONAL-A current, without this confirmation reference. Result: PERSONAL-A current, with E-101 recorded. The prior state remains recoverable from the controlled change record.
Entry B: Add a work number without creating another person
- Person: Maya Chen, H-104.
- Number, source, context: WORK-B, supplied in E-101; direct work number as described by Maya.
- Evidence: Maya supplies WORK-B during the established interaction and identifies it as additional.
- Earlier-number statement: PERSONAL-A remains current; WORK-B does not replace it.
- Conflict check: No conflicting association found in the reviewed records.
- Decision and action: Confirmed additional. Associate WORK-B with H-104 as work; preserve PERSONAL-A and the existing person record.
- Owner and follow-up: Elena; complete after the reviewed addition.
- Application record: Applied by Elena after CHANGE-101, event CHANGE-102. Prior state: PERSONAL-A current with E-101 reference; WORK-B absent. Result: PERSONAL-A unchanged; WORK-B current as an additional work endpoint with E-101 reference. Prior state recorded for recovery.
Entry C: Replace only the personal number
- Person: Maya Chen, H-104.
- Number, source, context: PERSONAL-C, supplied through an established contact route in later interaction E-202; new personal number.
- Evidence: Maya explicitly identifies PERSONAL-C as her replacement personal number.
- Earlier-number statement: PERSONAL-A is no longer hers; WORK-B remains current.
- Conflict check: No conflicting association found for PERSONAL-C.
- Decision and action: Confirmed replacement of PERSONAL-A only. Add PERSONAL-C, retire PERSONAL-A, record the replacement relationship, and leave WORK-B current.
- Owner and follow-up: Elena; replacement complete. Historical references remain subject to the organisation’s retention practice.
- Application record: Applied by Elena after review of E-202, event CHANGE-203. Prior state: PERSONAL-A current personal, WORK-B current work, PERSONAL-C absent. Result: PERSONAL-A retired and linked to its replacement; PERSONAL-C current personal with E-202 reference; WORK-B unchanged. The controlled change record preserves the prior associations and statuses needed to reverse this edit if the decision proves wrong.
Entry D: Keep an imported candidate unconfirmed
- Person: Candidate match to Maya Chen, H-104; association not established.
- Number, source, context: UNKNOWN-D, imported list row IMPORT-17; context unstated.
- Evidence: Name match only; no established interaction confirms the link.
- Earlier-number statement: Nothing supplied about PERSONAL-C, WORK-B, or PERSONAL-A.
- Conflict check: UNKNOWN-D also appears against a shared office record.
- Decision and action: Unconfirmed, awaiting review. Hold the candidate and source reference separately; do not attach it as Maya’s confirmed number, merge records, or change existing endpoints.
- Owner and follow-up: Sam reviews the import source and seeks clarification through an established route at the next appropriate interaction.
- Application record: Not applied to H-104; no contact-change event. Prior and resulting contact states are identical: PERSONAL-C and WORK-B current, PERSONAL-A retired. Only the separate review entry has been recorded.
The resulting state is one person with two current contact points, one documented retired number, and one separately held candidate. The unresolved candidate is not evidence of a second person.
5. Apply changes without flattening history
For an additional number, preserve existing valid endpoints. For a replacement, identify exactly which earlier endpoint is superseded. Recency alone is insufficient evidence to retire every number on a record.
If your CRM supports multiple contact points, use context and status consistently. If it offers only one usable phone field, acknowledge that limitation. A governed related record or controlled worksheet may preserve the distinction while the system design is reviewed. Do not assume a notes field behaves like a structured endpoint record.
Avoid concatenating several numbers into a field intended for one value. Staff and downstream processes may interpret that value inconsistently. Free-text notes can preserve context temporarily, but they are easier to miss and harder to review systematically.
If duplicate people already exist, compare their identity evidence and attached history before authorised consolidation. Establishing that two records concern one person does not establish that every number on both records remains current. Review each endpoint and preserve original interaction references where possible.
6. Stop on conflicts and make recovery explicit
A number appears on another record. Pause rather than merge. The association may reflect a shared line, stale data, reassignment, or an error. Record the conflict and an owner before moving either person’s history.
The person asks staff to use a new number. Clarify whether it is additional or replaces a particular existing endpoint. A preference about future contact does not necessarily establish that an older number no longer belongs to them.
A wrong link has been applied. Stop further consolidation and identify the affected records. An authorised reviewer should remove the incorrect association and restore displaced details from reliable change records. Check interactions attached after the mistake before deciding whether history also needs reassociation.
In the hypothetical replacement above, CHANGE-203 identifies both the edit and its recoverable prior state. That supports a targeted reversal rather than guessing which numbers were present. Restoration should still follow review: an old snapshot may no longer reflect the person’s current situation.
Keep a correction trail that explains what changed and why, without preserving unnecessary personal data indefinitely.
7. Check decision quality on a small batch
For a hypothetical initial review, inspect ten recent number-change cases. Check whether each contains an identity decision, context, evidence distinguishing addition from replacement, and an owner for unresolved questions.
- Unsupported overwrites: Was a number removed without replacement evidence?
- Unnecessary person creation: Was another person created solely because a different number appeared?
- Unowned conflicts: Does every uncertain association have a named reviewer and next trigger?
- Traceable application: Can a colleague distinguish proposed edits from applied ones and reconstruct the prior state?
Use failures to revise the process, not merely fill empty fields. Missing evidence calls for clarification; a missing application record calls for better change capture. For the next pending update, complete the worksheet before editing. If a colleague cannot tell why this is the same person, what the new number means, and what happens to the old one, keep the decision open.
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