Ticket Commands
Run these inside a ticket channel, except /new, which opens one. Support and Admin roles can use every command on this page; the few that also work for the ticket creator, or outside a ticket, say so in their row.
Ticket messages also carry buttons for the common actions, such as close,
claim or unclaim, and add or edit note. Run /help in Discord to see the
commands available in your server.
Open a ticket
| Command | What it does |
|---|---|
/new | Opens a new ticket from any channel. Anyone can run it. The category option lists the options on your deployed panels that the member's roles can open, so staff-only categories that sit on no panel never show. Picking one works like pressing that panel button: flows, forms and support hours all apply. With no category, it opens the only option straight away, or lists the choices. |
Already have a custom /new?
If your server made its own custom command called
new, it keeps running yours. Rename or delete it to use the built-in one.
Close and reopen
| Command | What it does |
|---|---|
/close | Closes the ticket, with an optional reason, and saves a transcript when the category is set to. The ticket creator can run it too when self-close is enabled. |
/close-request | Asks the opener to confirm the ticket can be closed. Takes an optional reason and auto_close_after (1 to 168 hours). Free on every plan. See Close requests. |
/reopen | Reopens a closed ticket. Leave ticket empty in the closed ticket's channel, or pass a number such as 123 or #123 from anywhere. |
/delete | Deletes the ticket and its channel after you confirm. A transcript is saved first, unless transcripts are turned off for the category. There is no undo. |
Close requests
When you think a ticket is done but want the opener to confirm, run /close-request instead of /close. The bot mentions the opener and posts two buttons:
- Accept & Close closes the ticket with the reason you gave. The close is recorded as done by whoever pressed the button, with your request noted on the ticket's history. Staff can press it too, for example when the opener confirmed in chat.
- Keep Open withdraws the request and edits the message to say the opener wants to keep the ticket open. If the ticket is claimed, the claimer is pinged.
Set auto_close_after to close the ticket if nobody answers within that many hours. The auto-close is recorded as done by Automation. Any message from the opener cancels the timer, and the buttons keep working. The timer survives a bot restart and is checked about once a minute, so a ticket can close up to a minute late.
A close request uses the normal close, so transcripts, close logs, webhooks and rating prompts behave as they do for /close. Sending a new request replaces the previous one and its timer.
You can also send a request from the close confirmation (staff see Request Close next to Confirm Close, carrying over any /close reason) or from the Close dialog in the dashboard ticket view. A ticket with a pending request shows a Close requested badge in the dashboard. The request message and its buttons also appear in the dashboard ticket view. The buttons there are for show only; the opener answers in Discord. Every button label and message can be translated on the Localization page.
People and ownership
| Command | What it does |
|---|---|
/add | Adds a user to the ticket. Bots cannot be added. The ticket creator can run it too when user-add is enabled. |
/remove | Removes a user from the ticket. The ticket creator cannot be removed. |
/claim | Marks you as the staff member handling the ticket, so the rest of the team can see it is taken. |
/unclaim | Releases the claim. The current claimant can run it, and Support staff can unclaim a ticket someone else claimed. |
/private | Hides the ticket from the category's support roles. Private tickets have to be enabled on the Features page first. Not available for thread tickets. |
/unprivate | Restores normal staff access by adding the category's support roles back. |
Who keeps access to a private ticket
The creator, staff already on the ticket, mandatory roles, the person who ran
/private and server administrators keep access. Staff with dashboard
transcript access can still read its transcript, so delete the transcript too
if the conversation must stay confidential.
Organize
| Command | What it does |
|---|---|
/priority | Sets the priority level to Low, Normal, High or Urgent. |
/rename | Gives the ticket a new name, and renames the Discord channel too when channel renaming is on. Discord allows about two channel renames every 10 minutes. |
/move | Moves the ticket to another category, picked with autocomplete. A thread ticket can only move to a category that uses the same thread channel. |
/ticket-info | Shows the status, category, priority, claim and participants in one embed. |
/note | Shows, adds or edits the internal staff note. Works even when a category hides the Add Note button. |
/rate | Sends the rating prompt to the ticket creator, the same one the Request Rating flow step sends. Each ticket can be rated once. |
Automations on a ticket
| Command | What it does |
|---|---|
/pause | Stops automations on this ticket. duration is 1 hour, 1 day, 1 week or Indefinitely (the default). Pick a rule to pause just that one rule. |
/resume | Lets automations run on the ticket again, or just the one rule you pick. Any inactivity clock restarts from the moment you resume. |
What a pause covers, and how to pause from the dashboard or from a rule, is in Exempting a single ticket.
Replies and records
| Command | What it does |
|---|---|
/reply | Sends your message under your brand name and avatar instead of your own. Pro, and anonymous replies have to be turned on. |
/canned | Posts a saved reply from your Canned Replies page, picked with autocomplete. No AI involved, and free on every plan. |
/kb | Sends a knowledge base article, picked with autocomplete. Outside a ticket, anyone can run it. |
/transcript | Generates an HTML transcript and sends it to the transcript channel, or to you if none is set. Includes attachments of supported types up to 5 MB. |
AI commands
The AI commands in Discord toggle on the AI Control page removes all of these from your server.
| Command | What it does |
|---|---|
/ask | Every plan. Answers a question from the Ticket Tool docs. On Community and Pro it also answers questions about this server: ticket counts, stats, settings, your knowledge base and Memory. Only you see the answer. |
/summarize | Pro. Posts an AI summary of the ticket. Respects the AI summary toggle on AI Control. |
/draft | Pro. Drafts a reply only you can see, steered by optional guidance, with Send, Edit and Discard buttons. Send as brand appears when anonymous replies are on. Respects the AI suggested reply toggle on AI Control. |
/translate | Pro. Translates text into a language, for example to answer in the customer's language. |
The Pro commands are only registered on Pro servers, so they do not appear in the command picker on other plans. Two message actions ship with them. Right-click a message in a ticket, open Apps, then pick:
- Reply with AI drafts a grounded reply to that specific message, with the same Send, Edit and Discard controls as
/draft. - Save to AI Memory saves a staff answer into the Memory Library as an approved entry.
See AI Assist for how grounding and drafts work.
Examples
/close reason:Issue resolved
/close-request reason:Refund sent auto_close_after:24
/reopen ticket:#123
/add user:@Username
/priority level:High
/pause duration:1 week
/pause rule:Auto-close after 3 days
/rename name:billing-question
/move category:Billing
/reply message:We are checking this now.
/kb article:Getting Started Guide
/ask question:How do refunds work?
/draft guidance:Ask for their order number