> 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/intents-and-automation/intents.md).

# Intents

Intents define the goals the Customer wants to achieve when he/she interacts with our bot.

The intent definition should include the triggers which help in identifying the intent during the conversation with the Customer. Once an intent is identified by the chatbot, the intent definition should be complete with the information (entities) it needs to have for completing the action.

## Create User Intent

You can create a new User Intent using the *IntentsAndAutomation->Intents* menu.

![Create User Intent](/files/WjJeN34e1lLg2DQAuoHO)

The above list shows all the configured intents for your current project. You can create a new *User Intent* using the *+* (Plus) button. Each User Intent requires

* **Name** : Unique name to identify the intent
* **Description** : Description for the intent
* **Is Top Level** : Specifies if the intent is a top-level intent.

## Edit User Intent

The developer can *edit* an existing User Intent meta-information using the *pen* icon in each row.

![Edit User Intent](/files/OwKB4ybNTFIkhM8yIbu1)

Use the *Save* to save the active changes.

## Delete User Intent

The *Intents Management Screen* also provides the developer with deleting existing User Intents. The developer can use the *Delete* button corresponding to the Intent to delete it.

![Delete User Intent ](/files/MD5mIUzUFAeAcvYwETqt)

On attempting to delete, the Developer would be prompted for a confirmation to avoid accidental deletion.

## Delete All

Additionally, the User has an option to delete all intents together. This is useful when Developer needs to delete multiple intents. The *Delete All* button on the top right of the *Intent List* allows the developer to delete all intents. As with the individual deletion of intents, the developer would be prompted for confirmation of his actions.

![Delete All User Intents](/files/cHVDqiIpCnfhwpsRlQCL)

## Additional Reading

{% content-ref url="/pages/HiEOHZIBwvmozuuAhJP5" %}
[Slots](/platform-reference/intents-and-automation/intents/slots.md)
{% endcontent-ref %}

{% content-ref url="/pages/On3qzIwKawwb40rP3Dob" %}
[Triggers](/platform-reference/intents-and-automation/intents/triggers.md)
{% endcontent-ref %}

{% content-ref url="/pages/KNUyjTMjReDhOC80pVIc" %}
[Stop Triggers](/platform-reference/intents-and-automation/intents/stop-triggers.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 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/intents-and-automation/intents.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.