Discord Ticket Priority: Who Sets It, and Which Level Wins

Priority is usually a label somebody has to remember to set. In practice nobody does, every ticket sits at the same level, and the label stops meaning anything. A priority is only useful if something sets it before a person has read the ticket, and if the rules between whoever sets it are clear enough that you can trust the level you see.

This guide covers those rules on AI Ticket Bot, including Urgent and the level each category starts its tickets at. What belongs in each level is a separate question, answered in the escalation guide. This one is about who decides, and what the decision does once it is made. It is a fair question to ask of any Discord ticket bot: when two things disagree about how urgent a ticket is, which one wins?

What does a ticket's priority actually do?

Short answer: it decides the order your team sees tickets in, and nothing else. A priority does not ping anyone, does not change when reminders go out, and does not move the channel. It is a sort order, and that is the right thing for it to be: an alarm tied to a label will eventually go off on a wrong one.

There are four levels. Low is for things nobody is waiting on, Normal for most requests, High for someone blocked or something of value at risk, and Urgent for harm happening right now, like a raid or a scam in progress.

The overview's Priority list is the one worth leaving open. The ticket at the top is the most urgent one that has waited longest, which is the question a person starting a shift actually has.

Who can set a ticket's priority?

Four things write it, and the rules between them are what make the level worth reading.

The short version: a person has the final say, the AI only ever pushes up from what a person decided, and a move never lowers anything.

Every change writes a row in your audit log with the old level, the new one, and what set it: a staff member, the AI when it handed over, or a move. Opening at the category's level is not a change and writes nothing.

How do you give a category a starting level?

This setting does the most work, and the reason is easy to miss. The AI only sets a priority when it hands a ticket over. In a category where you have switched the AI off, such as billing or reports going straight to people, it never hands anything over. The category's starting level is the only priority those tickets get until somebody reads them. Leave it at Normal and a scam report waits in line behind a question about roles.

In Discord, the same setting is Default priority on the category's card in /panel. It is free on every plan and needs no republish, because members never see the level on your panel. In the editor, any category that does not start at Normal carries a small chip such as Starts High, so you can tell at a glance which ones you changed.

Three things to know before you set one:

• It only applies going forward. Tickets already open keep the level they have.
• Web chats and tickets from a connected bot always open at Normal, because they have no category of ours.
• Choose High and Urgent with care. For the AI, a raised starting level is a minimum rather than a suggestion, as the next section explains.

How ticket categories work covers the rest of what a category controls.

How does the AI choose a level when it hands over?

By what waiting would cost, not by the topic, and not by how upset the member sounds. A member typing "this is urgent" does not make a ticket Urgent. A calm message saying their account is being taken over right now is exactly what Urgent is for. The AI is given no default level either, so Normal is a judgement like the others rather than a place to land when unsure.

Your rules come first. If your server treats every chargeback as Urgent, or every partnership request as Low, teach it that with /ai train like any other fact, and it follows your rule over its own. How the AI's memory works covers what it can and cannot hold.

Our side then applies two limits to the level it picked, before anything is written:

The first row is deliberate. If Normal were a minimum, the AI could never mark a suggestion as Low on the many servers that never touch the setting, and Low would go unused.

The third row is what lets you triage without stepping in. /ticket priority posts nothing in the ticket, so the AI keeps answering. Mark a ticket High while the AI is still working on it, and when it hands over later, it cannot pull the level back down.

What happens when someone changes it by hand?

Exactly what they chose. Neither of the AI's limits applies to a person. A ticket in a category that starts at High can be set to Low by someone who has read it and knows it can wait, and that is the point of a person having the final say.

There are two places to do it:

• In Discord, run /ticket priority inside the ticket. It needs a staff role with the Work on tickets permission, or Manage Server.
• On the dashboard, use the priority control on the ticket's own page, which needs Manage Server.

Both are free on every plan. Neither works on a closed ticket, whose record stays exactly as it was when it closed.

The change is quiet on purpose. The confirmation is shown only to the person who made it, nothing is posted in the ticket, and nobody is pinged.

A move works in one direction only. /ticket transfer, which needs the Move tickets permission, raises the ticket to the new category's starting level when that is higher and leaves it alone when it is lower. Only the person who moved it is told about the raise. The notice in the ticket says it moved, and nothing about priority.

What does the member see?

Almost nothing, and that is a choice. "Your ticket was marked Low" is an argument nobody needs to have with a member, so their list of tickets never shows a priority, and none of the changes above are announced to them.

The one exception is the AI's handoff. When it hands a ticket to your staff, the message it posts in the ticket names the level, and in a channel ticket the channel topic repeats it. Members can read both. Both record the moment of handoff and are not rewritten afterwards, so if the AI handed over at High and someone lowers the ticket a minute later, the message still says High. The current level always lives in the ticket list and in /ticket search, which the guide to ticket search walks through.

Where priority is the wrong tool

Read this before you build a process on it.

• Urgent does not ping harder. An AI handover pings the one staff role you wired for that category or panel, at every level, and setting Urgent by hand pings nobody. If something needs a person within minutes, that is a role and a ping, not a label.
• It does not change reminder timing. On paid plans, smart inactivity reminds staff based on how fast your team usually replies, and an Urgent ticket gets the same timing as a Low one.
• There is no deadline per level. Nothing says "Urgent within fifteen minutes". Response time promises covers why a number you might miss is worse than none.
• Setting it back erases the signal. The bot knows a person chose a level only because it differs from the category's starting level. Set a ticket back to exactly that level and the AI treats it as untouched, free to move it again. The audit log still has the whole story.
• It is not routing. Priority never moves a ticket to another channel, category or team. The category a member picks does that.