Skip to main content

Ticket Categories

Categories define the types of tickets your server accepts. Each category has its own Discord channel location, naming pattern, welcome message, support roles, creator restrictions, logging, and automations.

Common examples are Support, Bug Reports, Billing, Appeals, and Partnerships.

Each ticket is a channel by default. A category can instead open each ticket as a private thread in one channel, which avoids Discord's 50-channel category limit. See Thread Tickets.

Create a category

Open Categories

In the dashboard, select your server and open Categories.

Create the category

Click Create Category, then enter a name, optional emoji, and short description.

Pick the Discord category

Choose the Discord category where ticket channels should be created. Add overflow categories only if your server regularly hits Discord's channel limit.

Set messages and permissions

Write the intro message, choose support roles, and decide whether only certain member roles can create tickets.

Save and test

Save the category, then open a test ticket from a panel or command.

Important settings

SettingWhat it does
Name and emojiLabel shown in the dashboard, panels, and select menus
DescriptionShort explanation shown to users when choosing a category
Naming patternChannel name format, such as ticket-{{ticket.number}} or {{user.username}}-ticket
Max open tickets per userPrevents one user from opening too many tickets in this category
Ticket styleChannel (a channel per ticket) or Private thread (a thread per ticket in one channel). See Thread Tickets
Open categoriesOne or more parent categories where ticket channels are created. They fill in order: the first until it is full, then the next
Closed categoriesOptional parent categories a ticket's channel is moved to when it closes. Leave empty to keep the channel where it is
Intro messageFirst message shown when a ticket opens. See Custom Messages
Support rolesStaff roles that can see and manage tickets
Allowed user rolesMember roles allowed to create tickets
Blocked user rolesMember roles that cannot create tickets, checked before allowed roles
Log channelWhere ticket events are posted
Transcript channelWhere saved transcripts are posted
LookupsFetch the opener's linked Roblox account (Community and Pro) or call your own API (Pro) when a ticket opens. See Lookups

Naming variables

Use variables in the naming pattern. The Variables button next to the field lists them all.

VariableExample output
{{ticket.number}}0042, zero-padded to the category's number padding
{{user.username}}, {{user.id}}alex, 123456789012345678
{{category.name}}, {{guild.name}}support, my-server
{{ticket.status}}, {{ticket.priority}}open, high

Recommended patterns:

  • ticket-{{ticket.number}} for most servers
  • {{category.name}}-{{ticket.number}} when you have several ticket types
  • {{user.username}}-{{ticket.number}} when staff need to spot the creator quickly

Permissions

Category permissions are split:

  • Support Roles decide who can view and manage tickets in the category.
  • Who Can Open Tickets decides who can create tickets in the category: Allowed roles limit it to those roles, and Blocked roles shut roles out.

Leave Allowed roles empty if everyone can create tickets. Add roles only when the category should be restricted, such as staff-only, VIP-only, or customer-only support.

Automations

After a category is saved, use its Automations link to attach actions such as welcome messages, priority changes, reminders, auto-close rules, webhooks, or support flows.

Workflow Buttons

Workflow buttons are extra buttons on a category's ticket-opening message, next to the default Close / Claim / Add Note buttons. Clicking one starts a support flow, useful for actions staff use often, like escalating to billing or requesting more information.

Open the Buttons tab

In the dashboard, open the category and go to its Buttons tab.

Add a button

Click Add button, then choose the flow it should run, a label (up to 80 characters), an optional emoji, and a style. Button styles use the same four Discord colors as panel buttons. See Button Styles.

Choose the layout

Toggle Inline layout to place workflow buttons on the same row as Close / Claim / Add Note, or leave it off to give them their own row below.

Reorder or remove

Use the arrows next to a button to reorder it, or delete it when it's no longer needed.

Who can use them

Only staff with support-role access to the category can see and click workflow buttons. If the linked flow is deactivated, the button still shows but won't run the flow. Reactivate the flow or point the button at a different one.

Good defaults

Server typeSuggested categories
CommunitySupport, Reports, Appeals
Product or SaaSGeneral Support, Billing, Bugs, Feature Requests
MarketplaceBuyer Help, Seller Help, Disputes
GamingSupport, Player Reports, Ban Appeals

Start with fewer categories. Add more only when staff genuinely need different permissions, forms, messages, or routing.

Troubleshooting

ProblemCheck
Ticket channel is created in the wrong placeThe category's Discord category setting points to the right parent category.
Staff cannot see ticketsTheir Discord role is listed under Support Roles.
Members cannot open ticketsAllowed roles is empty or includes one of their roles, and no Blocked role applies.
Channel names look wrongThe naming pattern uses supported variables and no unsupported characters.
Logs are missingA log channel is selected and the bot can send messages there.