Salesforce duplicate rules not working? Why they miss real duplicates

How Salesforce duplicate rules work

There are two parts. A matching rule decides when two records count as the same. A duplicate rule decides what happens then: allow the save with an alert, or block it.

So when a duplicate slips through, look at the matching rule first. It did not see a match, or the record came in a way nobody was alerted.

1. The matching rule is too strict

A matching rule that needs name AND email AND phone to agree misses the person who typed a new email. Real duplicates differ somewhere.

• Leads and contacts: match on phone OR email, not on name. Names are spelled in different ways; a phone number is not.
• Opportunities: match on name plus phone, or name plus email.
• Accounts: match on the account name with fuzzy matching, plus phone or website.

Fuzzy matching on names catches "Jon" and "John". Exact matching on phone only works if phones are stored in one format, so clean the format first.

2. The duplicate came from a form, a call or an integration

Records from web forms, call tracking and other integrations come in through the API. A rule set to alert lets them save, and there is no user on the other end to see the alert. Each entry path needs its own check.

• Web forms: search for an existing lead or contact by email or phone before creating a new one.
• Call tracking: match the caller's number to an existing record before a new lead is created.
• Extra phone fields: an emergency contact's number on the record can match the wrong person. Leave it out of matching.
• Historical uploads: run the import with the duplicate rules on, or dedupe the file first.

3. Matches exist, but nobody sees them

An alert-only rule saves the record and moves on. Unless the Potential Duplicates component is on the page layout, nobody is reminded later.

• Add the Potential Duplicates component to the lead, contact and account record pages.
• Build a duplicate record set report, so an admin can work the list.
• Block, instead of alert, where a duplicate does real harm, like person accounts.

4. The merge itself fails

Your team finds the duplicate, clicks Merge, and gets an error. Merging saves the surviving record, so every rule on it runs.

• A validation rule on the account name, or on any field, that the merged values break.
• A required field that is empty on the record you keep.
• A user without delete access on the records being merged.

Fix the rule so it allows the merge, not by switching it off for everyone. A bypass permission for the people who merge works well.

Clean up the duplicates you already have

We set up and clean up duplicate rules on leads, opportunities, business accounts and person accounts in the Salesforce orgs we support. Book a free call if yours keep slipping through.