Duplicate Records: Merge the Confusion Before It Becomes a Missed Job
Question: What should a service team do when the same customer, lead, job, or supplier appears to have more than one record?
Do not merge on a hunch
Similar names, phone numbers, or descriptions are signals to review, not proof that records belong together. Before changing or combining anything, open the candidate records and compare the information that your approved process allows you to use.
If identity is uncertain, assign a human review rather than merging records and risking a lost history or incorrect communication.
A safe duplicate-review checklist
- Identify the record type: lead, customer, job, work order, vendor, or another operational item.
- Compare only the minimum relevant fields.
- Check for different active work, ownership, dates, or related records.
- Decide whether one record is clearly the authoritative record.
- Preserve the reason for the decision where your team requires it.
- Update links, ownership, and next actions only after the review.
- Reopen the surviving record and verify that it still tells a coherent story.
Avoid copying private information into a message merely to prove that two records match.
Common duplicate patterns
| Pattern | Safe response |
|---|---|
| New enquiry resembles an existing customer | Review the existing record before creating a second active customer record. |
| A job was created twice | Identify which one has the correct owner and current work before changing status. |
| A vendor appears under two names | Ask the internal owner to verify the supplier identity. |
| A follow-up exists in two places | Keep one named owner and close the other only after the next step is preserved. |
Prevent duplicates going forward
Use one clear intake path, check existing records before creating new ones, and make ownership visible. When a record is incomplete, mark what needs verification instead of creating a speculative duplicate.
For lead intake, see Leads: Turn a New Request Into a Clear Next Step. For customer records, see Customers: Keep Customer Context Clear Without Guessing.
Boundaries
This guide is a record-quality process. It does not prove identity, authorization, consent, data accuracy, retention requirements, or that merging or removing a record is safe in a particular workspace. Follow your approved data-governance process before making irreversible changes.