> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/bot-commands/priority.md).

# /priority

## Priority Command

### Overview

The `/priority` command marks how urgent a ticket is. It sets one of four levels and puts a colored marker at the front of the channel name, so a busy ticket category can be read at a glance. Run it inside the ticket.

This is free on every plan.

### Usage

```
/priority <priority>
```

* **priority** *(required choice)*: **Low**, **Medium**, **High**, or **Urgent**.

### What each level looks like

| Level  | Marker | Channel name becomes |
| ------ | ------ | -------------------- |
| Low    | 🟢     | `🟢┇ticket-42`       |
| Medium | 🟡     | `🟡┇ticket-42`       |
| High   | 🟠     | `🟠┇ticket-42`       |
| Urgent | 🔴     | `🔴┇ticket-42`       |

Discord sorts channels alphabetically within a category, so the markers also group tickets of the same priority together.

### Limits and constraints

These are worth knowing before you build a workflow around it:

* **It shares the rename budget.** A ticket can be renamed **twice every 10 minutes**, and `/priority` spends one of those, because it renames the channel. Two priority changes in a row lock out `/rename` until the window resets. The bot tells you when you can change it again.
* **It does not work on very old tickets.** Tickets opened long before priority levels shipped reject the command and tell you so. Open a new ticket to use it.
* **Setting the same level again does nothing.** The bot says the ticket is already at that priority.
* **`/rename` keeps the marker.** Renaming a prioritised ticket puts the same colored marker in front of the new name, so the priority stays visible.
* **Ticket History cannot filter by priority.** Priority is stored on the ticket and visible in the channel name, but the Ticket History page has no priority filter, and Statistics does not break tickets down by priority. Today it is a signal for staff in Discord, not a reporting dimension.

### When to Use It

* Triage: mark the tickets that need attention first, so whoever picks up next takes the right one.
* Escalation: raise a ticket to Urgent when it turns out to be an outage or a payment problem.
* Winding down: drop a ticket to Low when it is waiting on someone else and does not need watching.

### Permissions

* You can use this command if you have Manage Channels or Manage Server, or you are the server owner, or you hold an authorized support role. Administrator also works because it includes those permissions.
* The bot needs `Manage Channels` to rename the channel.

### Example

```
/priority priority: Urgent
```

Renames the ticket to `🔴┇ticket-42` and records the level on the ticket.

### Related

{% content-ref url="/pages/ujxnvUAUCZLiZeX60SNs" %}
[/rename](/docs/bot-commands/rename.md)
{% endcontent-ref %}

{% content-ref url="/pages/0PyHViOuXmoK0zVX0Ukd" %}
[The ticket lifecycle](/docs/tickets/lifecycle.md)
{% endcontent-ref %}


---

# 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://ticketking.xyz/docs/bot-commands/priority.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.