> For the complete documentation index, see [llms.txt](https://manuals.dialox.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manuals.dialox.ai/studio/flows/tags.md).

# Tags

To make items in the **Content** section conditional to a specific state we use [conditions](/studio/flows/conditions.md). Conditions can be based on the existence or non-existence of tags. 

Any flow node can be configured to set a tag when executed. 

Tags can also be set automatically by the system based on a context or system event.

### System tags 

This paragraph gives an overview of all the tags that are set by the system.

| Tag          | Explanation                                                                              |
| ------------ | ---------------------------------------------------------------------------------------- |
| online       | The conversation happens within [office hours](/settings/app-settings/opening-hours.md)  |
| offline      | The conversation happens outside [office hours](/settings/app-settings/opening-hours.md) |
| web\_capable | The conversation happens on a weblike channel (PWA, widget or studio)                    |

### User tags

The following tags are automatically set based on the basic user fields for **Name**, **Email**, **Phone** and **Language**.

<figure><img src="/files/AbqwSW71gl9HWm6CQhYe" alt=""><figcaption><p>Tags used to indicate the presence of reserved user fields</p></figcaption></figure>

{% hint style="info" %}
When you introduce new user fields, make sure to add a tag for them here too.
{% endhint %}

The **Remember** option in **Ask Choice**, **Ask Open**, etc will store the value in the user object as well as set a user tag using the **Assign to** property.

| Tag         | Explanation                                     |
| ----------- | ----------------------------------------------- |
| user:phone  | The phone number of the contact is known.       |
| user:name   | The name of the contact is known                |
| user:email  | The email of the contact is known               |
| user:mobile | The phone number of the user is a mobile number |

### Call status tags

For bots used on a phone channel the latest call status of the conversation will be annotated in the conversation using the following tags to be able to identify what happened to phone calls in the underlying phone system (pbx):

<figure><img src="/files/o22QuScCiYLTt7RVh0eF" alt=""><figcaption><p>Call status tags</p></figcaption></figure>

### Language tags

The following tags will be set to annotate the language the conversation is in at any given time. It will be set at conversation start, but also when using the flow nodes [ask: language](/studio/flows/nodes/ask-language.md) and [switch language](/studio/flows/nodes/control-flow-switch-language.md).&#x20;

For every supported language there is a tag available on your bot:

<figure><img src="/files/IlNGCBMew8XqKgGlEF16" alt=""><figcaption><p>Language tags</p></figcaption></figure>

{% hint style="info" %}
Note that, although a number of languages are supported in the platform, it will only allow the language to switch to the languages defined in your [Bot settings](/settings/app-settings/app-identity.md).
{% endhint %}

### Custom tags

To use tags in **Flows** or other parts of the system it is recommended to explicitly configure them under **Setting > Tags**. This way both the system as well as you and your colleagues can understand what tags are set. The system tags are also listed here.

<figure><img src="/files/8u8OeUwqLNJTEHSwaROh" alt=""><figcaption></figcaption></figure>


---

# 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://manuals.dialox.ai/studio/flows/tags.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.