Custom Commands

Custom commands are commands you create for your server. They can open a ticket directly or start a support flow first.

Use them when users or staff should be able to trigger support without finding a panel message.

Command types

Type	How users run it	Best for
Slash command	Type `/name` in Discord	Public support, bug reports, appeals, staff shortcuts
User context command	Right-click a member, then choose Apps	Staff actions about a specific user
Message context command	Right-click a message, then choose Apps	Reporting a message or opening a ticket with message context

Discord allows up to 5 user context commands and 5 message context commands per server. Slash command limits are controlled by your Ticket Tool plan.

In the dashboard, select your server and open Commands.

Pick slash, user right-click, or message right-click.

Choose Open Ticket to create a ticket immediately, or Start Flow to run a support flow first.

For Open Ticket, choose a category. For Start Flow, choose a flow.

Leave allowed roles empty for everyone, or add roles for staff-only or customer-only commands.

Save the command, wait for Discord to update, then run it in your server.

Slash command names must be lowercase, 1-32 characters, and cannot contain spaces. Use short names that describe the action.

Good examples:

Avoid generic names such as /help and long names that are hard to type.

Context-menu commands can use spaces and capital letters because users choose them from Discord's right-click menu.

Use commands when...	Use panels when...
Users already know what to run	New users need a visible entry point
Staff need private shortcuts	You want a public support channel
One action is enough	Users need to choose between several categories
The command should work from many channels	The entry point should stay pinned in one channel

Many servers use both: a public panel for members and staff-only commands for faster internal work.

When a context command starts a flow, Ticket Tool passes the clicked user or message into the flow.

Common examples:

Variable	Meaning
`{{options.target_user}}`	User selected by a user context command
`{{options.target_message_link}}`	Link to the selected message
`{{options.target_message_content}}`	Content from the selected message, when available

Problem	Check
Command does not appear	Give Discord time to sync, and check that the command is enabled.
User cannot run it	Their role is allowed, and the channel permits Use Application Commands.
It opens the wrong ticket type	The command points to the correct category or flow.
Context command has no options	This is expected; Discord context commands do not have custom options.
Flow variables are empty	The flow is using variables that match the command type.