Why this matters
Duplicate leads hide response problems
Duplicate inquiries are usually a buying-signal, not just a data-cleanup nuisance. A prospect may be trying multiple channels because they have not received a clear next step. If the records stay separate, the team can over-message, under-message, double-book, or lose attribution.
The fix is a short merge routine: confirm the person, preserve every source, pick one owner, and send one clear next-step message.
Copy/paste artifact
Duplicate lead merge worksheet
Lead name / business: [paste]
Phone/email: [paste]
Possible duplicate records: [CRM ids / source links]
Human reviewer: [dispatcher / office manager / owner]
1. Match check
[ ] same phone number
[ ] same email
[ ] same address or service location
[ ] same service request
[ ] same marketplace/profile name
[ ] uncertain match — do not merge until a human confirms
2. Preserve source history
First source: [call / form / text / ad / marketplace / referral]
Second source: [paste]
Latest source: [paste]
UTM/campaign if available: [paste]
Original timestamp: [paste]
Latest timestamp: [paste]
3. Current truth
Current request: [what they need now]
Urgency/safety flag: [none / urgent / safety review]
Latest promised next step: [paste only if already promised]
Assigned owner: [name]
Next action due: [date/time]
4. Merge decision
[ ] merge records
[ ] link records but keep separate
[ ] keep separate because match is uncertain
Final master record id: [paste]
5. Stop rules
Do not invent contact attempts, lead source, promised arrival windows, pricing, diagnosis, eligibility, consent, or customer intent. If history is missing, mark it as missing.Customer-safe replies
Two short messages after a duplicate is found
Same-day clarification:
Hi [Name] — thanks for reaching out. I see your request came through more than one channel, so I am keeping everything together under one request to avoid duplicate messages. The next step is [NEXT STEP], and [OWNER] will follow up by [TIME].
Uncertain match:
Hi [Name] — quick check: did you also send us a request through [CHANNEL] about [SERVICE/ADDRESS]? I want to make sure we do not mix your request with another customer before we reply with next steps.AI assist prompt
Prompt for a no-invention merge summary
You are helping a local service business summarize possible duplicate lead records.
Use only the records I provide. Do not invent contact attempts, customer intent, source attribution, pricing, diagnosis, availability, promises, consent, or urgency.
Return:
1. whether the records look like a confident match, possible match, or not enough evidence,
2. the exact evidence for the match,
3. the preserved source/timestamp list,
4. the latest known customer request,
5. missing facts a human must verify,
6. one customer-safe reply draft if a reply is appropriate.
Records:
[paste records]Next step
Pair the merge with reason codes
After merging duplicates, review the lost-lead reason code checklist and the lead source tracking worksheet so duplicate records do not distort weekly reporting.
For a fuller lead-response workflow, use Local Lead Rescue System.