> For the complete documentation index, see [llms.txt](https://docs.inogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inogic.com/deduped/features/duplicate-exclusion.md).
# Duplicate Exclusion
The Duplicate Record Exclusion feature allows users to whitelist specific duplicate records to prevent them from being captured in future detections. With authorized user roles, selected duplicates can be excluded via an **"Exclude"** button, which creates a backend exclusion record, ensuring the chosen records are removed from duplicate results in future detections.
Suppose you are detecting duplicates in Dynamics 365 CRM for contact entity based on first name and last name fields, and in the duplicate detection result, you find certain records that are not duplicates as they have different email domains.
In order to exclude records from duplicate detection, follow the steps given below:
* Once you find a record that you want to exclude from your future duplicate checks.
* Select the record and click on **“Exclude”** button.
* Click on **“Continue”.**
* Now the selected record will be excluded from your future duplicate checks.
---
# 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://docs.inogic.com/deduped/features/duplicate-exclusion.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.