Lead deduplication identifies multiple records that refer to the same customer inquiry and combines or links them according to a defined rule. A home service customer may submit a form, send a text, and call about one repair. Deduplication should preserve that conversation history while keeping genuinely separate properties and job requests distinct.
What is lead deduplication?
It is the process of finding repeated lead records and resolving them without losing useful history. The matching rule may consider customer identifiers, contact details, service location, request type, and time. Identifying the same person is not enough to prove two opportunities are the same job.
Why do duplicate home service leads occur?
A customer may use several channels, retry after receiving no response, or submit the same request through a lead provider and the business website. Integrations can also retry record creation. Preserve the source events so the office can identify whether duplicates came from customer activity or system behavior.
Should all leads sharing a phone number be merged?
No. Household members, property managers, and business contacts can share numbers, and one customer can request several jobs. Use additional context and a stable request identifier where available. Ambiguous cases should remain reviewable rather than being automatically combined.
What information should survive a lead merge?
Preserve original sources, timestamps, conversation history, active tasks, customer preferences, and relevant job or estimate references. Decide which verified values remain current. Avoid dropping a newer address or unresolved callback simply because an older record is designated as the primary lead.
How should deduplication quality be measured?
Track confirmed duplicates resolved, mistaken merges, remaining repeated records, and duplicated staff contacts. Audit examples after integration changes. The goal is one coherent record per actual inquiry, not the lowest possible lead count.
Related terms: Lead Capture, CRM Integration, Customer Conversation History