Without a ticket system, requests end up in the DMs of whichever moderator happened to be online. The rest of the team never hears about it, and if that person is busy for a week the person asking keeps waiting. A ticket turns that into a channel everyone responsible can see.
/ticket open creates a private channel for the topic given, visible only to the person who opened it and the support team. Everything about that case then lives in one place, including screenshots and follow-up questions that would have been buried in a public channel.
Because a ticket is an ordinary channel, anyone responsible can step in without anything being forwarded. Handovers take care of themselves: whoever has time picks it up, with the history sitting right above. /ticket list shows which cases are still open.
/ticket close ends the case and archives the channel rather than simply deleting it. That keeps it traceable later on how a case was decided. That helps when the same question comes back, or when someone questions a decision.
These slash commands belong to this module. Discord shows them with a description as you type, so nobody has to memorise them.
/ticket open/ticket close/ticket listOnly the person who opened it and the roles you designate as responsible in the dashboard. For every other member the channel is invisible.
Yes. /ticket list gives the team an overview of everything still open, so nothing is forgotten just because it scrolled out of the channel list.
The channel is archived rather than deleted, so the history is preserved. That makes it possible to read back later what was discussed and decided.
Invite it, configure it in the dashboard, done. Free, with no premium tiers and no features locked behind a paywall.
Invite