> For the complete documentation index, see [llms.txt](https://studio.docs.ai.vonage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio.docs.ai.vonage.com/properties-1/intents/intent-annotation.md).

# Intent Annotation

If you want to **extract or utilize a specific part of the caller’s input** you can do so by identifying a word or select part of the sentence. 

Once you highlight a part of the utterance, you will be prompted to select a parameter you want to attribute it to. You can either select a parameter you have already added from the dropdown (@entity:PARAMETER) or create a new parameter on the spot. 

### How to use intent annotation

Example use case: Call Routing

You can use Intent annotation for example for an intent that is supposed to route the call. You might have added utterances such as “I would like to speak to John” or “I need to have a chat with Betty”. 

Then you would go into the utterances and mark "John" and "Betty" as the parts of the contacts entity. When a caller would utter a phrase like this, the agent will know who to route the call to

{% hint style="warning" %}
*Keep in mind that you will need at least 3 expressions and 3 annotations for intent annotation to work.*
{% endhint %}

![](/files/7t188V1eEkXrzB0Fw3hT)


---

# 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://studio.docs.ai.vonage.com/properties-1/intents/intent-annotation.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.