> For the complete documentation index, see [llms.txt](https://documentation.movatic.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.movatic.co/admin-site/customer-support/tickets-tags.md).
# Tickets Tags
Here, you can define the tags that will be used to categorize support tickets within the system.
When you click on 'Support Tickets' and navigate to the 'Tags' tab, you'll gain access to the list of available tags. You can search by name and creation date, as well as filter by these columns to find specific tags efficiently.
To initiate the creation of new tags, navigate to the top-right corner and locate the **Add** button. Clicking on this button will prompt a popup where you can input the necessary name for the tag. After filling out the name, proceed to click the **Save** button
To archive a tag, navigate to the desired tag and click on the **Archive** button. This action will mark the tag as archived, removing it from active use while preserving its associated data for reference.
This action will trigger a confirmation popup, prompting you to confirm before archiving the tag. Once confirmed, the tag will be archived, ensuring that you're intentional about your actions and preventing accidental changes to your tagging system.
---
# 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://documentation.movatic.co/admin-site/customer-support/tickets-tags.md?ask=&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.
