> 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/delpha-apps/delpha-setup/delpha-configuration/duplicates.md).

# Duplicates

## Delpha Duplicate Management

### Overview

Duplicate records in Salesforce fragment your customer view, distort reporting, and confuse AI agents. Delpha's Duplicate Management module allows you to automatically detect, group, and merge redundant records across your Account, Contact, and Lead objects.

As seen in the Delpha Setup menu, this feature is managed through two distinct configuration areas:

1. Detection Settings: Define *how* Delpha finds potential duplicates (the matching logic).
2. Merge Settings: Define *how* Delpha combines them (the rules for retaining data).

### [1. Detection Settings (Finding Duplicates)](/delpha-for-salesforce/use-cases-setup/duplicate/duplicate-detection.md)

Before you can clean your data, you must define what constitutes a "match."

* Logic: Delpha uses advanced AI matching that goes beyond exact text matches. It can identify duplicates despite typos, nicknames (e.g., "Bob" vs. "Robert"), or different formatting.
* Scope: You can configure detection rules for specific objects to control sensitivity and performance.

### [2. Merge Settings (Fixing Duplicates)](/delpha-for-salesforce/use-cases-setup/duplicate/duplicate-merge.md)

Once duplicates are found, Delpha needs instructions on how to consolidate them into a "Master Record."

* Master Record Selection: Rules to determine which record survives (e.g., *Oldest Created Date* vs. *Most Recently Updated vs. Custom Selection rules*).
* Field Retention: Rules to ensure valuable data (like mobile numbers or titles) is not lost during the merge.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.delpha.io/delpha-for-salesforce/delpha-apps/delpha-setup/delpha-configuration/duplicates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.