🎫 Tickets

Private support channels opened with a button, with transcripts and multi-type panels.

How it works

Create a panel on the dashboard: name, description, color, and one button per ticket type (Support, Partnership, Report...).
Each type has its own staff roles (they see, manage and get pinged), its channel category, and optional questions asked at opening.
On close, a transcript of the conversation can be saved. Inactive tickets can close automatically.
A 🔊 Voice channel button (staff or the ticket's author) opens a matching voice channel alongside the text one, mirroring the same access - handy for a support case that's easier to sort out by talking. It's removed together with the text channel when the ticket closes, with a warning posted in the voice channel a few seconds before.
Closing a ticket now asks for confirmation first ("Are you sure?"), whether it's clicked as a button or typed as /ticket close - a miss-click or a fast command no longer deletes a channel by accident.
A panel can be disabled with its toggle: buttons then refuse to open new tickets.
The module switch (top right of "General configuration") turns the whole system off: no new ticket can be opened, whatever the panels say. Panels and already-open tickets stay in place, and they can still be claimed, transcripted and closed - switching the module off must never trap members in a ticket nobody can close.

💡 With the module off, the health check stops reporting the tickets settings (a missing staff role on a disabled module is not a problem).

/ticketManage the current ticket (close, add a member...).

/ticket-configQuick setup from Discord.

💡 Everything is easier from the dashboard → Tickets page: panels, types, roles and questions in one place.