How to Fix Duplicates in Salesforce with Delpha – Automatic, Bulk & Manual Options

Discover how to fix duplicate records in Salesforce using Delpha. Learn about automatic merging (Auto Yes), bulk cleanup in the Steward View, and record-level deduplication with the Delpha Bot.

Automatic Merge – When Status = Auto Yes

Delpha runs automatic duplicate detection every 12 hours. When a detected pair's score exceeds the Auto Merge Threshold, its status is set to Auto Yes.

What happens then?

The pair is automatically queued for merging.
Scheduled tasks run daily and process all Auto Yes pairs.
The master record is selected based on the configured merge rules (e.g. oldest record, most filled, or custom score) and the fields are selected based on the Merge Field Rules.

Mass Processing in the Duplicate Data Steward View

When duplicate pairs are flagged as Potential or Auto No (filtered but not merged), you can review and process them in bulk from the Duplicate Data Steward View.

In the Steward view you can:

Filter by object type, score, or status
Review field-by-field comparisons with color-coded indicators
Select multiple pairs to:
- ✅ Accept → will be merged in the next batch (status = Steward Yes)
- ❌ Reject → will be ignored forever (status = Steward No)
- 🗑️ Delete → removes one or both records from Salesforce

This method gives you control while accelerating cleanup at scale.

What happens then?

The pair is automatically queued for merging.
Scheduled tasks run daily and process all Steward Yes pairs.
The master record is selected based on the configured merge rules (e.g. oldest record, most filled, or custom score) and the fields are selected based on the Merge Field Rules.

Record-Level Merge – Delpha Bot

If you're working on a single record (e.g. Account, Contact, Lead, Lead Vs Contact or Person Account), the Delpha Bot allows you to process duplicates directly in context.

How it works:

The bot pops up automatically (if enabled) when a potential duplicate is detected.
You get a side-by-side view of the record and its potential match.
You can:
- ✅ Accept and merge immediately (status = User Yes)
- ❌ Reject if it's not a duplicate (status = User No)

You can configure which fields are visible and what rules apply in Delpha Setup > Duplicate Settings.

PreviousHow to make Duplicate Records exclusion dynamic NextHow to modify the detection threshold

Last updated 1 day ago

Was this helpful?

Automatic Merge – When Status = Auto Yes

Delpha runs automatic duplicate detection every 12 hours. When a detected pair's score exceeds the Auto Merge Threshold, its status is set to Auto Yes.

What happens then?

The pair is automatically queued for merging.

Scheduled tasks run daily and process all Auto Yes pairs.

The master record is selected based on the configured merge rules (e.g. oldest record, most filled, or custom score) and the fields are selected based on the Merge Field Rules.

Mass Processing in the Duplicate Data Steward View

When duplicate pairs are flagged as Potential or Auto No (filtered but not merged), you can review and process them in bulk from the Duplicate Data Steward View.

In the Steward view you can:

Filter by object type, score, or status

Review field-by-field comparisons with color-coded indicators

Select multiple pairs to:

✅ Accept → will be merged in the next batch (status = Steward Yes)
❌ Reject → will be ignored forever (status = Steward No)
🗑️ Delete → removes one or both records from Salesforce

This method gives you control while accelerating cleanup at scale.

What happens then?

The pair is automatically queued for merging.

Scheduled tasks run daily and process all Steward Yes pairs.

The master record is selected based on the configured merge rules (e.g. oldest record, most filled, or custom score) and the fields are selected based on the Merge Field Rules.

Record-Level Merge – Delpha Bot

If you're working on a single record (e.g. Account, Contact, Lead, Lead Vs Contact or Person Account), the Delpha Bot allows you to process duplicates directly in context.

How it works:

The bot pops up automatically (if enabled) when a potential duplicate is detected.

You get a side-by-side view of the record and its potential match.

You can:

✅ Accept and merge immediately (status = User Yes)
❌ Reject if it's not a duplicate (status = User No)

You can configure which fields are visible and what rules apply in Delpha Setup > Duplicate Settings.