> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/help-desk/settings/ticket-category.md).
# Ticket Category
When you've created ticket categories, your home screen will look similar to this view.
## 1 - Creating a Single Category
To get started, click the + button at the top right of the screen. Select Create and a single create prompt will pop up.
Fill in the Name and Ticket Type to create your category. To help decipher this ticket, you can add an icon and a description or notes as well. Click create and the category will automatically be added.
## 2 - Creating Bulk Categories
To create bulk categories, click the + button and select Bulk Categories. The bulk upload will load. Click the +Add Row to add as many categories as you'd like.
Enter the Name and Ticket Type for each category you'd like to add. Adding an Icon and Description or Note will help your team decipher even more between categories.
Once you click save, the system will load the files and create the categories. You will receive an email when the upload is completed.
---
# 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.adminremix.com/help-desk/settings/ticket-category.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.
