Choose Which Contact Fields Survive a Merge
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A contact merge can keep the wrong number, overwrite a preferred name, or revive an unwanted messaging preference simply because one record was updated more recently. Instead, select each surviving field separately: judge its source, look for explicit confirmation, and use dates that describe the value itself.
Do not choose one whole record as the truth. Choose supported values, retain the evidence behind each decision, and assign unresolved conflicts to a reviewer. A recent administrative edit should not outrank an older, direct confirmation from the person.
This guide assumes the records have already been confirmed as belonging to the same person. It covers field survivorship, not duplicate detection or exact merge controls. The worksheet is a recommended operating design, not evidence that a particular product provides these controls.
1. Separate the surviving record from its values
The retained record is a container. Its name, title, phone number, and preferences do not automatically deserve to survive with it. Otherwise, unrelated maintenance becomes an accidental decision rule.
Distinguish three dates before comparing candidates:
- Record updated: when anything on the record changed.
- Value observed: when an identifiable source supplied or displayed this value.
- Value confirmed: when the person explicitly affirmed the value for a stated purpose.
The latter two help establish currency, but neither removes the need for context. A recent signature may support a job title; it does not establish permission to receive promotional messages. An import date identifies when data entered the system, not when the person supplied it.
Also distinguish an empty field from an instruction. A blank number means no value is recorded there. A request to stop using a number is evidence against a particular use. Filling the blank from another record must not erase that instruction.
2. Set rules for each field and its intended use
Prefer relevant, explicit confirmation over an indirect observation, and attributable observations over unexplained imports. Compare recency within that context rather than assigning a universal score to unlike evidence.
- Preferred name: use the person's stated preference. Keep the full contact name separate when needed; a request to use Maya does not establish a preference for Maya Chen.
- Job title: assess evidence about the current role. A newer signature may justify a candidate title without making it explicitly confirmed.
- Phone: distinguish ownership, reachability, and permitted use. Previous successful contact does not establish a current preference.
- Language: preserve channel scope. English for email does not automatically mean English everywhere.
- Messaging permission: evaluate the supporting event independently. A newer import flag does not establish that an earlier opt-out was reversed.
Define statuses before selecting values. Selected means supported for the stated use, not universally valid. Provisional means a candidate has some support but requires confirmation and explicit use restrictions. Unresolved means no operational value has been chosen.
A provisional value must not silently become authoritative. If the destination cannot preserve its status and restrictions, leave the candidate in the review record rather than populating an active field. An incomplete contact can be safer and more accurate than a complete-looking contact with hidden uncertainty.
3. Create a review record with traceable evidence
Capture candidates before changing either record. Use an approved location with access appropriate to the information involved. Keep enough evidence to reconstruct the decision without copying entire correspondence histories unnecessarily.
For every disputed field, record:
- Field and intended use: the decision the value will control.
- Candidates and source records: each competing value and where it came from.
- Evidence locator and relevant date: a message reference, form submission identifier, or reviewed note reference—not merely a description such as recent conversation.
- Selected value, status, and permitted use: including restrictions on provisional values.
- Reason and alternatives: why the evidence wins and where rejected or unresolved candidates remain.
- Owner and next action: who must resolve uncertainty and what would count as sufficient evidence.
A reviewer should be able to follow the locator to the supporting event and distinguish it from other correspondence. If the evidence cannot be retrieved, mark that limitation rather than treating the description as confirmation. Record-level identifiers alone are insufficient when the record contains several conflicting events.
4. Filled worksheet: resolve one fictional contact
Hypothetical worked example: All people, organisations, dates, identifiers, and events below are fictional. Records C-104 and C-287 have already been confirmed as Maya Chen at Northbridge Studio. C-104 was updated on 12 May following contact; C-287 was updated during an import on 20 May. The import date does not date its underlying values.
Review record: MR-042, held in the team's approved restricted review location. Owner: account coordinator. Evidence references below are fictional locators in that location, not product links. Completing this worksheet does not authorise outbound contact.
Preferred name for staff display. C-104 contains Maya Chen; C-287 contains M. Chen. Evidence MSG-0512-01 records Maya's 12 May request to use Maya. Import entry IMP-0520-17 supplies the abbreviation without an original observation date.
Decision: Maya — selected as preferred name. Retain Maya Chen separately as the full contact name, supported by the contact-authored identity details in MSG-0512-01. The preference supports Maya, not the full name. Retain M. Chen only as a historical candidate in MR-042. Owner: coordinator; no confirmation needed unless the preference changes.
Current job title for staff reference. C-104 contains Operations Manager, supported by confirmation note NOTE-0206-03 from 6 February. C-287 contains Head of Operations, visible in the contact-authored signature of message MSG-0509-04 dated 9 May.
Decision: Head of Operations — provisional candidate. The newer signature supports possible currency but does not explicitly describe a role change. Permitted use: labelled internal reference during review only. It must not drive role-based segmentation, automated routing, or externally addressed titles.
For this hypothetical merge, the destination cannot preserve that distinction reliably. Therefore, leave the active current-title field unset and retain both candidates, their evidence, and the provisional status in MR-042. Do not leave Operations Manager active by default either. Owner: coordinator; confirm the current title during the next appropriate exchange, then approve a field update.
Primary phone for account-related calls. C-104 contains Phone A, ending 0142; C-287 contains Phone B, ending 0186. MSG-0512-02 records confirmation of Phone A for account-related calls on 12 May. IMP-0520-18 provides Phone B without an observation date or usage context.
Decision: Phone A — selected for account-related calls only. This establishes neither WhatsApp promotional permission nor unrestricted use. Keep Phone B in MR-042 as an unverified alternative, not an active fallback. Owner: coordinator; ask whether Phone B is obsolete during a suitable existing exchange.
Email language preference. C-104 contains English; C-287 contains French. MSG-0512-03 records an explicit request for English email on 12 May. FORM-0303-08 shows a French-language form submission on 3 March, from which the earlier preference was inferred.
Decision: English for email — selected. The explicit, channel-specific request outweighs the inference. Retain the French candidate only in MR-042; preferences for other channels remain unspecified. Owner: coordinator; ensure the destination does not broaden email language into an all-channel preference.
WhatsApp promotional permission. C-104 records an opt-out; C-287 contains a yes flag. MSG-0510-06 records a request to stop promotional messages on 10 May. IMP-0520-19 contains the yes flag but no underlying permission event, wording, or original date.
Decision: do not send WhatsApp promotional messages. The import does not establish a later change of preference. Retain the yes flag as disputed history in MR-042, never as active permission. Owner: campaign owner; exclude the contact from promotional preparation unless an appropriate later permission event is established and reviewed.
Preferred contact time for scheduling. C-104 contains mornings in NOTE-UNDATED-11; C-287 contains afternoons in NOTE-UNDATED-12. Neither note identifies an attributable request, observation date, or time zone.
Decision: unresolved; leave the active preference unset. Retain both candidates in MR-042. Neither may drive scheduling automation. Owner: coordinator; ask for a time range and time zone at the next appropriate exchange.
The proposed result is deliberately mixed: supported selections, a provisional candidate held outside the active title field, a promotional restriction, and an unresolved scheduling preference. Review success means preserving those distinctions, not filling every field.
5. Preserve permission scope independently
A correctly identified, reachable contact may still be unsuitable for a particular communication. Do not infer permission from a surviving phone number, an unrelated reply, or previous inclusion in a campaign list.
The WhatsApp Business Messaging Policy addresses recipient permission and requires businesses to honour opt-outs. Consult the current policy for precise requirements. For this merge decision, the practical question is narrower: does the evidence support the proposed channel and purpose, or does it contain a restriction that must survive?
Preserve the permission event's source, date, channel, purpose, and any withdrawal. If scope is disputed, do not broaden it. Make restrictions visible to those preparing communications rather than burying them in a general note. A merge approval is a data decision, not authorisation to send a message.
6. Verify the proposed result and the actual merge
Have the authorised reviewer inspect both the worksheet and the proposed fields. A valid number paired with an overly broad permission flag is still an unsafe result.
- Retrieve each cited evidence item and check that it supports the selected value and intended use.
- Verify that preferred name and full contact name remain distinct.
- Confirm that provisional status and use restrictions survive. In this example, check that the title remains in MR-042 and the active title is unset.
- Check that unresolved alternatives have not become active fallback values.
- Verify that opt-outs remain effective in the processes using the contact, including previously prepared lists.
- Record the authorising reviewer and decision date, then compare the merged fields with the approved worksheet.
Check your workspace and current plan before relying on history, field-status, permission, or review controls. Where the proposed distinction cannot be represented safely, retain it in the approved review location and withhold the affected use. This is an operating recommendation, not a claim about available Alactic controls.
7. Recover when the wrong value survives
Stop the affected use first. Pause reliance on a disputed number or remove the contact from relevant promotional preparation while checking evidence. Correcting a field may not correct a list or work item prepared earlier.
Use the review record to reconstruct the decision. Restore supported values where authorised, record the correction reason, and inspect downstream uses. Do not assume that restoring a field restores every related state.
If evidence is missing, mark uncertainty rather than rebuilding history from memory. Seek confirmation through an appropriate existing route when suitable; do not contact every conflicting number merely to discover which responds. Then fix the failed rule, whether it was import-date precedence, whole-record copying, or loss of provisional status.
8. Measure whether the review improves decisions
For a hypothetical pilot, review ten confirmed duplicate pairs using the worksheet. Assign an owner and review date to each unresolved field. Compare approved decisions with actual post-merge values, not just with the number of merges completed.
- Evidence coverage: selected fields with retrievable, relevant supporting evidence.
- Uncertainty handling: provisional and unresolved fields whose statuses and restrictions remain intact.
- Execution mismatches: merged fields that differ from the approved worksheet.
- Rule failures: corrections attributable to unsupported recency assumptions or lost permission scope.
Keep deliberate holds separate from errors. An unset title with a traceable candidate and an assigned reviewer is a controlled outcome; an unsupported title presented as confirmed is not. Use the observed failures to adjust the survivorship rules before expanding the review.
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