Tickets

Overview#

The Ticket system lets you create support panels that members click to open private ticket channels. Staff can claim, manage, and close tickets with tracked reasons and history. Everything from panel creation to ticket analytics is available on the dashboard.

How to Set Up#

1. Go to the dashboard and select your server
2. Navigate to the Tickets section
3. Click Create Panel to set up a new ticket panel
4. Configure the panel embed: set a name, description, emoji, button label, and button color
5. Choose the category where new ticket channels will be created
6. Set a prefix for the ticket channels (up to 10 characters, e.g., ticket or support)
7. Optionally add ticket types so members can say what their ticket is about before it opens
8. Optionally choose roles to mention when a ticket is opened, so staff are notified immediately
9. Post the panel to a channel, and members will see a button they can click to open a ticket
10. Manage incoming tickets from both Discord and the dashboard

Configuration Options#

Panel Settings#

Setting	Description
Name	The title of the ticket panel embed
Description	Instructions or context shown on the panel
Emoji	An emoji displayed on the panel button
Button Label	Text on the button members click to open a ticket
Button Color	The color style of the panel button
Category	The channel category where ticket channels are created
Prefix	The first part of every ticket channel name, up to 10 characters
Ticket Types	Optional categories members choose from when opening a ticket
Mention Roles	Roles pinged when a new ticket is opened

Channel Naming#

Ticket channels are named prefix-username: the prefix you set on the panel, then the name of the member who opened the ticket. With a prefix of support, a ticket opened by ashleigh becomes #support-ashleigh.

The prefix is a plain piece of text, not a template: there are no placeholders to fill in, and it is capped at 10 characters. Each panel has its own, so a Support panel and a Bug Report panel produce channels you can tell apart at a glance in the channel list.

Ticket Types#

Ticket types let a member tell you what their ticket is about before anyone reads it. Each panel can have up to 15 types, and each type has:

• Name: required, and what the member sees in the list (e.g., Bug Report, Ban Appeal, Partnership)
• Emoji: optional, shown beside the name. Standard emojis and your server's custom emojis both work
• Description: optional one-line explanation shown under the name, useful for steering people to the right option

Types are ordered, and you can move them up and down so the most common reason sits at the top.

What Members See#

• With no types configured, clicking the panel button opens a ticket straight away, exactly as before
• With types configured, clicking the button first asks "What is this ticket about?" and shows a select menu of your types. Picking one opens the ticket

The chosen type is recorded on the ticket, shown as a badge in the dashboard's ticket list, and included in the ticket-opened log entry, so staff know what they are walking into before they read a word.

Ticket Lifecycle#

• Open: A member clicks the panel button and a private ticket channel is created
• Claimed: A staff member claims the ticket, signaling they are handling it
• Closed: The ticket is closed with an optional reason

Dashboard Features#

• Ticket history: View all past and current tickets
• Stats: Track ticket volume, response times, and resolution rates
• Search and filter: Find tickets by member, status, or date

Tips#

• Place ticket panels in a visible channel like #support or #help so members can easily find them.
• Use mention roles to alert your support team the moment a ticket opens. This reduces response time.
• Set up a dedicated category for tickets to keep them separate from your regular channels. You can set default permissions on the category so only staff and the ticket creator can see new channels.
• Add ticket types before you add a second panel. One panel with well-named types is usually easier for members to navigate than several panels scattered across channels.
• Keep type names short and type descriptions specific. "Ban Appeal: appeals for bans issued in this server" stops people opening appeals for the wrong thing.
• Encourage staff to claim tickets to avoid multiple people working on the same request.
• Close tickets with a reason so you have a clear record of how each issue was resolved. This is valuable for reviewing patterns and training new staff.
• Review ticket stats on the dashboard periodically to identify peak times, common issues, and how your team is performing.