> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/crm-v1-old/custom-fields/how-to-create-super-fields-in-crm.md).

# How to Create Super Fields In CRM ?

Go to CRM V2, click on "Add super Fields" and enter the field label, such as "City," then select the data type from various options including text, email, URL, phone number, numeric, amount, decimal, address, date, date and time, periodic time,etc.

For a dropdown super field, predefined options can be added, such as "Delhi," "Mumbai," "Dubai," and "Singapore," and a default value can be defined.

Additional settings for a super field include making it a required field, displaying it on the contact page, as a label in the chat inbox, and in the sidebar in the chat inbox.

After configuring the super field, click "Save field" to apply the changes.

The benefit of super fields over earlier custom fields in CRM is that they offer predefined fields to manage data more effectively, such as a "gender" field with fixed dropdown options for "male" and "female."

Super fields allow for more systematic and organized data management, filtering, and utilization.

{% embed url="<https://youtu.be/MfuzNUQP9y0?si=D1ecJEgQUWjrJ8hC>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/crm-v1-old/custom-fields/how-to-create-super-fields-in-crm.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.