Custom & Built-in Commands
The Commands page in the dashboard does two things:
- 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.
- Built-in commands are the ones Ticket Tool comes with, such as
/new,/closeand/claim. The card at the bottom of the page lets you turn them on or off for your server. The Command Reference lists what each one does.
Opening the page needs the Manager role. Read-only staff can see it, but the controls are turned off for them.
Command types
| Type | How users run it | Best for |
|---|---|---|
| Slash | Type /name in Discord | Public support, bug reports, appeals, staff shortcuts |
| User context | Right-click a member, then choose Apps | Staff actions about a specific user |
| Message context | Right-click a message, then choose Apps | Reporting a message or opening a ticket with message context |
Free servers can have up to 5 custom commands (Community: Unlimited, Pro: Unlimited). Discord separately allows up to 5 user and 5 message context commands per server.
Create a command
Open Commands
In the dashboard, select your server and open Commands.
Choose the command type
Pick slash, user right-click, or message right-click.
Set the action
Choose Open Ticket to create a ticket immediately, or Start Flow to run a support flow first.
Pick the target
For Open Ticket, choose a category. For Start Flow, choose a flow.
Restrict access if needed
Leave allowed roles empty for everyone, or add roles for staff-only or customer-only commands.
Save and test
Save the command, wait for Discord to update, then run it in your server.
Naming
Slash command names must be lowercase, 1-32 characters, and cannot contain spaces. Use short names that describe the action.
Good examples:
/support/bug/billing/appeal/report-user
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.
Command or panel?
| 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.
Turn built-in commands on or off
The Built-in commands card at the bottom of the Commands page shows how many of Ticket Tool's own commands are on, and which are off. Press Manage to see the full list, search it by name or by what a command does, and filter it to member commands, staff commands or the ones turned off. Each row shows who uses the command and whether it works in a ticket or any channel. Switch one off and anyone who runs it gets a private Command Turned Off reply that only they can see, saying it's turned off in this server. Changes apply within seconds. Turn all on under the list switches every command back on at once.
A turned off command also drops out of the list of commands that AI auto-replies are allowed to suggest, so the AI won't tell a member to use it. If you made a custom command with the same name, such as your own /new, your command keeps running and the AI can suggest that one.
Because the built-in commands are shared by every server, Discord still lists a turned off command in the / menu. To hide a command, or limit it to some roles or channels, open Discord's Server Settings, then Integrations, then Ticket Tool. Both settings work together.
/help, /setup, /setup-panel, /deploy-flow, /health and /debug always stay on, so you can't lock yourself out of fixing your setup. The Pro AI commands (/summarize, /draft, /translate) have their own switch, AI commands in Discord, on the AI Control page.
Flow variables from context commands
When a context command starts a flow, Ticket Tool passes the clicked user or message into the flow. A command that opens a ticket directly passes the same values to the intro message as {{responses.target_user}} and so on. See Variables for everything else a flow can use.
| Variable | Meaning |
|---|---|
{{options.target_user}} | Username of the right-clicked member, or of the message's author |
{{options.target_user_mention}} | Mention for that member |
{{options.target_user_id}} | Their user ID |
{{options.target_message_link}} | Link to the selected message |
{{options.target_message_content}} | Content from the selected message, when available |
Troubleshooting
| Problem | Check |
|---|---|
| Command does not appear | Give Discord time to sync, and check that the command is enabled. |
| A built-in command says it's turned off | Switch it back on under Built-in commands on the Commands page. |
| 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. |