# Train the Triggers

In the previous section, we configured the different inputs/outputs that are associated with the intent. The next step is to define *triggers* which would help the *agent* to identify the intent to use from the User utterances.

To add triggers, select the *Trigger* button under the *Action*.

![Select Trigger](/files/ojr3tekFK5nIYUGU1vRj)

Triggers allow you to define a collection of sentences or phrases which would be considered as a trigger for the intent. These could be explicit statements that help identify the intents or could be indirect references. For example, for the *applyLeave* intent, the user can interact with the chatbot in any of the following ways.

```
i need a leave
i am sick
I am planning some time off
```

You can also select to *auto translate* the texts to support a multilingual chatbot.

![Triggers for applyLeave](/files/ZJcjxzeAwBlr4jmMNgN0)

Each of the above states different ways a user might interact with the chatbot about the need for taking a day off. If the chatbot detects any of these, it would recognize the intent that needs to be considered as *applyLeave*.

![Chatbot recognizes the intent using trigger](/files/FeKFC94UegnzH89eHVFh)


---

# Agent Instructions: 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:

```
GET https://readme.dhee.ai/getting-started/train-your-bot/train-for-intent-recognition/train-the-triggers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
