Workflow automation

How to Stop Duplicate Customer Records

A customer fills in your form twice. Two staff members contact them, and their notes end up in different places. Duplicate records can start with something this small. The fix is a clear matching rule at the point where new details enter your system.

By Automations For BusinessPublished October 20, 20265 min read

Key takeaways

Choose one main customer list.

Keep the customer ID across tools.

Search before creating records.

The short answer

Choose one main customer list. Search it before creating a record, using the system’s customer ID where possible. Update a clear match, create a record for a genuinely new customer and send uncertain matches to a person. Test repeated submissions and imports.

Find the customer
Update a clear match
Review uncertain matches
Record completed work

Choose the main customer list

Name the system that holds the customer record your team trusts. It might be your customer-management app, booking tool or a well-kept spreadsheet. Other tools should refer to that record rather than each inventing a new version.

List how customer details arrive: website forms, shop orders, manual entries and imported lists. Check each route. Fixing one form will not stop another import from creating the same problem.

Decide what counts as the same customer

A customer ID is the unique reference your main system gives a record. Keep that reference when sending details to another app, so the next update can return to the same record.

For a new person without an ID, an exact email match may be useful. It is not perfect: two people can share an address, and one person can use several addresses. A matching name alone is not enough to merge records.

HubSpot, for example, uses email addresses for contact matching and supports Record IDs when importing updates. Its rules differ by entry method and record type. Check the rule for the specific route you use, especially when another app connects through an API.

Search first, then choose the next step

When new details arrive, check for a valid customer ID first. If there is none, search using your agreed matching field. Remove accidental spaces and apply a consistent format before comparing values.

If there is one clear match, update only the fields you intend to change. A blank form answer should not erase a useful phone number. Keep the existing owner and important notes unless your rule explicitly says to replace them.

If there is no match, create a new record and store its ID. If there are several possible matches, put the item in a short review list. Guessing can mix two people’s contact details and history.

A repeat enquiry should stay with one record

Here is an example. Sam submits an enquiry on Monday and again on Tuesday using the same email. The first submission creates customer C104. The second finds C104 and adds the new enquiry to that customer’s history.

The team can still see two enquiries. It does not need two customer records. If the second form has a blank phone field, the stored phone number stays.

Now suppose a colleague uses the same shared office email but gives a different name. Send that case for review under your shared-address rule. Do not silently replace Sam’s details.

Check what happens when a job runs twice

A repeat submission and a repeated automation run are different problems. Keep the source submission or event reference as well as the customer ID. If the same event is retried, check whether its work already finished.

Zapier explains that duplicate handling in an action depends on the receiving app. A trigger’s duplicate checks do not mean every later create-record step is safe. Two separate workflows using the same trigger can also both run.

Test the receiving app’s find-and-update behaviour. Where possible, use its unique-field checks or create-or-update action. A simple search followed by create can still race if two requests arrive together.

Clean existing duplicates carefully

Export a recovery copy before merging records, and check what the tool keeps or discards. Review ownership, conversation history, orders and marketing preferences. A merge should not turn an opted-out contact back into a subscriber.

Fix the route that created the duplicates before working through the old list. Otherwise the same records may appear again after your cleanup.

Use the worksheet below to test a new customer, a repeat form, a changed email, a shared address and a repeated run. For help connecting forms and customer records, send Automations For Business your current tools and the problem on WhatsApp.

Your ready-to-use checklist

0 of 6 checked

Choose one main customer list.Keep the customer ID across tools.Search before creating records.Do not match by name alone.Review uncertain and shared-address cases.Test repeated events and imports.

Make the next step clear.