> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/guides/crm/contacts/managing-your-contacts/managing-duplicates.md).

# Managing Duplicates

Managing duplicate contacts is easy with Rechat. When two contacts share the same **email address**, Rechat will automatically recognize the duplicate, ensuring you don’t have multiple profiles for the same person. This helps keep your contact list clean and organized, making it easier to manage communication and follow-ups.

## Merging Duplicates

1. When Rechat detects duplicate contacts, an avatar will appear in the upper right corner.
2. Merge the contacts;
   1. **Single Contact:** Select which contact record(s) you'd like to merge contact-by-contact.
   2. **Bulk:** Merge all detected contacts with one click.

### Merging a Single Contact

<figure><img src="/files/lpyNgpJlbEW9HymWSEPV" alt=""><figcaption></figcaption></figure>

### Bulk Merging

<figure><img src="/files/HFUorqiX8cHlQHNF4Ynn" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Tip:** The contact you select first will be the photo and name you see in the main dashboard.&#x20;
{% 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 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.rechat.com/guides/crm/contacts/managing-your-contacts/managing-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.