> 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/getting-started/train-your-bot/train-for-intent-recognition.md).

# Train for Intent recognition

In the previous section, you have created a new Project and configured the basic configuration for your bot. In this section, we will continue configuring our Bot, especially the Intents.

![](/files/TDJof0j0eUdo3rr5w8r7)

### 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. You can read more on [Intents and Automation](/platform-reference/intents-and-automation.md) in our documentation.

{% hint style="info" %}
Intents are used to define what you want a bot to respond with when it picks up the intention of a user, or when you want to trigger a response based on some other event.  In other words, it describes the intention and the expected interaction user would want from the chatbot.
{% endhint %}

We will go ahead and create our first intent *applyLeave*, which would describe the intent of the user to apply for leave. Each intent is characterized by a few features.

* **Intent Name** : *Unique identifier for the intent.*
* **Description** : *Description for the intent.*
* I**s Top Level** : *Specifies if the intent is a top-level intent or not.*
* **Action** : *Comprises of Slots, Triggers and Stop Triggers.*

![Intents & Automations](/files/ojr3tekFK5nIYUGU1vRj)

As seen in the image, we have set the *Intent Name* as *applyLeave*. Henceforth, we would be referring to this intent when we specify *applyLeave*. We will now proceed to describe the *Action* parameters associated with the intent.

{% content-ref url="/pages/bHG42NUkr6N5rJ7FpEi0" %}
[Define the Slots](/getting-started/train-your-bot/train-for-intent-recognition/define-the-slots.md)
{% endcontent-ref %}

{% content-ref url="/pages/iOUD4MbklHRdDhbigQlY" %}
[Train the Triggers](/getting-started/train-your-bot/train-for-intent-recognition/train-the-triggers.md)
{% endcontent-ref %}

{% content-ref url="/pages/jVhd5UzehEBrnFEzkwxi" %}
[Train for Stop-Triggers](/getting-started/train-your-bot/train-for-intent-recognition/train-for-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/getting-started/train-your-bot/train-for-intent-recognition.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.