How to set up a ticket system in Discord

A ticket system turns "DM a mod and hope they see it" into organised, private support channels your staff can actually track. With Skipper you can build one entirely inside Discord, with no second bot and no external dashboard. Here's how it works.

Where to find it

Run /config, open the Category dropdown, choose Support, then Tickets, and toggle the module on.

Tickets are built from two pieces:

• Panels: the template for one kind of ticket (its name, appearance, staff, and questions).
• Platforms: the clickable embed you post to a channel. Each platform links to one or more panels as buttons or a dropdown.

Step 1: Create a panel

In the Tickets menu choose Panels Add Panel and give it an id (letters, numbers and dashes). Then set:

• Display Layout: the label, description, emoji and colour members see.
• Ticket staff: the roles that can see and handle the ticket, with an optional ping.
• Modal inputs: up to five questions members answer before the ticket opens, so staff have context immediately.

Optional extras include transcripts, a creation message, a close-confirmation prompt, a staff control panel, and an inactivity timer that auto-acts after a set period.

Step 2: Post a platform

Choose Platforms Add Platform, set the Platform Message embed, then pick your Linked Panels and whether they appear as Buttons or a Dropdown Menu. Finally, Send it to a channel.

Make sure Skipper has View Channel, Send Messages and Embed Links in that channel, or the send will fail.

Step 3: Decide the limits

• Limit: one open ticket per panel or one per server.
• Blacklisted Roles: roles that can't open tickets.
• Commands: in-ticket message commands with buttons like Close Ticket, Claim Ticket and Ping Staff.

How members and staff use it

Members click the button (or pick the dropdown option) on your posted platform. If the panel has questions, they fill those in first. A private ticket opens with your staff roles added, and staff work it using the control panel or your custom commands.

Tips & gotchas

• Panels must exist before platforms. You can't post a platform with nothing linked to it.
• After editing a platform, use Sync to update the already-posted message instead of sending a new one.
• Prefer lightweight tickets? Flip the system to Thread mode, though the Category and Base Permissions options aren't used there.
• Roles that carry dangerous permissions can't be added by ticket commands, and Skipper only manages roles below its own, so keep its role high enough in your list.

For every setting in detail, see the Tickets documentation. Ready to try it? Add Skipper to your server and run /config.