Panel
The message members interact with. It lives in a channel and shows either buttons or a dropdown. A server can have several — one in
#support, one in #staff-applications.Option
A reason for opening a ticket — one button or one dropdown entry. “General Help”, “Report a User”, “Billing”. Options belong to a panel, and carry almost all the configuration: which roles can open them, which roles can see them, what category the channel goes in, what messages get sent.
Ticket
The channel created when someone picks an option. It gets a case number, controls for claiming and closing, and produces a transcript when it’s done.
The fast way
configure, config. Requires ticket staff or Administrator.
If you’d rather do it by hand, the manual version is:
1
Set your staff roles
2
Create a panel
3
Add options
4
Post it
Day-to-day commands
For staff, once tickets are running:
For members:
Access control
Three levels, set per option:
Plus the global staff roles from
!tickets staff, which apply everywhere.
Full detail in Access & permissions.
Lifecycle automation
Options can manage themselves. All of these are per-option, and0 turns each off:
Where to go next
Panels
Modes, categories, naming formats, case numbers, limits.
Options
Labels, emojis, styles, categories, lifecycle timers.
Access
Support roles, trainees, requirements, blacklists.
Messages
Greetings, DMs, close notices, and the forms system.
Transcripts
Where they’re stored and how to pull them back.
