> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/settings/how-to-create-and-use-custom-fields.md).

# How to create and use custom fields

Learn how to create and manage custom contact fields on DoubleTick, including field types, visibility and role access, so you can store the customer data your business needs.

**Custom Contact Fields** let you store additional information about your customers beyond the default details DoubleTick captures, such as subscription plan, city, lead score, account ID, or any other data relevant to your business. Once created, these fields can be used across **customer profiles, segments, bots, broadcast templates, and reports**.

#### What's covered

* [How to access Custom Contact Fields](#how-to-access-custom-contact-fields)
* [How to create a new custom field](#how-to-create-a-new-custom-field)
* [How to manage custom fields](#how-to-manage-custom-fields)
* [Tips before you start](#tips-before-you-start)
* [Key takeaways](#key-takeaways)

#### How to access Custom Contact Fields

* Click **Settings** from the left navigation bar.
* Select **Custom Contact Fields** from the Settings menu.
* You will see a list of all existing custom fields along with their type, scope, and timestamps.

#### How to create a new custom field

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FxkFR3hcyCNqeqa410Up5%2Fgif1_create_field.gif?alt=media&amp;token=99d1406c-542b-4353-9e33-a69a430db675" alt=""><figcaption></figcaption></figure>

Click the **Create New Field** button in the top-right corner. A popup will open with the following fields.

**Field Name:**\
Enter a name for the field. This is how it will appear across customer profiles, segments, bots, and templates. Choose a clear, descriptive name, for example Subscription Plan, City, or Lead Score.

**Parent Field (Optional):** You can link a field to an existing field to create a hierarchical data structure. Click **Add Parent Field** to select a parent. This is optional and only needed for advanced setups.

**Defined Per (Scope):** This setting controls whether the field value is tied to the **customer as a whole** or a **specific channel**.

* **Customer:** The value is the same for this customer across all your connected WhatsApp numbers. Use this for global attributes like name, email, or date of birth.
* **Channel:** Each connected WhatsApp number can have a different value for the same customer. Use this for channel-specific data like lead status or iRate score.

**Field Type:** Choose the type of data this field will store. DoubleTick supports the following field types:

* **Text:** Free-form input for names, IDs, short descriptions, or any string value.
* **Date:** A date picker for storing dates such as subscription expiry or date of birth.
* **Number:** Stores numeric values like wallet balance, message count, or lead score.
* **List (Single Select):** A dropdown where only one value can be selected at a time. Selecting a new value overwrites the existing one. Use this when a customer can only belong to one category, for example subscription plan or industry.
* **Multi Select List:** A dropdown that allows multiple values to be selected at the same time. Use this when a customer can belong to more than one category, for example product interests or features used.

**Field Visibility:** This controls how the field appears in the **customer details panel** during a chat. Custom fields remain accessible in segments, bots, templates, and broadcasts regardless of this setting.

* **Always Visible:** The field is shown even when it has no value.
* **Only Visible if Field Value is Set:** The field is hidden until a value is entered. Recommended for keeping the chat panel clean.
* **Never Visible:** The field is hidden from the customer details panel but can still be accessed and updated via API or bots.

**Method to Update Values:** Choose how this field gets populated.

* **Static:** Values are entered manually by your team or updated via API.
* **AI Based Field Values:** DoubleTick's AI scans chat conversations and automatically populates the field value. This is a premium feature, useful for fields like lead intent, sentiment, or product interest.

#### How to manage custom fields

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2Fp5W12H9m4qvuYnUSabMT%2Fgif2_manage_edit_delete.gif?alt=media&amp;token=ae34ea13-c913-4385-8e51-cca17f4132ef" alt=""><figcaption></figcaption></figure>

On the Custom Contact Fields page, you can:

* **Search** for a specific field using the search bar.
* **Reorder** fields by dragging the handle on the left of each row.
* Click the **three-dot (⋮) menu** on the right of any field to access the following options.

**Edit:** Modify the field name, type, scope, visibility, or any other setting configured when the field was created.

**Manage Access:** Control which roles in your DoubleTick account can access this field. In the **Manage role access for custom fields** window, you can assign one of three access levels to each role, if your account has multiple roles defined:

* **Edit custom field:** The role can view and update the field value.
* **View only:** The role can see the field and its value but cannot make changes.
* **Hide (**<mark style="color:$primary;">**New**</mark>**):** The role cannot see the field or its values anywhere in DoubleTick. This includes chats and customer details, chat filters and sorting, template variables, customer segments and exports, CX Overview, Enterprise Analytics, AI agent settings, and lifecycles.

{% hint style="info" %}
Use **Hide** for sensitive data, such as lead score or account ID, that a team should not see at all.
{% endhint %}

**Good to know about Hide**

* **Parent fields:** Hiding a parent field also hides its child fields. Hiding a child field does not hide its parent.
* **Existing setups keep working:** Segments and AI agents that already use a hidden field keep using it. Users in that role see the field as a locked **Hidden by role** chip, which they cannot edit or remove. Lifecycles built on a hidden field are not shown to that role.
* **No lock-outs:** You cannot hide a field from your own role. Default roles (Owner, Team Lead, and Team Member) are never affected, so the Owner can always change it back.
* **Undo anytime:** Set the role back to **View only** or **Edit custom field**, and the field reappears for that role.

**Delete:** Remove a custom field that you no longer need.

#### Tips before you start

* Use **List** or **Multi Select List** field types instead of Text when the values come from a fixed set. This keeps your data consistent and makes segmentation more reliable.
* Use **Customer** scope for global attributes and **Channel** scope for data that may vary across your WhatsApp numbers.
* Set visibility to **Only Visible if Field Value is Set** to avoid cluttering the customer details panel with empty fields.
* Use **AI Based Field Values** for fields that can be automatically inferred from conversations, such as lead intent or sentiment.
* Use **View only** when a team needs to see a value but not change it. Use **Hide** when they should not see it at all.

#### Key takeaways

* **Custom Contact Fields** store extra customer information and work in profiles, segments, bots, templates, and reports.
* Match the **field type, scope, and visibility** to how you use the data.
* **Manage Access** has three levels for each role: **Edit custom field**, **View only**, and **Hide**.
* **Hide** removes the field and its values for that role everywhere in DoubleTick.
* You can undo **Hide** at any time. The **Owner** can always change access.

#### FAQs

<details>

<summary>What is the difference between View only and Hide?</summary>

With **View only**, the role can see the field and its value but cannot change it. With **Hide**, the role cannot see the field or its values at all.

</details>

<details>

<summary>What happens to segments and AI agents that already use a hidden field?</summary>

They keep working. Users in the role see the field as a locked **Hidden by role** chip, which they cannot edit or remove.

</details>

<details>

<summary>Can I hide a field from my own role?</summary>

No. You cannot hide a field from your own role. The default roles (**Owner**, **Team Lead**, and **Team Member**) are never affected, so the Owner can always change access back.

</details>

<details>

<summary>If I hide a parent field, are its child fields hidden too?</summary>

Yes. Hiding a parent field hides its child fields. Hiding a child field does not hide its parent.

</details>

<details>

<summary>How do I make a hidden field visible again?</summary>

Open **Manage Access** for the field and set the role back to **View only** or **Edit custom field**. The field reappears for that role.

</details>

#### Related articles

{% content-ref url="/spaces/53n17VnOICC1LtDqlENV/pages/mjRAF4BpKorMHg5F5JzQ" %}
[How to set permissions for custom organization role](https://learn.doubletick.io/settings/manage-roles/how-to-set-permissions-for-custom-organization-role.md)
{% endcontent-ref %}

{% content-ref url="/spaces/53n17VnOICC1LtDqlENV/pages/3uu5ndpZLxzO9Py3lJcY" %}
[How to use Custom Nested Fields for CRM-grade Data](https://learn.doubletick.io/settings/how-to-use-custom-nested-fields-for-crm-grade-data.md)
{% endcontent-ref %}

{% content-ref url="/spaces/53n17VnOICC1LtDqlENV/pages/dfKWnZgupjZcEZpjnF2U" %}
[How to Create and Use Multi-Select List in Custom Contact Fields](https://learn.doubletick.io/settings/how-to-create-and-use-multi-select-list-in-custom-contact-fields.md)
{% endcontent-ref %}

{% content-ref url="/spaces/53n17VnOICC1LtDqlENV/pages/zpZbZCWD5ggXBdHTrMoL" %}
[Create Customer Segments](https://learn.doubletick.io/customers/create-customer-segments.md)
{% endcontent-ref %}

{% content-ref url="/spaces/53n17VnOICC1LtDqlENV/pages/pJllWQhxztq0NGJJkuB2" %}
[How to create an AI custom field](https://learn.doubletick.io/doubletick-ai/ai-governance/understanding-ai-custom-field/how-to-create-an-ai-custom-field.md)
{% endcontent-ref %}


---

# 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://learn.doubletick.io/settings/how-to-create-and-use-custom-fields.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.
