How to Set Up a Discord Ticket System
Category panels, staff claiming, and transcripts — how to configure Airwavy's ticket system, and what Premium adds for larger teams.
Quick answer
A ticket system turns unstructured DMs and mentions into a proper workflow: a member opens a ticket from a category panel, staff claim and handle it in a private channel, and it closes with a transcript link. Airwavy's free tier covers persistent buttons, claiming, and close logs; Server Premium adds SLA response reminders, inactivity auto-close, and up to 25 ticket categories.
What you'll learn
- Why unstructured support (DMs, mentions) breaks down as a server grows
- What's free versus what Premium adds for larger teams
- How to set up category panels correctly
- How claiming and transcripts actually work
- Common mistakes that leave tickets visible to the wrong people
Why unstructured support doesn't scale
In a small server, a DM to a staff member or a mention in general chat works fine. As a community grows, that same pattern means requests get lost, no one knows who's already handling what, and there's no record once the conversation is over. A structured ticket system fixes all three at once.
What Discord itself offers
Discord has no native ticket or support-request feature — private channels can be created manually, but there's no category system, no claiming mechanism, and no automatic transcript when one closes. Every part of a real ticket workflow comes from a bot.
How Airwavy's ticket system works
Category panels give members a clear starting point, and persistent entry buttons survive a bot restart — a ticket workflow that keeps working even through routine maintenance.
- Free: persistent ticket buttons, staff claiming, close logs, DMs, and dashboard transcript links.
- Server Premium: SLA response reminders so a ticket doesn't sit unanswered, inactivity auto-close rules, and up to 25 ticket categories instead of the free tier's smaller set.
- Claiming lets one staff member take ownership of a ticket so members aren't getting conflicting answers from multiple people at once.
One open ticket per member in this category.
Greet members the moment a ticket opens.
Set it up
- Open Support Tickets in the dashboard and create your category panel.
- Add the categories your community actually needs (general support, reports, appeals) — start small, you can add more later.
- Configure the staff roles allowed to see and claim tickets.
- On Premium: set SLA reminder timing and inactivity auto-close rules if your team needs them.
- Publish the panel and open a test ticket to confirm the full flow — open, claim, close, transcript.
Common mistakes
- Creating too many categories up front — start with the essentials and expand only when a real need shows up.
- Not restricting who can see and claim tickets — review staff role access before launch.
- Skipping the test ticket — confirm the full open-to-transcript flow works before announcing it to the community.
- Ignoring SLA reminders once configured — they're only useful if staff actually act on them.
Troubleshooting
The category panel button doesn't respond
Confirm the panel is still published and Airwavy can view and send in the panel's channel — persistent buttons should survive a bot restart, but a deleted or heavily restricted channel will still break them.
A ticket transcript is missing
Check the dashboard transcript link directly — transcripts are generated on close, so a ticket that's still open won't have one yet.
I need more than the free category limit
That's a Server Premium upgrade — free servers have a smaller category limit, Premium raises it to 25.