Back to all articlesContact identity

Handle Duplicate Contacts When Each Record Has Active Business History

Alactic Editorial10 min read

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

Two contact records appear to represent the same person, but each has an active enquiry. Staff hesitate to merge them because one record holds a current quotation and the other holds a separate request with its own next action. That hesitation is useful: the risk is not simply losing a phone number. It is losing the distinction between two pieces of business.

The right approach is to separate two decisions. First, decide whether the records represent one person. Then establish how each linked enquiry and its history will remain intact after identity consolidation. One person record should not mean one combined enquiry. Do not proceed until you understand what the merge operation actually changes in your workspace.

The relationship map below gives staff a concrete way to agree on the intended result before making changes, and a checklist for proving that the result matches the plan.

1. Decide whether this is one person before touching their history

Similar names alone are not enough to establish a duplicate. A shared office phone, a general email address, or a family contact number may belong to several people. Conversely, one person may legitimately use different email addresses for different enquiries.

Review identity evidence separately from business activity. Ask whether the contact details, previous correspondence, and context consistently identify the same individual. If evidence conflicts, resolve the conflict through an appropriate existing contact route rather than selecting whichever record looks more complete.

Record a short reason for the decision. For example, in a hypothetical case: “Both enquiry threads identify Maya Chen as the requester; Maya confirmed that the work and personal email addresses belong to her.” That is more useful than a note saying only “duplicate.”

Different enquiry subjects, statuses, or staff assignments do not by themselves disprove a shared identity. Equally, a shared identity does not justify making those enquiries identical. Keep this review narrowly focused: are these records about the same person, and is there enough evidence to act?

If the answer remains uncertain, leave the records separate and flag the suspected duplicate for review. Preserving an unresolved duplication is preferable to confidently joining two different people and exposing their histories to the wrong context.

2. Write down what consolidation must—and must not—change

Before choosing a surviving contact record, define the expected outcome in plain language. The contact identity may be consolidated. The separate enquiries should retain their identifiers, subjects, stages or statuses, and business histories unless a separately authorised change is intended.

  • Identity change: both enquiries will refer to the same surviving person record.
  • Relationship preservation: each enquiry will retain its own associated notes, files, tasks, and communications where those links already exist.
  • Attribution preservation: historical authorship, timestamps, and enquiry-specific context should remain traceable.
  • No unrelated decisions: the merge will not be used to redesign the pipeline, combine opportunities, or decide sales ownership.

A contact-level timeline may show activity from several enquiries together. That can be a useful overview, but it is not proof that the underlying enquiry links are correct. A message visible on the person record might still be attached to the wrong enquiry—or to no enquiry at all.

Likewise, linking an enquiry to a surviving contact does not mean that every email address on that contact is appropriate for every purpose. Preserve the context of contact methods rather than treating consolidation as permission to use them interchangeably.

3. Fill a pre-merge relationship map

Fictional worked example: all names, record identifiers, activities, and counts in this example are hypothetical. Maya Chen has two contact records. One is linked to an equipment purchase enquiry; the other is linked to a training enquiry. Both enquiries are active and must remain separate.

The map records a proposed result, not an assumption about what a CRM will do automatically. Replace the example details with your own record references and resolve every uncertain link before authorising a change.

PRE-MERGE RELATIONSHIP MAP — HYPOTHETICAL EXAMPLE

Person: Maya Chen
Identity evidence: Existing correspondence and direct confirmation
establish that both contact records represent Maya.

CONTACT RECORDS
C-104 — Maya Chen
  Work email: maya.chen@example.com
  Linked active enquiry: E-310
  Proposed role: Surviving contact

C-287 — M. Chen
  Personal email: maya.private@example.net
  Linked active enquiry: E-462
  Proposed role: Duplicate to be consolidated into C-104

DISTINCT BUSINESS ACTIVITY
E-310 — Equipment purchase enquiry
  Current status: Quotation sent
  Next action: Follow up on equipment specification
  Enquiry-linked history: 3 notes, 1 quotation file, 1 open task
  Current person link: C-104
  Expected person link: C-104
  Expected history: Remains attached to E-310

E-462 — Team training enquiry
  Current status: Requirements discussion
  Next action: Confirm training dates
  Enquiry-linked history: 2 notes, 1 requirements file, 1 open task
  Current person link: C-287
  Expected person link: C-104
  Expected history: Remains attached to E-462

CONTACT-LEVEL HISTORY REQUIRING REVIEW
C-287 has a note: “Use personal email for training scheduling.”
Expected treatment: Retain the note and its original provenance;
make its training-only context visible to staff handling E-462.
Do not treat it as a global instruction for E-310.

EXPECTED RESULT
Active person identity: C-104
Separate active enquiries: E-310 and E-462
E-310 and E-462 are not combined.
Each enquiry retains its original status, next action, and history.
Historical activity retains its author and timestamp where available.
Old identifier C-287 is recorded in the change log.
Treatment of C-287 after consolidation: Verify workspace behaviour.

CHECK BEFORE AUTHORISATION
Confirm merge behaviour for notes, files, tasks, communications,
contact methods, permissions, and any dependent workflows.
Confirm an available recovery route before proceeding.

The most important entry is often the awkward one: the contact-level note that belongs in the context of only one enquiry. It forces a decision about interpretation without pretending that all history is neatly organised already.

If your records contain additional relationships, add them to the map. These might include an organisation link, a service request, or a scheduled appointment. Record their current and expected links; do not assume that checking the two main enquiries covers everything.

4. Check the merge operation against the map

Use the current workspace documentation or an authorised administrator to establish what the available operation does. Check your workspace and current plan for availability. This is an operating procedure, not a claim that any particular merge, preview, export, or restoration control exists in Alactic.

Answer these questions before proceeding:

  • Can both enquiries link to the surviving person while remaining distinct records?
  • Which contact fields survive when values conflict, and can staff choose between them?
  • What happens to contact-level notes, attachments, and communications?
  • Are enquiry-specific relationships retained, reassigned, or left unchanged?
  • How is the former contact identifier handled after consolidation?
  • Could the change trigger tasks, notifications, assignments, or other dependent workflows?
  • Could moving relationships change who can see either enquiry or its history?
  • What recovery options exist if a link or field is wrong?

Choose the surviving contact based on the practical consequences of retaining its identifier and relationships, not merely on which record was created first. A record with more populated fields is not automatically the safer survivor if important dependencies point elsewhere.

If the system cannot preserve the mapped relationships, stop. Consider an available, documented alternative, such as retaining both records with a clear duplicate-review note until an administrator can resolve the links. Do not improvise a chain of deletions and recreations to simulate a merge: that can make historical attribution harder to verify.

5. Execute a small, controlled change

Once the map is agreed, have an authorised operator perform the change during a period when staff can avoid editing the affected records. A brief coordination message can prevent someone from adding a note to the duplicate halfway through the operation.

  1. Capture the baseline. Record the contact identifiers, enquiry identifiers, statuses, next actions, and linked-item counts. Use an approved snapshot or export method if one is available and appropriate.
  2. Record field decisions. Identify which name and contact details should remain, and preserve relevant context for conflicting values. Do not silently replace a specific communication instruction with a general preference.
  3. Confirm authorisation and recovery. Name the operator, the reviewer, and the available route for correcting an unsuccessful result.
  4. Perform only the agreed identity change. Follow the documented process. Do not add unrelated record cleanup while the relationships are being changed.
  5. Verify immediately. Compare the result with the map before staff resume normal work.

A smaller change is easier to inspect. If you also want to standardise names, tidy old tasks, and reorganise notes, separate those actions from the identity consolidation. Otherwise, an unexpected result may be difficult to attribute to a particular action.

6. Verify attribution, not just record counts

In the hypothetical example, seeing one person record and two enquiries is necessary but insufficient. Open E-310 and E-462 individually, then check the surviving contact from the opposite direction.

  • Person links: both enquiries point to Maya’s surviving contact, not to another person with a similar name.
  • Business distinction: the equipment quotation remains on E-310; the training requirements remain on E-462.
  • History: notes, files, and tasks match the baseline and are readable in their intended context.
  • Attribution: authorship and timestamps remain traceable rather than appearing to be newly authored by the merge operator.
  • Next actions: each enquiry still shows the correct outstanding work, without substitution or duplication.
  • Contact context: the training scheduling instruction has not become a blanket instruction for the equipment enquiry.
  • Access: authorised staff can still reach the records they need, without unintended exposure of the other enquiry.

Check content as well as counts. Two notes can replace two different notes while leaving the count unchanged. Review identifying details, such as the quotation file and the training requirements note, to establish that the right material survived in the right place.

Finally, ask a staff member familiar with each enquiry to confirm that their next action is still understandable. Structural checks can pass while operational context becomes confusing.

7. Recover deliberately when the result is wrong

If an enquiry disappears from the contact view, do not immediately recreate it. First determine whether it still exists under its original identifier and whether only the relationship or display has changed. Recreating an existing enquiry can introduce a second duplication problem.

If history appears under the wrong enquiry, pause changes to the affected records. Compare the baseline with the current state and list the exact mismatches. Use the documented restoration or relationship-correction process available in the workspace, with appropriate authorisation. Do not assume there is an undo function.

If the enquiries remain distinct but a mixed contact timeline confuses staff, the issue may be presentation rather than lost data. Keep enquiry references visible in subsequent notes and use enquiry-specific views where available. Avoid deleting valid history merely to make the contact timeline look simpler.

If an identity decision proves wrong, escalate promptly and preserve the change record. Unpicking two different people’s histories is more complex than correcting a missing email field. Stop further activity on the affected identity until the responsible administrator has established a safe correction plan.

8. Close the review with a measurable handoff

For the hypothetical Maya example, completion means one intended surviving identity, two distinct active enquiries, both expected person links confirmed, and every mapped history item accounted for. It also means no unexplained change to status, next action, attribution, or access. An unresolved mismatch means the review stays open.

Your next action is to choose one suspected duplicate pair and fill the relationship map before editing either record. Record the number of distinct enquiries before and after, the number of expected links checked, and any unresolved exceptions. Have a reviewer sign off against those observations rather than against a general impression that the contact looks tidier.

The decision becomes much safer when staff can point to the intended relationships in advance: one person, separate business activity, and a verifiable history for each enquiry.

Contact identityDuplicate contactsCRM operationsData integrity

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