> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/hablla/settings/tags.md).

# Tags

Tags are used to classify and organize support cases, making it easier to identify topics, segment conversations, create filters, and generate reports.

### ✅ How to create a label

1. Go to the menu **Settings**.
2. Click on **Labels**.
3. Select the option **New label**.
4. Fill in the label information:
   * **Name:** Enter the name that will identify the label.
   * **Color:** Choose a color to make it easier to identify (optional, if available).
5. Click on **Save**.

Done! The label will be available for use in chats and other features that use labels.

### ✏️ How to edit a label

1. Access **Settings > Labels**.
2. Find the desired label.
3. Click on the label.
4. Make the necessary changes.
5. Click on **Save**.

### 🗑️ How to delete a label

1. Access **Settings > Labels**.
2. Find the label you want to remove.
3. Click the trash icon.

### 📌 How to add a label to a chat

1. Open the desired chat.
2. Find the chat information icon.
3. Click on **Add label**.
4. Select the desired label.
5. The label will be linked to the chat immediately.

> **Attention:** If the label is being used in chats, flows, or other settings, deleting it may affect those records.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hablla.com/hablla-docs-en/hablla/settings/tags.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
