Tickets
Panel buttons, departments, claiming, transcripts and logging — the complete support ticket flow.
The tickets module gives each server a support panel with private channels, staff claiming, transcripts and per-department routing.
Set up the panel#
- Configure the panel on the dashboard (fields) or with slash commands.
- Publish it: run
/ticket panel(optionally with a target channel — Manage Server or Administrator required). The panel posts one message with a Open Ticket button. - Members click the button; a ticket channel is created in the configured category and only the creator, support roles and the bot can see it.
Every server holds one live panel message; publishing again replaces it.
Departments#
Configure up to ten departments, each with its own label, emoji, description, category and extra support roles. A panel with departments shows:
- one button per department (up to five),
- a select menu instead when there are more than five departments.
The buttons#
| Button | Action |
|---|---|
| Open Ticket | Creates the ticket (honours the max-open-per-user limit) |
| Claim Ticket / Unclaim | Staff-only; marks a staff member as responsible |
| Close Ticket | Staff, or the creator when allow user close is on |
| Reopen | Restores a closed ticket |
| Delete / Confirm delete | Two-step delete; generates a transcript first |
Slash commands#
/ticket carries the full management surface:
| Subcommand | Who | Purpose |
|---|---|---|
panel | Manage Server / Administrator | Publish or refresh the panel |
claim, unclaim | staff | Manage responsibility |
close, reopen | staff (or creator, per config) | Lifecycle |
delete | staff | Transcript + channel delete |
add <member> | staff or creator | Give a member access |
remove <member> | staff | Revoke access (creator and bots cannot be removed) |
info | anyone in the ticket | Status, creator, opened/claimed/closed times, department |
Transcripts#
When transcripts enabled is on, deleting a ticket generates a transcript of the channel history (fetched in pages of 100 messages), posts it to the ticket log channel, and only then deletes the channel. Deleting a channel manually marks the ticket closed too.
Logging#
Ticket opened, closed and reopened events post to the logging channel (green / yellow / green) under their own log keys, and the ticket log channel receives panel and transcript activity. See Logging.