Using Call

Finding and Merging Duplicate Contacts in Call

Why duplicate contacts appear in a phone-team CRM, how to tell a true duplicate from a lookalike, and how to merge two records without losing calls or notes.

Call editorial team · Published · 6 min read

Every phone team eventually has the same experience. An agent opens a contact, sees one short note, and then the customer says, "I spoke to someone last week about this." The earlier conversation exists, but it sits on a second record with a slightly different name. Nobody did anything wrong. The system simply held two records for one person.

A team member reviewing a customer list on a monitor at a shared desk
Illustrative image

This guide explains where duplicates come from, how to judge whether two records are really the same person, and how to merge them safely. If your contact data is still young, read keeping CRM data clean and how contacts work in Call first.

Why duplicate contacts appear

Duplicates are a side effect of busy teams and several entry points. The same person can arrive through a call, a web form, a spreadsheet import and a manual entry in the same month. Each path has its own habits about names and numbers.

Common sources of duplicates

  • Number formatsOne record holds a number with a country code and another holds it with a leading zero. To a person they match; to a database they are different text.
  • Name variations"Robert Smith", "Bob Smith" and "R. Smith" all describe one customer, typed by three different agents.
  • ImportsA list loaded from a spreadsheet adds rows for people who already exist, especially when the list came from another tool.
  • Web forms and portalsA visitor who fills in a form twice, or uses a different email the second time, creates a fresh record each time.
  • Shared devicesA person calls from a colleague's phone and is saved as a new contact under that number.

None of these is a training failure. They are predictable, which is why the cleanup should be routine rather than a once-a-year rescue.

What duplicates cost your team

The damage is mostly invisible until a customer notices it. The most common effects are practical ones:

Fixing duplicates is one of the cheapest improvements to customer experience, because it costs staff time only once per pair.

Deciding whether two records are the same person

A system can only suggest that two records look alike. A person has to decide whether they really are. Treat a suggestion as a question, and answer it with evidence.

SignalWhat it suggestsHow much to trust it
Same phone numberLikely the same personStrong, but check for shared lines such as a switchboard, a family phone or a shop counter
Same email addressVery likely the same personStrong, unless a team mailbox is used by several people
Similar names, different numbersPossibly the same person with two phonesWeak on its own; look at the notes and history
Same company, different peopleProbably two colleaguesDo not merge; link them through the company instead

A practical way to judge a pair is the two-minute test. Look at the most recent call on each record, then at the notes. If the second record reads like the next chapter of the first, with the same topic, the same preferences and the same concerns, you have your answer. If you still cannot tell, ask the agent who last spoke to the customer, or leave the pair for the next call, when the customer can confirm their own details.

How merging works and what it keeps

A merge combines two records into one. The point is to keep the customer's full history in a single place without throwing anything away.

Before and after a merge

Two separate recordsOne merged record
CallsSplit across both recordsAll calls on one timeline
NotesEach record has part of the storyEvery note is on the survivor
AppointmentsBooked against whichever record was usedAll appointments on the same contact
ReportsOne customer counted twiceOne customer counted once
UndoNothing to undoNot reversible from the merge page

Because a merge cannot be undone from the page where you do it, make it a deliberate step. Many teams give the job to one or two people, usually a supervisor or an admin, rather than letting every agent merge during a call.

Merging duplicates in Call

In Call, possible duplicates are listed for you to review. Open Settings, go to CRM setup, and find the Possible duplicates section. Each group shows the records under Looks like the same contact, together with Matched on, which tells you what the system noticed, for example the phone number.

Merge a pair of duplicates

  1. Open the listGo to Settings, then CRM setup, then Possible duplicates.
  2. Read the evidenceCheck Looks like the same contact and the Matched on line for each pair.
  3. Confirm it is one personOpen both records if needed and compare their history.
  4. Press MergeMerge keeps the older record and moves the calls, notes and appointments onto it.
  5. Check the resultThe page confirms with Merged; open the surviving contact and read its timeline.

Two details are worth knowing. First, the older record survives, so its identifier and its name win; edit the name afterwards if the newer spelling is better. Second, if a group shows no Merge button, it does not offer a merge for that group, so review those records by hand rather than expecting the button to appear.

Preventing the next batch

Merging is cleanup. Prevention is cheaper. A few habits cut the flow of new duplicates a long way.

Habits that keep duplicates down

  • Search by number and by name before creating a new contact
  • Enter phone numbers in one consistent format, with the country code
  • Clean and de-duplicate any spreadsheet before importing it
  • Ask returning web-form users to use the same email address
  • Agree one spelling convention for names, such as the full legal first name
  • Schedule a short duplicates review at a regular interval, for example monthly

A clean import is the single biggest prevention step, so read importing contacts before you load a list.

A simple monthly routine

Reviews are quick when they are regular. A small team with a modest customer base can usually finish in a few minutes. A larger team might split the list between supervisors.

  1. Open the possible duplicates list and sort your attention to the obvious pairs first, those matched on a number.
  2. Merge the clear ones straight away.
  3. Set aside uncertain pairs and ask the agents who handled them.
  4. Note the cause of any pattern, such as one import or one web form producing most pairs, and fix that source.
  5. Check the customer view of a merged contact to confirm the history reads sensibly.

Keep a short log of what you merged and why, even if it is only a line in a shared note. When someone later asks why a customer's record shows an earlier creation date, the answer is easy to find, and the team learns which sources create the most duplicates.

Over time the list gets shorter, and the causes become visible. If one source keeps producing duplicates, change the source rather than merging forever.

Frequently asked questions

What is the difference between a duplicate and a related contact?

A duplicate is the same person recorded twice. Related contacts are different people, such as two colleagues at one company or members of one household. Merge duplicates; keep related contacts separate and link them through the company or notes.

Which record survives a merge in Call?

The older record is kept, and the calls, notes and appointments from the other record move onto it. Review the name afterwards, since the surviving record keeps the older details.

Can I undo a merge?

Not from the merge page. That is why it pays to compare both records before pressing Merge, and to restrict merging to people who know your customers.

Why does a pair match on a phone number when they are different people?

Shared lines are common: switchboards, family phones and shop counters. A matching number is strong evidence, not proof. Read the history on both records before you decide.

Do merged contacts lose their appointments?

No. Appointments, calls and notes move to the surviving record, so the full timeline stays in one place.

How often should we review duplicates?

A monthly review suits most teams. After a large import or a campaign that created many leads, review straight away.

Review possible duplicates in your Call contacts

In the demo console you can try incoming calls in a simulation.

Related guides