Commands Reference
All TicketFlow slash commands, their options, and what they do.
/setup
Creates a new ticket board in the current channel.
Permission required: Manage Server
/setup name:Bug Reports category:#Support staff_role:@Moderatorsname
Yes
Text (max 100)
Board name shown on the embed
category
Yes
Channel category
Where ticket channels are created
staff_role
Yes
Role
Role that can view/manage tickets on this board
message
No
Text (max 2000)
Description shown on the embed
color
No
Hex code
Embed accent color (default: #5865F2)
maxtickets
No
Number (0–25)
Max open tickets per user on this board (0 = unlimited, default: 1)
What happens: TicketFlow posts an embed with an "Open Ticket" button. Users click it to create a ticket.
You can run /setup multiple times in different channels to create multiple boards (e.g. one for general support, one for bug reports).
/ticket close
Closes the current ticket. Run this inside a ticket channel.
Who can use it: Staff members (anyone with the board's staff role) or the user who opened the ticket.
What happens:
An HTML transcript of the conversation is generated
The transcript is DM'd to the ticket creator
A closure message is posted in the channel
The ticket status is set to Closed
The channel is deleted after 5 seconds
Closed tickets remain visible on the web dashboard under the Closed tab.
/ticket claim
Claims the ticket so other staff know you're handling it.
Who can use it: Staff members only (must have the board's staff role).
What happens: The ticket is marked as claimed by you. A message is posted in the channel and the claim is logged (if a log channel is configured). Claimed tickets show the staff member's name on the web dashboard.
/config logchannel
Sets or clears the channel where ticket events are logged.
Permission required: Manage Server
channel
No
Text channel
Log destination (leave empty to disable logging)
Logged events: Ticket opened, ticket claimed, ticket closed — with timestamps, user info, and ticket details.
/config maxtickets
Sets the maximum number of open tickets a single user can have across all boards.
Permission required: Manage Server
limit
Yes
Number (0–25)
Max open tickets per user (0 = unlimited)
This is a server-wide limit. Individual boards can also have their own per-board limit set during /setup.
/config autoclose
Sets how many days of inactivity before a ticket is automatically closed.
Permission required: Manage Server
days
Yes
Number (0–90)
Days of inactivity before auto-close (0 = disabled)
Note: The auto-close check runs periodically. Tickets with no messages for the configured number of days are automatically closed with a transcript DM to the creator.
/refresh
Re-sends a board embed in the current channel with up-to-date template buttons. Use this after adding or removing templates from a board on the web dashboard.
Permission required: Manage Server
board
Yes
Text
Name of the board to refresh (case-insensitive)
What happens: TicketFlow posts a new embed with one button per enabled template linked to the board. The old embed stays in the channel (you can delete it manually). If no templates are linked yet, the embed shows a hint to add them from the dashboard.
Typical workflow:
Create a board with
/setupCreate templates and link them to the board from the Templates tab in the dashboard
Run
/refresh board:<name>in the channel to display the updated buttons
/config view
Displays the current server configuration.
Permission required: Manage Server
Shows: log channel, max tickets per user, and auto-close setting.
Last updated