CRM & sales / GUIDE + WORKSHEET
Why CRM duplicates keep coming back
Trace duplicate records to their creation paths, identify ownership conflicts, and use an event worksheet to prevent recurrence.
THE STARTING POINT
Recurring duplicates usually require an investigation of record creation, not another round of merging. Trace where each copy originated, which identifier it used, and whether a retry or a competing workflow created it. Define who owns creation and send uncertain identity matches for review.
Trace a pair of duplicates to their origin
Choose a recent pair and compare creation time, source form, import batch, integration history, and the IDs in other systems. Similar timestamps may suggest a retry or simultaneous writers, but are not proof. Preserve the event evidence before merging the records, otherwise the cleanup can erase the clue you need.
Agree on identity and creation ownership
List every route that can create a customer: website forms, staff entry, billing sync, event imports, and partner feeds. Decide which stable identifiers travel between systems and which system should create the master record. An email can be shared or changed; a name is not a reliable unique key. Document what happens when a match is uncertain.
Test repetition and simultaneous work
Run controlled tests for the same event arriving twice, a response being lost, and two workflows arriving together. A lookup followed by creation can still race with another writer. Ask the implementer how uniqueness, repeated requests, and conflict review are handled. Confirm the final destination state rather than trusting only a successful workflow badge.
WORKED EXAMPLE / ILLUSTRATIVE
One enquiry, two creation paths
In this fictional trace, the web form and billing integration both create the same customer without sharing a customer ID. Cleanup removes the symptom; changing ownership prevents this particular cause from repeating.
| Event | Identifier used | Observed result |
|---|---|---|
| Form received | Form submission F-108 | Creates customer C-21 |
| Billing contact synced | Billing ID B-55 | Creates customer C-22 |
| Ownership corrected | Shared customer ID C-21 | Billing links to the existing customer |
MAKE IT USEFUL
Duplicate origin investigation
Use a recent duplicate pair and keep the trace with the eventual fix.
Your notes stay in this page and are not sent to Smithers. Download or copy them before leaving; refreshing clears them.
Before you put it to work
- Preserve creation evidence before merging.
- Test two writers, not just one happy path.
- Verify actual destination records.
- Monitor recurring exceptions.
Deduplication inside one trigger is not a guarantee across every workflow or destination. Zapier documents different trigger and action behaviors; check the actual apps involved.
Source notes
These references support the specific product or technical points discussed above. Checked September 24, 2026.
IF THIS LOOKS FAMILIAR
Your tools. Your particular mess.
The worksheet is yours to use. If the difficult part is making it work with the systems you already have, that's the kind of thing we help with.