> For the complete documentation index, see [llms.txt](https://docs.imber.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imber.dev/imber-bot/feature-guides/ticket-system.md).

# Ticket System

## How to setup the ticket-system

* Run the command "/tpanel setup \[name] \[emoji] \[colour] \[role]"

<details>

<summary>Command Usage</summary>

**\[name] -** *The name of the ticket category button*

**\[emoji] -** *The emoji of the ticket category button*

**\[colour] -** *The colour of the ticket category button*

**\[role] -** *The first role that can access the tickets in this ticket category*

</details>

<div align="left"><figure><img src="/files/DV2ZuZ36FmG49YkHFBTx" alt="" width="313"><figcaption><p><strong>THIS IS THE EMBEDBUILDER</strong></p></figcaption></figure></div>

<div align="left"><figure><img src="/files/ZjBj3BGaJNUpkg94r5on" alt="" width="283"><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="/files/OCcKsOosuXvIwb0A610i" alt="" width="302"><figcaption><p><strong>THE FINISHED EMBED</strong></p></figcaption></figure></div>

## How to edit the ticketpanel

* Run the command "/tpanel edit"

<div align="left"><figure><img src="/files/7wp5syfRObEdOEvMebz6" alt="" width="425"><figcaption></figcaption></figure></div>

## How to add/remove categories

* Run the command "/tpanel add-category \[name] \[emoji] \[colour] \[role]"
* Run the command "/tpanel remove-category \[name] \[edit]"

<details>

<summary>Command Usage</summary>

**ADD CATEGORY:**

**\[name] -** *The name of the ticket category button*

**\[emoji] -** *The emoji of the ticket category button*

**\[colour] -** *The colour of the ticket category button*

**\[role] -** *The first role that can access the tickets in this ticket category*

**REMOVE CATEGORY:**

**\[name] -** *The name of the ticket category*

**\[edit] -** *Whether to edit the ticket panel embed or not*

</details>

<div align="left"><figure><img src="/files/4uK8CcYU3gNwWl7kfC9z" alt="" width="296"><figcaption></figcaption></figure></div>

## How to add/remove a supporter role to a category

* Run the command "/tpanel add-role \[name] \[role]"
* Run the command "/tpanel remove-role \[name] \[role]"

<details>

<summary>Command Usage</summary>

**ADD A SUPPORTER ROLE:**

**\[name] -** *The name of the ticket category*

**\[role] -** *The role to add to the ticket category*

**REMOVE A SUPPORTER ROLE:**

**\[name] -** *The name of the ticket category*

**\[role] -** *The role to remove from the ticket category*

</details>

<div align="left"><figure><img src="/files/IdrPvcXtL0i9PuItHExL" alt="" width="467"><figcaption><p><strong>HERE WE ADD THE ROLE @EVERYONE TO THE TICKET</strong></p></figcaption></figure></div>

## How to remove the ticket system

* Run the command "/tpanel reset"

{% hint style="warning" %}
This will reset the ticket system.

All categories and the ticket panel embed will deleted.
{% endhint %}

{% hint style="info" %}
Have a suggestion or feature request? We'd love to hear from you! If there's something missing or an idea you'd like to share, head over to our suggestions section in our Discord and let us know. Your feedback helps us improve and tailor Imber Bot to meet your needs better.
{% endhint %}


---

# 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://docs.imber.dev/imber-bot/feature-guides/ticket-system.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.