Discord ticket categories for a game server: a setup that works
By Termi3 min read
A ticket panel with one "Open ticket" button sends everything to the same queue: a bug, a refund, an appeal against the admin reading it. Splitting tickets into a few categories lets the right people see the right tickets and lets each one start with the questions it needs. Here is a setup that works for most FiveM and Minecraft communities.
The seven categories
| Category | Who sees it | The opening form asks |
|---|---|---|
| General support | All support staff | What you need help with |
| Bug report | Support staff, developers | What happened, where, a clip |
| Player report | Moderators and admins | Who, when, what, a clip |
| Ban appeal | Senior admins only | What happened and why it should be lifted |
| Payments | Owner and a trusted admin | Transaction ID and package |
| Staff matters | Owner and head admin | Which staff member and what happened |
| Partnerships | Owner | Who you are and what you propose |
What each one should ask
Discord forms hold five questions, which is enough if you ask only what the record cannot tell you.
General support
One question: what do you need help with? This is where AI answers do most of their work, because the same questions about joining, rules and jobs come in every day.
Bug report
What happened, what you expected, where in the map, and a clip if you have one. Add the steps to reproduce if your developers want them.
Player report
Who, when, what happened and a clip. If you run FiveBot's report command instead, the card already carries both players, their characters and the distance between them. In-game reports.
Ban appeal
Your in-game name, when you were banned, what happened, why it should be lifted, and evidence. Keep the admin who gave the ban out of the category's staff roles. Running ban appeals.
Payments
The transaction ID and the package name. With those two, staff can check the purchase in the store from inside the ticket. Payment tickets.
Staff matters and partnerships
Complaints about a staff member go here, away from that staff member. Partnerships are their own category so they do not sit in the support queue for a week.
Settings that save the most time
- Staff roles per category, so appeals and staff complaints stay with the people who should see them.
- Channel or private thread, chosen per category. Threads keep the channel list short on busy servers.
- Close quiet tickets: a ticket nobody has written in for a while closes itself, and the player gets a card by DM saying so.
- Rename and move: staff can rename a ticket or move it to another category when a "general" ticket turns out to be an appeal.
- A cap on AI answers per ticket, set per category, where a person should take over after the first reply.
Transcripts stay after a ticket channel is deleted, on every plan, and tickets are unlimited. Entry includes three panels, Starter ten and Pro unlimited.
Don't overdo it
Twelve categories look organised and confuse players, who then pick the wrong one. If two categories go to the same staff and ask the same questions, merge them.
Questions people ask
Should whitelist applications be tickets?
Applications work better as a web form reviewed in Discord, because a whitelist needs more than five questions. Whitelist questions to copy.
Can I move my current panel to FiveBot?
Set up FiveBot's panel next to the old one, run both for a week, then remove the old panel. Switching from a classic ticket bot.