> For the complete documentation index, see [llms.txt](https://readme.dhee.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://readme.dhee.ai/platform-reference/entities-and-other-data/entities/custom-entity-types.md).

# Custom Entity Types

Dhee.AI comes equipped with built-in support for various data types, offering versatility and precision in handling user input. These data types include:

* INTEGER
* DATE
* TIME
* NAME
* ARTEFACT
* LOCATION
* BOOLEAN
* CODE
* PAST\_DATE
* FUTURE\_DATE
* ADDRESS
* RELATIONSHIP
* PASS\_THROUGH
* PHONE\_NUMBER
* EMAIL\_ID
* NUM\_PLATE
* EVENTS
* SYSTEM FILLED
* QUERY\_PHRASE

Additionally, Dhee.AI grants users the flexibility to define their own Custom Entity Types to align with specific intents and requirements. These Custom Entity Types can be established within the Entities & Other Data section, under Custom Entity Types.

![Custom Entity Type](/files/r9bY8QP7JV54aADR6OE9)

Each Custom Entity Type is characterised by a unique type name and the option to provide a description, clarifying the entity's purpose and significance in the chatbot's interactions.

This feature empowers users to create a highly tailored chatbot experience that accurately interprets and responds to user input.


---

# 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://readme.dhee.ai/platform-reference/entities-and-other-data/entities/custom-entity-types.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.