CRM Operations
The Same Buyer Enquired Twice: How to Handle Duplicate Leads Across Channels
A repeated phone number may be a duplicate submission—or a new buying requirement. Preserve the enquiry before deciding what to merge.
A buyer fills out your website form on Monday and sends a WhatsApp message on Tuesday. On Wednesday, the same phone number arrives through a marketplace enquiry. Three salespeople call, each believing they own a new lead.
Duplicate leads in a CRM create more than untidy reports. They can cause conflicting quotes, repeated introductions and lost context. The fix begins by distinguishing a duplicate record from a legitimate new enquiry by an existing person.
Separate the person from the requirement
A contact represents someone you communicate with. An enquiry or opportunity represents something they want to buy. Depending on your CRM’s structure, these may be separate objects or information stored within one record. Either way, the business distinction matters.
A facilities manager requesting chairs for a second office is not simply a duplicate to delete. The contact may be the same while the quantity, delivery address, timeline and decision process are new.
Normalize identifiers before comparing them
Spaces, punctuation and country-code formatting can make the same phone number look different. Use a consistent representation and preserve the original value where needed for review. Do not guess that every number belongs to the same country.
A matching name is weak evidence. A shared switchboard, family phone or generic company email can belong to several people. Review context before combining records, especially when different names or organizations appear.
| Situation | Safer decision |
|---|---|
| Same external event delivered again | Treat as a retry when the integration identifies it reliably. |
| Same person, same requirement | Preserve the latest conversation and use one clear owner. |
| Same person, new purchase | Keep the new requirement distinct within the supported CRM model. |
| Same number, conflicting identities | Review manually before merging. |
| Similar name only | Do not merge on name similarity alone. |
Preserve history before changing records
Check conversations, notes, tasks, attachments, quotations, stage history and source fields. Decide which record is authoritative and what must be retained. A merge that keeps the name but loses the promised callback has not improved the customer experience.
If your CRM does not support a safe merge for the information involved, use its supported review process. Do not delete a record merely to make a duplicate count smaller. Keep a record of the decision and the owner responsible.
Understand each integration’s behavior
Different connectors can identify retries differently. SHVYA’s JustDial integration uses the external lead ID to recognize repeated delivery, while a new enquiry ID with the same normalized phone can update an existing lead. That behavior should not be generalized into a claim that every channel automatically merges every duplicate.
Check the relevant event log and actual record result. The JustDial guide explains the setup checks. For spreadsheet imports, read the Excel migration checklist before uploading a file twice.
Resolve ownership before the next call
Once the team recognizes the shared buyer, nominate one current owner or an explicit collaboration rule. Read the latest conversation before replying. A simple internal note can prevent a second salesperson from offering a different price or asking questions already answered.
Keep original acquisition source and later enquiry source distinguishable where your fields allow it. Otherwise, duplicate cleanup can distort the lead source comparison.
Use a repeatable review checklist
Ask: Is identity confirmed? Is the requirement the same? Which history must survive? Who owns the next action? What will happen if another event arrives? Test these questions with fictional records before bulk changes.
Review duplicate enquiry handling with SHVYA. Bring redacted examples from two channels. The aim is one coherent customer conversation without erasing legitimate buying activity.
