Separate the person from the request
Two records can describe the same person and still represent different work. A homeowner asking about a kitchen repair in May and a garage repair in September has not necessarily submitted a duplicate inquiry. One household may also share a phone number while different people arrange different visits.
Start with the request: what work is being discussed, where, and in which conversation? Then check identity using information already available to the authorized team. A matching number is a reason to review, not permission to combine histories or disclose one person’s information to another.
The immediate objective is one clear next action for this request. A cleaner customer list can come later, after someone has established what actually belongs together.
Work through a repeated repair inquiry
Fictional example: Jordan leaves a voicemail about a leaking kitchen tap at 9:10. At 9:18, Jordan submits a form about the same tap, explaining that Thursday morning works for a visit. Sam has the voicemail; Lee has the form.
Sam and Lee compare the relevant details and confirm that both entries concern the same request. They agree that Lee owns the response and carries forward Thursday’s availability. Sam marks the callback task as covered by Lee’s response, with a reference to the current request.
No one needs to delete the voicemail to prevent two callbacks. Preserve its source and timing. If the form instead described a separate rental property, the team would keep two requests and check which person can authorize each visit.
Use a decision sheet before combining records
Copy this review sheet for a sample pair. Use internal references instead of putting customer details into a shared worksheet.
On a small screen, swipe or scroll sideways to read the full table.
| Check | Record the evidence | If uncertain |
|---|---|---|
| Same person? | Which reliable details agree, and which conflict? | Keep identities separate pending review. |
| Same request? | Compare the work, location, timing and conversation. | Keep separate request histories. |
| Current information? | Identify the latest relevant instruction and its source. | Ask a focused clarification through an appropriate channel. |
| Who responds? | Name one owner who has accepted the next action. | Assign the unresolved handoff for review. |
| Other actions? | Identify any competing callback or reminder. | Review it before another person contacts the customer. |
Finish the sheet with a decision: separate, linked for this request, or unresolved. Add the reviewer and date. “Linked” describes a working decision; it does not mean records were technically merged.
Try the decision sheet on three different pairs.
The blank duplicate-inquiry comparison sheet (CSV) makes the review above reusable. Use one row per pair and internal record references. If the evidence is incomplete, record what needs clarifying and who will check it.
On a small screen, swipe or scroll sideways to read the full table.
| Pair to review | Decision supported by these facts |
|---|---|
| Nora’s voicemail and form concern the same exterior-window job at the same property. The form adds a preferred day. | Link the sources for this request. Carry forward the preference, retain both records and agree one next-action owner. |
| Nora then asks about cleaning windows at another property. | Keep a separate request with its own next action. The same person does not mean the same job. |
| Two names share a household phone number but describe different work. | Keep the requests separate and identity unresolved. Clarify who is involved before sharing either person’s details. |
These decisions concern the next step; none instructs you to merge customer accounts. Keep any contact restrictions visible whichever decision you choose. If the problem is a changed instruction inside one conversation, use the conversation-handoff guide.
Preserve the parts a tidy list can hide
A combined view should not erase which channel the customer used, what they asked, or what the team promised. Keep an audit trail of meaningful decisions. Check contact restrictions and recorded preferences before any further outreach; a second record should never become a way around a stop-contact instruction.
If records really need merging, have the responsible administrator review the intended surviving record, conflicting fields, associated requests and recovery options first. Do not run a bulk cleanup because a spreadsheet flagged matching numbers. The right decision may be to retain both records.
Salesforce’s duplicate-record guidance distinguishes intentional from unintentional duplicates and discusses false matches from shared contact details. That distinction informs this review; the worksheet and repair example are JetSynapse’s own practical suggestions.
Rehearse the exceptions
- One person submits the same request through two channels. Can the team agree on one next action without losing either source?
- Two people share a number but ask about different work. Can the team keep their requests distinct?
- An older record contains a contact restriction. Does the review surface it before anyone follows up?
- The details conflict. Is there an explicit unresolved state and someone responsible for clarifying it?
A useful cleanup ends with a decision the next person can understand. Measure unresolved pairs and competing follow-up tasks separately from the total number of customer records. Fewer rows alone do not prove a better customer experience.
Explore From the first inquiry to a clear booking. for related questions and a useful starting point.