Call Center Outsourced evidence brief · Desk review · Published
How should a contact center resolve duplicate customer records from two intake systems?
A duplicate-record method with verified match keys, a separate merge review, protected consent, and prevention at intake.

On this page
- Key stats
- Key takeaways
- Question and scope
- What the evidence supports
- Define a duplicate
- Find the sources of creation
- Choose verified match keys
- Separate a match from a merge
- Keep the audit trail
- Set a merge approval threshold
- Decide the surviving record
- Handle conflicting consent
- Move open promises
- Prevent duplicates at intake
- Test the rules on a sample
- Keep the customer's history readable
- Tell the customer when needed
- Measure the duplicate rate
- Assign an owner on both sides
- Limits of the evidence
- Manager review questions
- Conclusion
- Put this into a support lane
- Related operating guides
- FAQs
- Sources
Key stats
- 2.67 million U.S. customer service representative jobs in 2025 (BLS)
- $21.53 median hourly wage in May 2025 (BLS)
- 289,500 projected annual openings, 2025 to 2035 (BLS)
Key takeaways
- Match on verified attributes, never on a name alone.
- Keep matching and merging as separate steps with a reviewer in between.
- Move open promises and keep the stricter consent choice when records conflict.
- Fix the intake path so the queue stops creating new duplicates.
Question and scope
This brief asks how a contact center should resolve duplicate customer records created by two intake systems. The population is an operation that receives requests through a client CRM and a separate ticketing or chat platform. The unit is a customer identity that appears more than once. The analysis covers detection, matching, merging, and prevention, not the client's master-data program. Record the two systems and the fields each one owns; list the systems, the fields, and the team that owns each record before choosing a match rule.
What the evidence supports
Federal identity guidance separates identity resolution from authentication and asks organizations to validate the evidence they use to link a person to a record. Data-quality guidance asks for documented sources and known limitations. Neither source defines a merge rule for a contact center. The operating inference is to match on verified attributes, keep the audit trail, and merge only when the evidence supports it. Write the inference in the guide so a reviewer can see the reasoning, not only the outcome.
Define a duplicate
A duplicate is two records that describe the same customer and the same relationship. Two records with the same name are not necessarily duplicates. A shared household, a common name, or a reused phone number can produce a false match. Write the definition with the attributes that count as evidence. A loose definition creates merges that are hard to undo; test the definition on ten pairs that look alike but are different customers.
Find the sources of creation
Find where the second record comes from. Common causes include a web form that does not check the CRM, a chat tool with its own contact list, and an agent who creates a new record instead of searching. Count the creations by source and by week. The source with the most duplicates usually has the cheapest fix. Rank the sources by volume and by the cost of the duplicates they create.
Choose verified match keys
Choose the attributes that reliably identify the customer, such as a verified account number or a confirmed email plus a recent interaction. Treat a name alone as weak evidence. Rank the attributes by how often they are wrong. A match rule built on weak keys will merge strangers. Record why an attribute is trusted, because a phone number can be shared or reassigned.
Separate a match from a merge
A match is a candidate pair for review, while a merge changes the record of truth. Keep the two steps separate. A reviewer should see the evidence before any data moves. The separation prevents an automated rule from making an irreversible change. Show the reviewer the candidate pair and the evidence, and require a reason for the decision, and keep the candidate list separate from the merged record.
Keep the audit trail
Record both record identifiers, the fields compared, the reviewer, and the decision. Keep the pre-merge values for the retention period. The trail should let the team reconstruct what the customer saw before the merge. Without it, a later dispute becomes a guess. Keep the audit trail in the same system as the merge so a later reviewer can find it.
Set a merge approval threshold
Decide which merges need a second reviewer. A high-confidence match on a verified account number may need one reviewer, while a name and address match may need two. Write the threshold so the queue does not rely on individual judgment. Review a sample of low-threshold merges each month. The rule should be strict enough to prevent a wrong merge and simple enough to use during a shift.
Decide the surviving record
Decide which record survives and which fields it keeps. The older record is not always the better one. Prefer the record with the verified contact data and the open promises. Copy the missing fields before closing the other record. Write the rule so two reviewers reach the same choice; test the surviving-record rule with a pair where the older record has the better contact data.
Handle conflicting consent
Two records may carry different marketing or contact preferences. The merge must not widen consent. Keep the more restrictive choice unless the customer confirms a change. Record which preference survived and why. A merge that silently opts a customer in is a privacy failure, so check the consent record before and after the merge and keep the stricter value in the surviving record.
Move open promises
Before closing a duplicate, move every open case, promise, and attachment to the surviving record. Check the due dates and the owner. A promise lost in a merge becomes a broken commitment. Confirm the move with the team that owns the work. List the open promises before the merge and confirm each one after it, and check the new owner can open every attachment.
Prevent duplicates at intake
Add a search step before a new record can be created. Search on the verified key, not only the name. Show the agent the closest matches and require a reason to create a new record. A short reason field makes the duplicate pattern visible. Review the reason field each month to see which intake path creates the most duplicates, and review the reason field with the intake owner.
Test the rules on a sample
Test the match and merge rules on a sample of known duplicates and known non-duplicates. Include names that look alike and customers who share an address. Measure false merges as well as missed matches. A rule that catches everything usually merges too much. Keep the false-merge count beside the match count so a high catch rate is not mistaken for quality.
Keep the customer's history readable
A merged record should still show the customer's earlier contacts in a way an agent can read. Keep the source, the date, and the channel for each interaction. Do not bury the history in an audit table that only a specialist can open. Test the merged view with an agent who did not perform the merge. If the agent cannot explain the history, the merge is not finished.
Tell the customer when needed
Tell the customer when a merge changes what they see, such as a combined history or a new reference number. Keep the message short and free of internal jargon. Give them a way to correct a wrong merge. A silent merge can look like a data breach. Use the customer's preferred channel and keep the message short enough to read on a phone.
Measure the duplicate rate
Measure the duplicate rate as a share of active customer records, not as a raw count. Track new duplicates created per week and the share resolved within the target window. Keep the denominator stable. The trend shows whether prevention is working. Report the rate by source system so the owner of the creation path can see the effect, and keep the denominator the same across reports.
Assign an owner on both sides
Name one owner for the duplicate queue and one owner for each source system. The queue owner triages and merges, while the source owner fixes the creation path. Without both roles, the team cleans the same duplicates every month. Put the names in the operating guide. Put both owners in the operating guide and review the arrangement each quarter, and record the date of the last review.
Limits of the evidence
This brief cannot guarantee that a match is correct for a specific customer. Identity evidence can be stale, shared, or forged. The method reduces the risk of a wrong merge but does not remove it. Keep a reversal path for the cases that turn out to be wrong. Keep the reversal procedure short enough to use during a live customer call.
Manager review questions
Managers should ask which systems create duplicates, which attributes are trusted, and who can approve a merge. They should also ask how a customer can correct a wrong merge. Record the answers with the sample results and the review date. Ask how many merges were reversed last quarter and what caused them. Put the answers with the sample results so the next review can check them.
Conclusion
Resolve duplicates with verified evidence, a separate review step, and a full audit trail. Move open promises and protect the stricter consent choice. Fix the intake path so the queue stops recreating the same problem. The record is trustworthy when the merge can be explained and reversed. Review the merge rules after any change to either intake system, and keep the reversal path in the same guide.
Put this into a support lane
Bring the two intake systems, the match keys, and a sample of open duplicates so the review can test a real merge.
Review the record mergeRelated operating guides
FAQs
Can two records with the same name be merged automatically?
No. Common names and shared households produce false matches. Require a verified key and a review.
What if a merge turns out to be wrong?
Use the audit trail to reverse it and tell the customer what changed. Keep the pre-merge values long enough to reconstruct the record.