What custom commands are

Prefix-style canned responses for your staff. Premium only.

Premium feature. Custom Commands let you set up prefix-style triggers your staff can type to send a saved response with one short command.

A custom command fires when someone types the trigger text in a Discord channel. For example, typing !faq in a ticket channel makes the bot post your saved FAQ response.

These are not slash commands

Ticket King's custom commands are prefix triggers. The bot watches for the trigger text in normal messages. They are not Discord slash commands.

What this means:

• They do not appear in the / slash-command picker.

• The trigger is exactly the text the user types. Many teams use a ! prefix, but any text works.

• The bot needs permission to read messages in the channel so it can see the trigger.

What you configure

On the dashboard, open Custom Commands in the sidebar. The page is Premium.

For each command you set:

• Command name, your reference for it. Up to 100 characters. It is lowercased and must be unique in your server. Users do not see it.

• Command trigger, the text users type, for example !faq.

• Response content, up to 2000 characters.

• Embeds, optional, up to 10.

• Link buttons, optional, up to 5 rows of up to 5 buttons.

• Permissions, either Allow All Staff or a list of specific roles.

• Options, the Enabled, Ticket Only, Delete Command Message, and Reply to Command Message toggles.

Creating a custom command

Limits

• Up to 25 custom commands per server.

• Free servers cannot create custom commands.

Use cases

Common things custom commands are used for:

• FAQ replies. A staff member types !faq.refund and the bot posts your standard refund answer.

• Quick greetings. !greet for a friendly hello in a new ticket.

• Wrong-ticket nudges. !wrongticket to redirect a member politely.

• Server rules. !rules reposts the rules in a ticket.

• Common troubleshooting steps. !restart for "have you tried restarting?".

Use cases

Ticket-only commands

A command can be set to Ticket Only, so it works only inside ticket channels. Ticket-only commands can also use ticket placeholders, such as {TICKET_NUMBER} and {USER}.

Use this when a command only makes sense inside a ticket and should not fire in general channels.

Permissions

Each command has a permissions section:

• Allow All Staff, so anyone with a server-wide support role can use the command.

• Or specific roles, chosen with a role selector.

A user does not need to be a server admin to use a command. Holding an allowed role is enough.

Related

Creating a custom commandEditing and deleting commandsUse casesLimits