Duplicate seller leads in Salesforce: rules that catch them without losing leads

Why do investor CRMs fill up with duplicates?

• Sellers call from different numbers. A landline for the first mailer, a cell for the second, a spouse's phone for the third.
• Lists overlap. Absentee owners, pre-foreclosures, tax delinquent, probate: the same owner shows up on several lists, often with several skip-traced numbers.
• Lists get re-imported. Cold-calling teams load a fresh list every month, and last month's sellers come in again.
• Many doors in. Phone, web form, PPC form, text reply, a cold caller's handoff, a referral. Each one can create a record.
• Properties have more than one owner. Heirs, ex-spouses and co-owners can each become a lead for the same house.

What do duplicates cost you?

• Bad numbers. Lead counts go up, so cost per lead looks better than it is, and conversion rates look worse.
• Two reps, one seller. The seller gets two calls and two different offers, and the reps argue about who owns the deal.
• Lost history. The rep calling the new record doesn't see that the seller turned down an offer in the spring, or what their real reason for selling was.
• Compliance risk. A seller who opted out on one record can still get texts from the automation running on the other copy.

That last one is the one I'd fix first. Whatever else you do, an opt-out or Do Not Call flag on any copy should count for the person.

How does Salesforce catch duplicates?

Two pieces work together:

• Matching rules define what "the same" means: which fields to compare and how strictly. Salesforce's standard lead matching rule compares name, company, email and phone with fuzzy matching.
• Duplicate rules decide what happens when a match is found: allow the save with an alert, block it, and whether to log it to a report.

The standard rule is built for B2B sales, where a company name means something. Seller leads usually have no company, and the name is often just what the seller said on the phone. That's why investor orgs need their own matching rules, built around what actually identifies a seller: phone, email and the property.

Limits worth knowing: up to five active duplicate rules per object, up to three matching rules in one duplicate rule, and up to five active matching rules per object. A lead duplicate rule can also compare new leads against existing contacts, which matters if you convert leads.

Where do duplicate rules not run?

This is the part that catches people out. According to Salesforce, duplicate rules don't run when:

• Records are created with Quick Create.
• Leads are converted, unless the "Use Apex Lead Convert" setting is on.
• Records are restored from the Recycle Bin.
• Records are created by Lightning Sync or Einstein Activity Capture.
• Records are merged by hand.

And a few behaviors that surprise people:

• Records saved at the same time aren't compared with each other. If one import file contains the same seller twice, both get created.
• On edits, a rule only runs when an edited field is in the matching rule. Changing a seller's phone number triggers it. Changing their motivation doesn't.
• Imports and API connections can't show an alert. A rule that would show a person a warning can make an import or integration fail instead. That's what's behind an import that errors with DUPLICATES_DETECTED.

The setup I'd use for an investor team

1. Clean the keys before matching

Phone numbers arrive as (614) 555-0100, 614.555.0100 and +16145550100. Add a field that stores the number as digits only, filled by a before-save Flow, and match on that. Do the same for the property address: one cleaned street field, so "123 N Main St" and "123 North Main Street" have a chance of matching.

2. Match on what identifies a seller

• Cleaned phone, exact match.
• Email, exact match.
• Cleaned property street plus zip code.

Use them as separate conditions (phone OR email OR property), not all at once, because a returning seller rarely matches on everything.

3. Alert people, never block integrations

4. Report every match

Turn on reporting in the duplicate rule, so every match is logged. A weekly look at the duplicate report tells you which door is creating them, which is usually more useful than cleaning them up one by one.

5. Make opt-outs follow the person

When a match is found, copy any opt-out or Do Not Call flag to every matching record, and stop automations on all of them.

How should you handle list imports?

If your team cold calls, lists are likely your biggest source of duplicates, so this is where to be strict:

1. De-duplicate the file itself before import, on phone and property address. Salesforce won't compare rows in the same file with each other.
2. Check the file against Salesforce on the same keys, and split it into new sellers and sellers you already have.
3. Load only the new ones as new leads. For existing sellers, update the record or add them to the new campaign, so their history stays in one place.
4. Tag every row with the list and the campaign, so you can tell later which list produced the deal.

Your list provider or skip-tracing tool may do the first step for you. The second step is the easy one to skip.

How should you merge duplicates?

• In Salesforce you can merge up to three leads at a time, and the person merging needs Delete permission on leads. Keep that permission with ops or an admin, not every rep.
• Pick the surviving record on purpose: usually the oldest one with the most activity, so the seller's history stays together.
• Decide ahead of time which lead source wins. If the seller first came from a mailer and called back from a PPC ad, your attribution rule should decide, not whoever happens to merge. My take on that is in which campaign gets credit.
• Check opt-outs and Do Not Call on every record before you merge, and keep the strictest one.
• Do it on a schedule. A weekly 20-minute merge session beats a yearly clean-up of thousands of records.

What should happen when a seller comes back?

A seller who went quiet and then calls again is one of the best leads you'll get, and one of the easiest to mishandle. The right behavior:

1. The call or form matches the existing seller on phone, email or property.
2. Instead of a new lead going into round robin, the existing record is updated and reopened.
3. The original owner gets a notification that their seller is back, with the new source.
4. If the original owner has left, the seller goes to the queue with their history attached.

Duplicate handling that keeps the history and notifies the original owner is part of the setup I run for a two-market home-buying company in Ohio.

To bring quiet sellers back on purpose rather than waiting for them to call, see reactivating dead seller leads.

Questions

Related guides

Sources

Checked in October 2026. Salesforce and vendor features change with each release, so check the linked page before you rely on a detail.

1. Salesforce Help: Things to know about duplicate rules. Limits, when rules don't run, imports and the API, edits, records saved together
2. Trailhead: Duplicate management (unit 2). Standard matching rules and how duplicate rules use them
3. DataLane: Salesforce duplicate rules. Standard lead matching rule fields and fuzzy matching
4. Salesforce Help: Merge duplicate leads. Up to three leads at a time, Delete permission required
5. Salesforce Help: DUPLICATES_DETECTED on import (knowledge article 000391118). Why an import fails when a duplicate rule matches