> 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/how-to-faq/duplicate-cases-email-to-case/as-a-data-steward-how-to-process-duplicate-cases.md).

# As a Data Steward, how to process duplicate cases

[Duplicate case information is stored in the **DDQ Duplicate Cases** object](/delpha-for-salesforce/how-to-faq/duplicate-cases-email-to-case/what-is-the-outcome-of-the-duplicate-emailtocase-analysis.md), accessible directly from the Delpha Data Quality app.\
Within this tab, you can filter, sort, and review duplicate pairs.\
If you confirm that a pair is a valid duplicate to be processed, simply change its Status from **Potential Duplicate** to **Auto Yes**—the duplicate will then be processed immediately.

If you want to work from the **Service Console** app, just open the DDQ Duplicate Cases tab in the application.

{% hint style="warning" %}
To apply a decision in bulk, select the potential duplicates, update the Status field for one pair, and make sure to check the **Apply on all records** option so the change is applied to all selected cases.
{% 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.delpha.io/delpha-for-salesforce/how-to-faq/duplicate-cases-email-to-case/as-a-data-steward-how-to-process-duplicate-cases.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.