
Duplicates creep in over time — the same person entered twice, or imported again. AI Engage CRM helps you both prevent and clean up duplicates.
Email is unique, so a repeat email is caught immediately. Your admin can also turn on duplicate detection across other fields (e.g. name + phone); when it is on, creating a contact that looks like an existing one shows a warning with the possible matches, and you can open the existing record, merge, or save anyway.
To configure duplicate detection for a module:
Go to Settings. Navigate to Customization → Modules and Fields. Locate the module you want to configure. Click Configure beside the module.

Click Settings in the top-right corner of the module builder.

Open the Features tab. Enable the Duplicate Check & Merge toggle. Configure the duplicate matching settings.

The Duplicate Matching Criteria determines which fields the CRM uses to identify duplicate records.
Click Select Fields and choose one or more fields that should be compared when checking for duplicates.
For example:
Phone Number
Company Name
Website
Customer ID
Note: At least one field must be selected before duplicate checking can be enabled.
Choose how the selected fields should be evaluated when searching for duplicate records.
The CRM considers a record a duplicate only when all selected fields contain matching values.
Selected fields:
Phone Number
Existing Record | New Record | Result |
|---|---|---|
Email ✔ Phone ✔ | Email ✔ Phone ✔ | Duplicate |
Email ✔ Phone ✘ | Email ✔ Phone ✘ | Not a duplicate |
This option provides stricter duplicate validation and helps reduce false matches.
The CRM considers a record a duplicate if any one of the selected fields matches.
Selected fields:
Phone Number
Existing Record | New Record | Result |
|---|---|---|
Email ✔ Phone ✘ | Email ✔ Phone ✔ | Duplicate |
Email ✘ Phone ✔ | Email ✔ Phone ✔ | Duplicate |
This option is useful when a single unique identifier, such as an email address or phone number, is sufficient to identify duplicate records.
Select when the CRM should perform duplicate validation.


When enabled, duplicate detection is performed whenever a new record is created.
If a matching record is found, the user is notified before the record is saved.
When enabled, duplicate detection is also performed whenever an existing record is updated.
This helps prevent updates that may unintentionally create duplicate records.
Enable this option to allow users to manually search for duplicate records and merge them.
This is useful for cleaning existing data that was created before duplicate detection was configured.
From the Contacts list, open the menu (top right) and choose Deduplicate Contacts.

Pick up to three fields to match on (for example First Name, Email, Phone) and click Continue. The CRM scans for duplicates in the background and emails you when it is done with a link to review.

Exact matches can be merged automatically; anything that needs a decision is listed as a conflict for you to resolve. When you merge, you choose the master record to keep and, where values differ, which value to keep. All related records — deals, activities, notes — move onto the master, and the duplicates are archived.
Merges are not permanent — a completed merge can be reverted. Every merge is logged in Merge History. From the Contacts list, open the More actions (⋯) menu and choose Merge History (the same menu as Deduplicate Contacts).
The panel lists recent merges, newest first. Each entry shows the master record that was kept, a "{n} merged" badge for how many records were merged in, and who performed it and when. A merge is restorable for 30 days; after that — or if it has already been restored — the Restore button is disabled and shows the reason ("Outside the 30-day window" or "Already restored").

Click Restore on a merge, then confirm "Restore this merge?". Restoring will:
Recreate the merged-away duplicate record(s) and re-activate them, with their original field values restored.
Roll back the master record's field values to what they were before the merge — while keeping any edits you made to the master after the merge.
Restore a merge — up to 30 days after the merge, from Merge History.
Resolve conflicts from a Deduplicate run — the review link in the completion email stays active for about 3 days. After it expires, run Deduplicate again for a fresh scan.

OpenAI Engage and apply what you just learned to your own workspace.
Open AI Engage CRM