All ticket commands use the
ticket group (alias tickets). They require Manage Server unless noted otherwise.What you can configure
Limits
Limits
- Up to 15 ticket panels per server
- Up to 5 active options per panel (more can be saved on standby)
- Up to 25 forms per server, 5 fields per form
- Up to 25 options shown on a deployed panel (Discord component limit)
Panels
Panels
- Button or dropdown display mode
- Custom panel embed/message
- Default and overflow categories
- Per-user open ticket limits
- Channel naming format and case IDs
Options
Options
- Label, emoji, button color, and dropdown description
- Support and trainee roles
- Required roles to open a ticket
- Intake forms
- Custom greeting, close, claim, reopen, and automation messages
- Claim/close/reopen/delete button labels and styles
- Category moves on claim or close
- Channel rename templates
Server-wide settings
Server-wide settings
- Transcript channel (
,ticket transcript) - Log channel (
,ticket log) - Global staff role (
,ticket staff)
Quick setup
1
Create a panel
,ticket panel and click Add in the interactive manager.2
Add at least one option
3
Configure (optional)
Run
,ticket panel, select your panel, and use the buttons:- Behaviour - delete delay, max open tickets, claims toggle
- Categories - where new ticket channels are created
- Display - button vs dropdown mode, channel name format
- Message - custom panel embed
- Options - per-option roles, forms, messages, and behaviour
4
Deploy the panel
5
Set transcript channel (recommended)
6
Set log channel (recommended)
7
Set staff role (recommended)
How it works
- A member uses your deployed panel (button or dropdown).
- If the option has a form with fields, they answer questions in a Discord modal first.
- adore creates a private channel, sets permissions for the creator and support roles, and sends a greeting.
- Staff work in the channel. Action buttons (claim, close, reopen, delete) are configured per option in the panel manager.
