> 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/delpha-duplicate/how-can-i-hide-a-field-from-the-delpha-bot-conversation.md).

# How can I hide a field from the Delpha Bot conversation?

## How to Hide Fields in Delpha Bot During Duplicate Merges

When using the **Duplicate conversation in the Delpha Bot**, you might want to **hide technical or sensitive fields** from the end user to streamline the merge process and improve clarity.

This is especially useful for internal identifiers (e.g., external system IDs) that shouldn't be part of user-facing decision-making.

## Use Case Example: Hiding a Technical ID Field

If you have a custom field like `External_System_ID__c`, you likely don’t want it visible to users during the merge conversation.

Delpha makes it easy to hide this field from the bot UI while still applying a merge rule.

## How to Hide a Field in the Duplicate Conversation

### Step 1: Navigate to Merge Field Rules

1. Open the **Delpha Setup** app
2. Go to the **Duplicate Settings** tab
3. Select the **target object** (e.g., Contact, Lead, Account)
4. Scroll down to the **Merge Field Rules** section
5. Click **New Rule**

### Step 2: Configure the Field Rule

| Field             | Description                                                                            |
| ----------------- | -------------------------------------------------------------------------------------- |
| **Action**        | Choose `Customize` (used for single field customization)                               |
| **Visible**       | Set to `Off` to **hide the field** from the Delpha Bot interface                       |
| **Override Rule** | Choose the rule to determine how the field is populated (e.g., `Master and Not Empty`) |
| **Custom Value**  | Optionally set a **default value** that will overwrite the field after the merge       |

{% hint style="info" %}
When the Override Rule is set to Empty, the value will be reset after merge.
{% endhint %}

### Result

Once saved:

* The field is **not shown** to users in the Delpha Bot conversation
* Your **merge rule still applies** as configured
* The process becomes more **user-friendly and secure**


---

# 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/delpha-duplicate/how-can-i-hide-a-field-from-the-delpha-bot-conversation.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.