Tickets
The ticket system gives members a private channel to talk to your staff team, without exposing the request to the whole server. Categories let you route different kinds of requests to different staff roles, and every closed ticket is archived to a plain-text transcript before its channel is deleted. Everything below can be configured either from this dashboard or directly in Discord with /ticket and /ticketcat.
What it covers
- A ticket panel — buttons or a dropdown, your choice — that members click to open a private channel. Post it with /ticket panel wherever members should open requests.
- Up to 25 optional categories, each with its own priority, parent Discord category, panel channel, opening message, staff roles, and per-category open-ticket limit — create or edit one in a single command with /ticketcat add and /ticketcat edit, or use the dashboard form. Skip categories entirely to use one default ticket type instead.
- A dedicated single-category panel for any category via /ticketcat panel (or the dashboard's per-category "Post panel" button) — handy for posting an "Open Billing" button in a channel of its own.
- "One open ticket per member" per category, so the same person can't stack multiple requests in the same queue.
- Claim/unclaim buttons on the ticket's opening message (also available as /ticket claim and /ticket unclaim for managers) let staff signal who's handling a request — the status updates live in that embed, not just a follow-up message.
- Auto-warn and auto-close for inactive tickets, with warning/close timers that persist across bot restarts — configure it from the dashboard or with /ticket inactivity.
- /ticket settings gives staff a quick read-only summary of the current configuration without leaving Discord.
- Automatic archiving on close: every message, author, and timestamp is written to a transcript before the channel is deleted, and the closure is logged with a link to it.
How to configure it
- Open the Tickets section of the dashboard, or use /ticketcat and /ticket in Discord — both write to the same configuration.
- Optionally add categories under step 1 — each needs a name, staff roles, and (optionally) a parent category, dedicated panel channel, opening message, and its own ticket limit. In Discord this is one command: /ticketcat add, with /ticketcat edit to change any field afterward. Leave categories empty to use a single default ticket type.
- Set the server-wide defaults under step 2 — maximum concurrent open tickets (/ticket limit), panel display style (buttons support up to 5 categories; use the dropdown for more), the log channel (/ticket log), the default parent category (/ticket defaultcategory), and the auto-warn/auto-close inactivity timers (/ticket inactivity).
- Post the panel with /ticket panel in Discord (or the per-category /ticketcat panel / the dashboard's "Post panel" button for a dedicated single-category panel). The panel updates automatically if you rename or remove a category afterward.
- Closed tickets and their transcripts are listed under "View archived tickets" on this page, with per-ticket detail including open/close times and first-response time.
TipStart with a small number of categories. It's easier to split a busy category into two later than to untangle an overly granular setup — and switching to the buttons panel style later requires 5 or fewer categories.
Looking for exact syntax?
This page covers what the feature does and how to turn it on. For every command, option and cooldown in Tickets, see the Tickets command reference.