# Tags

**Tags** are a tool for users to define important milestones in the conversation. 

It enables you to query for important insights (e.g. what are my most common call topics, how many calls were routed to a live agent, how many calls ended successfully, how many times the agent didn't understand the caller, etc.).

A Tag can be placed on any node on the graph. Each time a conversation reaches a tagged node, the attached tag will be collected (see below "tags collection").

![](/files/-Mb64KGyzKo9gOrDWNu6)

### Tags Definition <a href="#tags-tagsdefinition" id="tags-tagsdefinition"></a>

A tag is a property on the agent level, each tag will have a **Tag** **name** and will be associated with a **Category**. The category will assist in reporting.

### How and where to place a tag

On each node, there is an option to attach one or more tags (category + tag name). Once you open a node, you will notice three dots on the top right next to the save button.&#x20;

If you click on the dots, it will show you the option to add a tag. You can also remove or edit an existing tag from a node.

![](/files/Nsh0XMUOSuZUBKYhJ12O)

### Examples <a href="#tags-examples" id="tags-examples"></a>

| **Category**       | **Tags**                                                                         | **How to use it**                                                                                                        | **Insight**                                                                                                                              |
| ------------------ | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
| **Fallback**       | <ul><li>Misclassification</li><li>Missed Parameter</li></ul>                     | Misclassification: Place either on the Collect input "Missed" or the Classification "Default"                            | **Agent failed** to understand the caller                                                                                                |
| **Performance**    | <ul><li>Success</li><li>Fail</li></ul>                                           | <p>Place right before the End Call node / </p><p>Any other node that indicates success (e.g. route/SMS or any other)</p> | Shows calls that were **successful or failed**                                                                                           |
| **Action**         | <ul><li>Send Email</li><li>Send SMS</li><li>Route call</li><li>Webhook</li></ul> | Place on the relevant action node                                                                                        | Shows calls that **included an action (e.g. Calls/Emails/SMS/Webhook)**                                                                  |
| **Flow**           | Label the tag based on its content                                               | Place on the Conditions node                                                                                             | Indicates that a conversation went through a **specific flow**                                                                           |
| **Classification** | Label the tag based on the topic of the intent                                   | Place on the Classification node from one of the intents outputs                                                         | <p>Shows that a session included a <strong>specific intent</strong> </p><p>Can indicate the most <strong>common call topics</strong></p> |

### Tags Collection <a href="#tags-tagscollection" id="tags-tagscollection"></a>

Tags will be collected per session in real-time. Each time a conversation reaches a node, the attached tag will be collected.

If the same Node was reached twice, the tag will be collected twice - and so on.

![](/files/f7yPP9JLSUN9oOjvjaBi)


---

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