> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-duplicate/how-to-fix-duplicates-in-salesforce-with-delpha-automatic-bulk-and-manual-options.md).

# 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.&#x20;

## **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

{% hint style="warning" %}
This method gives you **control** while accelerating cleanup at scale.
{% endhint %}

**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.&#x20;

## **Record-Level: Delpha Merge Editor**

If you're working on a single record (e.g. Account, Contact, Lead, Lead Vs Contact or Person Account), the [Score Meter allows you to process duplicates directly in context](https://help.delpha.io/pages/TXkLPi5ENGXFxkUoaHiu#id-3.-duplicate-review-and-fix-potential-duplicates).

### Step 1: From the Score meter, select the duplicates pairs to process

After clicking the link in the Score meter, the Duplicates Merge Editor opens automatically and presents the potential duplicates related to your current record.&#x20;

You get the some information (score, comment, fields value...)  to decide whether or not the proposed duplicate is legit.&#x20;

<div align="left"><figure><img src="https://2667079222-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYmkiQxbgPV34P1O0Qsq9%2Fuploads%2FMaHtdp3znOFlE3BDfVYQ%2Fimage.png?alt=media&amp;token=921ad6d6-51d5-4fd4-aae7-b2e783bc606f" alt="" width="375"><figcaption></figcaption></figure></div>

You can:

* ❌ Reject if it's not a duplicate (status = User No)
* ✅ Accept and go to the next that displays side by side all selected records.&#x20;

### Step 2: Review Master and Fields and merge

The selected pairs are shown alongside each other. The master record and the chosen fields are automatically configured based on the [duplicate merge rules](https://help.delpha.io/delpha-for-salesforce/use-cases-setup/duplicate/duplicate-merge.md).&#x20;

You can modify these default values on this screen.

By hitting the **Confirm and Merge** button, the status is set to User Yes and the merge is done instantly.&#x20;

<div align="left"><figure><img src="https://2667079222-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYmkiQxbgPV34P1O0Qsq9%2Fuploads%2Fjg49QXON9Nup1shJ92Jy%2Fimage.png?alt=media&amp;token=f9a493ad-d867-47c1-8b89-903b686b8944" alt="" width="375"><figcaption></figcaption></figure></div>

{% hint style="info" %}
You can configure which fields are visible and what rules apply in **Delpha Setup > Duplicate Settings**.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-duplicate/how-to-fix-duplicates-in-salesforce-with-delpha-automatic-bulk-and-manual-options.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
