> 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/use-cases-setup.md).

# Use Cases Setup

Use Delpha’s Use Cases Setup to configure data quality and duplicate detection rules in Salesforce. Tailor each use case to meet your business needs and maintain clean, reliable CRM data.

## Use Cases Setup Menu in Delpha

The **Use Cases Setup** menu allows administrators to configure key operational workflows in Delpha:

* **Duplicate** – [Set up rules and automation to detect and manage duplicate records across Salesforce objects.](https://help.delpha.io/delpha-for-salesforce/use-cases-setup/duplicate.md)
* **Data Quality** – [Define and customize how Delpha evaluates field-level data quality based on business needs](https://help.delpha.io/delpha-for-salesforce/use-cases-setup/data-quality.md).

These options ensure your Salesforce org is equipped to handle both duplicate management and ongoing data health monitoring.


---

# 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.delpha.io/delpha-for-salesforce/use-cases-setup.md?ask=<question>&goal=<user_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.
