> 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/appendix/brokerage-set-up/service-network/managing-duplicate-providers.md).
# Managing Duplicate Providers
Use Duplicate Cleanup to find and review potential duplicate providers that already exist within your Service Network.
Rechat scans providers across every Service Type in the account and groups records that may represent the same provider.
Duplicate Cleanup is designed for existing Service Network records. If you are uploading a new provider file, duplicate detection is built directly into the import process.
### Open Duplicate Cleanup
From the **Service Provider Management** dashboard, open **Duplicate Cleanup**.
Rechat scans providers across every Service Type within the account and displays the results.
### Understand the Duplicate Scan
At the top of Duplicate Cleanup, you'll see a summary of the scan.
#### Providers Scanned
The total number of provider records Rechat analyzed across the account.
#### Duplicate Groups
The number of groups containing provider records that Rechat identified as possible duplicates.
A duplicate group can contain multiple provider records.
#### Exact Matches
Groups where Rechat found matching identifying information between provider records.
#### Needs Review
Groups that require additional Admin review before determining whether the records are duplicates.
### Filter Duplicate Providers
Use the filters at the top of Duplicate Cleanup to view:
* **All** — all identified duplicate groups.
* **Exact** — groups identified as exact matches.
* **Needs Review** — groups requiring additional review.
You can also search the results using provider information such as company, person, or email.
### Understand Why Providers Were Matched
Each duplicate group displays the provider records Rechat believes may represent the same provider.
Rechat also identifies matching information when available. For example, records may be grouped because they have the **same phone number**.
Each group can display information such as:
* Company or provider name
* Contact name
* Email address
* Service Type
* Number of records in the group
* Matching information
* Recommended keeper
The **Recommended keeper** identifies the record Rechat recommends retaining when reviewing the duplicate group.
{% hint style="info" %}
**Important:** Review the provider information before resolving a duplicate. Providers can appear across different Service Types, and similar information does not always mean two records should be combined.
{% endhint %}
### Review a Duplicate Group
Click **Review** beside a duplicate group to inspect the matching provider records.
### Refresh Duplicate Results
Use the refresh option within Duplicate Cleanup to scan the current provider records again.
This can be useful after resolving duplicate groups or making changes to provider information.
### Duplicates Found During an Import
You do not need to run Duplicate Cleanup before every provider import.
When you upload an Excel or CSV file, Rechat performs duplicate detection as part of the import workflow and identifies:
* New providers
* Existing providers
* Potential duplicates
You can then choose to skip duplicates, update existing providers, or import all eligible records.
**Learn more:** [Importing Providers](/appendix/brokerage-set-up/service-network/importing-providers.md)
### Best Practices
Review duplicate groups carefully before making changes, especially when the same provider or company may legitimately appear under multiple Service Types.
Use Duplicate Cleanup periodically as your Service Network changes to help keep provider records organized and current.
For future bulk updates, use **Update Existing Providers** during import when appropriate rather than automatically creating another provider record.
### Related Resources
* \[Service Network]
* \[Importing Providers]
* \[Using Service Network]
---
# 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/appendix/brokerage-set-up/service-network/managing-duplicate-providers.md?ask=&goal=
```
`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.
