> 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/whats-new/manage-duplicate-contacts-simplified.md).
# Manage Duplicate Contacts, Simplified
Review duplicate contact groups from the Duplicate Contacts modal.
When contacts share an email address, **Duplicate Contacts** opens a modal with each record's **Name**, **Email**, **Phone**, and **Address**. You can choose a Primary record and then:
* **Merge All**
* **Dismiss All**
* Merge groups one at a time
For Primary selection, retention limits, comparison limits, and merge safety, see [Managing Duplicates](/guides/crm/contacts/managing-your-contacts/managing-duplicates.md).
### Open the Duplicate Contacts screen
Click the **Duplicate Contacts** button located in the upper-right corner of the People screen, next to the search bar and select **Duplicate Contacts**.
### Review and choose an action
The modal shows all contacts that share an email. From here, you can choose to **Merge All**, **Dismiss All**, or go through them individually.
### Select the Primary contact
For each duplicate group, select the contact you want to use as **Primary**. Review the full records before merging.
---
# 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.rechat.com/whats-new/manage-duplicate-contacts-simplified.md?ask=&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.
