Feature Overview
Duplicate Detection Rules are designed to flag potential duplicate records during creation or updates. When a user clicks the Save button, the system checks for matching data across existing Client or Contact records. If a match is found, the user is alerted and can choose to either cancel the new record or if updating, contact a Mercury Administrator to merge the duplicates.
Purpose
Applying these rules helps prevent the creation of duplicate records in Mercury, ensuring your CRM data remains accurate, consistent, and high quality.
Default and Considerations
The default rules for Clients are:
- Where 'Client Name' matches another client
- Where 'Website' matches another client
- Where 'Main Phone' matches another client
The default rules for Contacts are:
- Where first name, last name and client match another contact
- Where ‘Personal Email’ matches another contact
- Where ‘Personal Mobile' matches another contact
- Where ‘Work Email’ matches another contact
- Where ‘Work Mobile' matches another contact
When setting up duplicate detection rules, it's important to strike a balance: rules that are too narrow may miss genuine duplicates, while overly broad rules can flag unrelated records that simply share similar data. The goal is to fine-tune the criteria to catch true duplicates without generating false positives. The rules outlined above are most commonly successful.
Only Mercury Administrators have permissions to merge records as there is no “undo” option once the merge is complete.
To Enable or Amend this Feature
This feature will be enabled as standard as per the defaults above. Should you wish to make any amendments please provide your Mercury Product Consultant with the following:
- Additional or amended rules
-
The names of any users (ideally a designated team) who should also be granted merge permissions