A duplicate check can prevent two teams from calling about the same request, but a false match can hide a genuinely separate need. Define what counts as a possible match, which evidence is compared, and who decides whether records should be linked.
Examples below are illustrative. Do not merge personal records merely because a name, company or phone number looks similar.
Separate match signals from match decisions
Use a stable identifier where the organization has permission and a supported system, then compare contextual fields such as request date, product and stated reason. A shared household number or company switchboard can be used by different people; a changed email can belong to the same person. Signals identify a review candidate, not proof that two records are identical.
HubSpot’s current knowledge base describes record deduplication and merge behavior for that product. Treat those controls as vendor-specific and check your own CRM’s matching and merge behavior before designing an integration.
A review queue that protects distinct requests
- 1Create or retain the new enquiry with its own source and timestamp.
- 2Flag the candidate match and list the fields that agreed or conflicted.
- 3Have an authorized reviewer compare the request context and choose link, merge, keep separate or request clarification.
- 4Preserve the original records and the decision reason according to the CRM’s audit capabilities.
- 5Check that a follow-up owner remains assigned after the decision.
Worked example: same number, different need
Illustrative case: two enquiries share a family phone number. One concerns a rental property; the other asks about a sale listing. The number alone is not enough to merge them. A reviewer keeps separate requests, verifies each preferred callback recipient and assigns the correct team.
If a duplicate is confirmed, do not count the second record as a second unique prospect without defining that metric. Keep attempt counts and unique people or requests separate.
A little more before you begin.
Can an AI agent automatically merge duplicate leads?
Only if a tested product workflow explicitly supports it and the business has approved the matching rule. This guide does not claim that capability for HeyRik.
Which field is a safe universal matching key?
There is no universal key for every CRM and use case. Use the account’s approved identifiers and review exceptions.
Start here
Map your duplicate-review process
Build a voice agent, upload your list or connect your leads, and run your first campaign on HeyRik — free to start, no credit card required.