Skip to main content
Fire’s ticket system allows you to create a professional support workflow where members can open private tickets to get help from your team. Each ticket is a private channel visible only to the member and your support staff.

What is the ticket system?

The ticket system creates a structured way for members to:
  • Request support privately
  • Report issues or problems
  • Apply for server positions
  • Submit appeals or complaints
  • Get individual assistance from your team
Benefits:
  • Organized support workflow
  • Private conversations with members
  • Dedicated channels for each request
  • Easy for staff to manage multiple tickets
  • Automatic ticket logging and archiving

Setting up tickets

Enable the ticket system

/ticket enable category:"Support Tickets" channel:#open-ticket
Parameters:
  • category - The category where ticket channels will be created
  • channel - The channel where members click a button to open tickets
1

Create a category

First, create a category in your server called “Support Tickets” (or any name you prefer).
2

Create a ticket channel

Create a channel (e.g., #open-ticket) where members will open tickets.
3

Run the enable command

Use /ticket enable to set up the system with your category and channel.
4

Customize the message

Fire will send a message with a button in the ticket channel. Members click this button to open tickets.
Make sure Fire has permissions to create channels in the category and manage permissions in those channels.

Configure ticket settings

Set maximum tickets per user

Prevent spam by limiting how many tickets each member can have open.
/ticket limit number:3
This allows each member to have up to 3 open tickets at once.
The default limit is 1 ticket per user. Adjust this based on your server’s needs.

Managing tickets

Opening a ticket

Members open tickets by clicking the button in your designated ticket channel. Fire will:
  1. Create a new private channel
  2. Give the member access to the channel
  3. Give your support team access
  4. Ping the alert role (if configured)
  5. Send a welcome message

Working with tickets

Close a ticket

Mark a ticket as resolved and archive it.
/ticket close reason:"Issue resolved"
Options:
  • reason - Why the ticket is being closed (optional)
When a ticket is closed:
  • The channel is deleted
  • A transcript may be saved (if configured)
  • The member can open a new ticket
Only support staff and the ticket creator can close tickets.

Advanced settings

Toggle ticket system

Temporarily disable ticket creation without removing the system.
/ticket toggle
This prevents members from opening new tickets while keeping existing tickets active.
Disable tickets temporarily during:
  • Major server events when staff is busy
  • Server maintenance
  • Staff meetings
  • Times when you can’t handle support requests

Invitable tickets

Allow ticket creators to invite their friends to their tickets.
/ticket invitable
When enabled, members can use /ticket add in their own tickets to invite others.
Be cautious with this setting - it allows members to bring others into private conversations with your staff.

View ticket info

Get help with ticket commands.
/ticket help
Shows all available ticket commands and their usage.

Ticket workflow example

1

Member opens ticket

User clicks “Open Ticket” button in #open-ticket channel.
2

Private channel created

Fire creates a private channel (e.g., ticket-001) and pings @Support role.
3

Support responds

Support staff member responds to the ticket and helps the user.
4

Add specialist if needed

If specialized help is needed, use /ticket add to bring in another staff member.
5

Close when resolved

Once the issue is resolved, use /ticket close to close and archive the ticket.

Best practices

Clear guidelines

Create a tag or embed explaining when and how to use tickets.

Quick responses

Try to respond to new tickets within a few minutes to show you care.

Professional tone

Train your support team to be friendly and professional in tickets.

Close resolved tickets

Don’t let old tickets pile up - close them when issues are resolved.

Use ticket reasons

Always include a reason when closing tickets for better record-keeping.

Set expectations

Let members know your typical response time in the ticket description.

Ticket permissions

Required bot permissions

Fire needs these permissions in the ticket category:
  • Manage Channels - To create and delete ticket channels
  • View Channels - To see ticket channels
  • Send Messages - To send messages in tickets
  • Embed Links - To send formatted messages
  • Manage Permissions - To control who can see each ticket

Staff permissions

Your support team should have:
  • Manage Server permission, OR
  • A role that’s configured as a moderator via /moderators add
These permissions allow them to:
  • See all tickets
  • Add/remove users from tickets
  • Close tickets
  • Configure ticket settings

Common use cases

Support tickets

Members can get help with:
  • Account issues
  • Technical problems
  • Questions about server features
  • Reporting bugs

Applications

Use tickets for:
  • Staff applications
  • Partnership requests
  • Content creator applications
  • VIP/premium role requests

Reports

Handle sensitive reports via tickets:
  • User behavior reports
  • Rule violation reports
  • Bug reports
  • Suggestions (if you prefer private submissions)

Appeals

Allow members to appeal:
  • Bans or kicks
  • Mutes or warnings
  • Role removals
  • Other moderation actions
Fire also has a dedicated /appeals system for ban appeals that works separately from tickets.

Troubleshooting

Make sure Fire has permission to send messages and embed links in the ticket channel. Try running /ticket enable again.
Check that Fire has “Manage Channels” permission in the ticket category. Also verify the category isn’t full (Discord has a 50 channel limit per category).
Make sure your support staff have the “Manage Server” permission or have been added as moderators using /moderators add.
Check if the ticket system is toggled off using /ticket toggle. Also verify the member hasn’t reached their ticket limit.

Command summary

CommandDescriptionRequired Permission
/ticket enableSet up the ticket systemManage Server
/ticket toggleEnable/disable ticket creationManage Server
/ticket limitSet max tickets per userManage Server
/ticket nameSet ticket naming formatManage Server
/ticket descriptionSet ticket panel descriptionManage Server
/ticket alertSet role to ping on new ticketsManage Server
/ticket invitableAllow members to invite to their ticketsManage Server
/ticket closeClose a ticketManage Server / Moderator
/ticket addAdd user to ticketManage Server / Moderator
/ticket removeRemove user from ticketManage Server / Moderator
/ticket listList all open ticketsManage Server / Moderator
/ticket helpGet ticket command helpEveryone

Build docs developers (and LLMs) love