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

# Customize tags

## Overview <a href="#yleista" id="yleista"></a>

Tags are an efficient way for agents to categorize conversations with customers. Tags help you keep track of conversations, you can find all the tags which have been used in the Queue statistics.

Your organization operators can create, edit, and delete tags.

## Customize tags

![](/files/-LNpShEO8u9w4diCVeZ8)

1. Click the tag bar to edit label or delete it.
2. Click the paint icon to change the color of the tag. Colors are a great way to differentiate between categories of tags.
3. Add a new tag as a subcategory under an existing category.
4. Create a new tag category.


---

# 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://support.ninchat.com/ninchat-support/english/organization/customize-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.
