Tickets

A ticket panel is a message with a button. Pressing it opens a private channel between the member and your staff. Everything else — naming, transcripts, closing, reopening — is configuration on that panel.

Setting up a panel

1. 1

   Choose where tickets are created

   A category the bot can create channels in. Discord caps a category at 50 channels, so pick a closing or archiving policy at the same time rather than later.

2. 2

   Choose who can see them

   The staff roles granted access to every ticket. Access is applied per channel as the ticket opens, so adding a staff role later does not grant it access to tickets already open.

3. 3

   Write the panel message

   The message members see, with the button on it. This is the one place the panel's text, embed and buttons are edited.

4. 4

   Name the channel

   A template such as ticket-{user.name}. The name is what your staff scan, so put the useful part first.

The rename budget

Opening hours

A panel can accept tickets only during set hours. Outside them, the button replies with your closed message instead of opening a channel. The schedule is a weekly grid in UTC — set it in UTC deliberately, because a schedule that follows a staff member's local time drifts twice a year.

Closing and transcripts

• Closing removes the member's access but keeps the channel, so staff can still read it.
• Deleting removes the channel. If transcripts are on, one is saved first.
• Reopening restores the member's access to the same channel, keeping the history in one place.