Tickets
Create and manage support ticket channels with customizable workflows and staff roles.
Overview
The ticket system allows servers to create dedicated support channels for users. Administrators set up panels with button or dropdown menus, and members create tickets by selecting an option. Staff can claim, manage, and track tickets with full customization.
Getting Started
Run one command:
,ticket setup
Pick the channel your panel goes in and the role that answers tickets, and press Create panel. That's it — the panel is published and working. A category is optional; without one, tickets open at the top level.
Everything else has a sensible default you can change later from ,ticket panel.
Prefer to do it by hand? ,ticket panel create (name) [mode] and ,ticket panel send (name) still work, along with every other subcommand.
Panels can use button or dropdown mode (default). You can create up to 15 panels per server.
Before sending a panel, you must add at least one option to it. The panel message requires Send Messages and Manage Webhooks bot permissions in the destination channel.
Panel Setup
Configure where and how ticket panels appear.
Options & Categories
Options are the buttons or dropdown choices users click to create a ticket. Each option can route to its own category.
Support Roles & Access
Control which roles can see, claim, and manage tickets.
Forms & Fields
Forms collect structured data from users when they create a ticket. Each panel can have multiple forms, and each form can have up to 5 fields.
Ticket Lifecycle
Commands for creating, claiming, and managing open tickets.
Ticket Management
Rename, move, and edit metadata on tickets.
Blacklist
Prevent users or roles from creating tickets.
Blacklisted users cannot create tickets but can still be added to existing tickets manually.
Claim Profiles
Members can set a personalized greeting message that displays when they claim a ticket.
Listing & Statistics
View ticket history and statistics.
Priorities, Ratings & Notes
Tools your staff use inside a ticket.
Ratings & Analytics
On the dashboard
Everything above is configurable from Discord, and the parts you are most likely to want on a screen are on the dashboard too, under Tickets.
Channel name formats
An option can name its ticket channels one of three ways:
- Case number —
ticket-0001, the default. - Username —
someone-ticket. - Option name —
support-0001, useful when one panel offers several very different options.
You can also type your own format instead of picking one of the three.
Appeal a punishment with a form
Add a case field to a form and the person opening the ticket picks which punishment they're appealing from a dropdown of their own cases — no typing an ID, and no way to reference someone else's.
If they have no cases on record, the field is skipped automatically rather than showing an empty dropdown.
Troubleshooting
If the panel message doesn't post, check that the bot has Send Messages and Manage Webhooks permissions in the destination channel.
A panel must have at least one option before it can be published. Use ,ticket option add to add options first.
If no category is set for an option, tickets will use the panel's default category. If neither is set, tickets create in the guild root.
Support roles are required for staff to claim tickets. If no roles are set on an option, only users with Administrator permission can interact with those tickets.
Deleted panels cannot be recovered. Transcripts are sent to the log channel before deletion.