> 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.md).

# Duplicate Cases - Email to Case

- [How Delpha Handles Email-to-Case Duplicates](https://help.delpha.io/delpha-for-salesforce/how-to-faq/duplicate-cases-email-to-case/how-delpha-handles-email-to-case-duplicates.md): Delpha auto-detects and processes duplicate Email-to-Case records—only “Possible Duplicates” need your review.
- [What is the outcome of the Duplicate EmailToCase analysis](https://help.delpha.io/delpha-for-salesforce/how-to-faq/duplicate-cases-email-to-case/what-is-the-outcome-of-the-duplicate-emailtocase-analysis.md): Email-to-Case Duplicate Object stores comparisons between a new case and a matched case, including IDs, numbers, status, subjects, similarity score, and Email body text differences.
- [As a Data Steward, how to process duplicate cases](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 an End User, how to process duplicate cases](https://help.delpha.io/delpha-for-salesforce/how-to-faq/duplicate-cases-email-to-case/as-an-end-user-how-to-process-duplicate-cases.md)
- [What happens when I process a duplicate cases pair?](https://help.delpha.io/delpha-for-salesforce/how-to-faq/duplicate-cases-email-to-case/what-happens-when-i-process-a-duplicate-cases-pair.md): Based on your settings, the cases are processed, merged or re-parented. Some extra information is added so you can keep track of the changes and extra operation performed on the attachments.
- [As an End User, I do not see the bot](https://help.delpha.io/delpha-for-salesforce/how-to-faq/duplicate-cases-email-to-case/as-an-end-user-i-do-not-see-the-bot.md)


---

# 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.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.