Configuration lives on a dashboard, not in command flags
Most ticket bots configure a category through a sequence of slash commands and modals, one flag or subcommand per setting. Here, creating a category, setting staff roles, channels, questions, permissions and voice options all happen on the web dashboard, see Ticket settings, including sending the panel itself through the dashboard’s Message builder rather than a command. This isn’t unique to tickets. Applications, jail, leveling and roleplay all use the same dashboard, so a server doesn’t end up running one bot for tickets and separate bots for applications, leveling and moderation-adjacent jail handling.Transcripts are signed, not just archived
Closing a ticket generates an HTML transcript and signs it the moment it’s created. Running/verify on that file later confirms whether it’s genuinely unmodified since closing, been edited, or never came from this bot at all. Most ticket bots archive a transcript; this one lets anyone check it hasn’t been altered after the fact.
Command permissions aren’t just Discord’s
Discord’s own permission system only gates a command server-wide, by role. Command permissions adds required roles, required channels (or whole categories), a Discord permission on top of the command’s own default, and a per-user cooldown, scoped to a single command or a whole module, from the dashboard. No separate permissions bot needed to say “only these roles, only in this channel, once every 10 minutes.”The free tier runs every feature, not a trimmed preview
Tickets, applications, jail, leveling and roleplay all work with their full mechanics for free, see Premium. Upgrading raises numeric limits, category counts, role list lengths, question counts, and unlocks cosmetic fields like channel name templates and rank card backgrounds. It doesn’t unlock a feature that was disabled before, and downgrading later doesn’t delete anything already configured, see the FAQ.Jail is the ticket system, not a bolted-on module
Jailing a member opens a private channel for them in a dedicated category, uses the same claim/close/transcript flow as a support ticket, and can be escalated into or out of like any other category. See Jail. There’s no separate punishment-log feature with its own, different UI to learn.A real message builder and webhook sender, not just ticket/application panels
The dashboard’s Message builder composes and sends any Discord message: text, embeds, image galleries, buttons, select menus, sent as the bot or through a webhook with a custom name and avatar. It replaces/ticket send and /application send, but works for arbitrary announcements too, no separate webhook tool or bot needed.
Every command works identically as ! or /
Slash and prefix commands run the same code, not a stripped-down prefix fallback, see the FAQ. The handful that don’t (like /ticket send, deprecated in favor of the dashboard) are called out explicitly wherever they come up.