Skip to content
20% off + 25% more tokensSee prices

BlogGuides

Discord Ticket Bot Commands: Every Command and Who Can Run It

Every AI Ticket Bot command, sorted by job: setup, panels, handling a ticket, staff, the AI and members. What each one does and who is allowed to run it.

Dani, Founder, AI Ticket Bot

7 min read

Most of what a Discord ticket bot does, it does through commands. Every one below is grouped by job, with what it does and who may run it. If you remember one, make it /help: it lists them inside Discord, by topic.

How to read "who can run it"

Who can run it

Anyone
Every member of the server. No permission needed
Manage Server
Discord's own permission. Administrator counts too, and it covers every staff permission
A staff permission, like Close tickets
A box ticked on a staff role in /staff roles. Manage Server always counts as well

Staff permissions give a moderator some powers without handing them the server. The permissions guide covers both kinds.

Which commands set up the server?

All of these need Manage Server.

CommandWhat it does
/setupBuilds a staff role, a ticket category, a panel channel and a live panel in one step. Only on a server with no panel yet
/panelCreate a panel, or open one to edit, post or delete it
/ticket settingsServer-wide switches: who can close, the Claim button, transcripts, asking for feedback and more
/ticket connectLets our AI answer inside tickets another ticket bot opens
/languageThe language the bot speaks in this server
/whitelabelThe bot's name, picture, banner and bio in your server (Premium)
/subscription buyA checkout link for Premium or Pro
/subscription infoThe server's plan, AI usage and what it unlocks

Most open a card with buttons and menus: run the command once, then press. The setup guide walks through the first ten minutes.

Which commands do staff use inside a ticket?

These run inside the ticket channel or thread.

CommandWhat it doesWho can run it
/ticket claimClaims the ticket. Run it again to release it, or on a colleague's claim to take it overClaim tickets
/ticket closeCloses it, with an optional reasonClose tickets, or the member who opened it
/ticket close-requestAsks the member if it can close, and closes on a timer if nobody answersClose tickets
/ticket transferMoves it to another category on the same panelMove tickets
/ticket peopleShows who is in it, and adds or removes someoneAdd people to tickets
/ticket replyPosts your message as "Staff", without your nameReply as Staff
/qr useSends a saved reply, or lets you browse them firstUse quick responses
/ticket pingDMs the member a button back to the ticket, with an optional noteWork on tickets
/ticket prioritySets Low, Normal, High or UrgentWork on tickets
/ticket renameGives the channel a clearer nameWork on tickets
/ticket aiTurns the AI on or off for this one ticketWork on tickets
/ticket inactivityShows what happens when it goes quiet, and pauses or resumes that (Premium)Anyone in the ticket can look. Pausing needs Close tickets

Three rules sit on top. A member can close their own ticket while a server setting allows it, which it does until you turn it off. A ticket claimed by a higher staff role cannot be closed by a lower one. Taking over a colleague's claim needs Manage Server or a top staff role at or above theirs. What claiming does and how a transfer works go deeper.

Sending a saved reply without your name needs Reply as Staff as well as Use quick responses.

Which commands find and measure tickets?

CommandWhat it doesWho can run it
/ticket searchFilters tickets by status, priority, opener, panel, and who claimed or closed them. Private to youWork on tickets
/ticket statsThe server's ticket numbers for a period. Free shows the last 7 daysSee stats
/staff statsA leaderboard per staff member: tickets handled, reply time, solve time (Premium)See stats
/ticket feedbacksThe ratings members left on closed ticketsSee stats

These run anywhere in the server. See stats lets a support lead read the numbers without Manage Server.

Which commands run the team?

CommandWhat it doesWho can run it
/staff rolesAdd a staff role, choose what it can do, or remove itManage Server
/blacklistBlock members or roles from tickets and the AI, see who is blocked, unblock themManage the blacklist
/qr manageAdd, edit, rename, duplicate or delete saved repliesManage Server

/staff roles decides every "who can run it" cell on this page. A trial moderator might get Work on tickets and Claim tickets and nothing else. Team structure has sensible splits.

Which commands control the AI?

CommandWhat it doesWho can run it
/ai overviewThe AI's home: status, model, memory, this month's usage, what it learned last, its FAQ channelsAnyone. Members only see whether the AI is ready
/ai askAsk the AI a question in the channel, to test what it knowsAsk the AI
/ai trainTeach it a fact, paste your docs, a link or filesTeach the AI
/ai improveTeach it from one closed ticket it did not solveTeach the AI
/ai memoryRead, change or delete what it knows. Delete all starts it overManage Server
/ai usageHow much of today's and this month's AI allowance is usedManage Server
/ai modelPick the model, or connect your own AI provider (Pro)Manage Server
/ai settingsWeb search, staying quiet once staff write, and the AI FAQ channelsManage Server

The four admin commands open /ai overview on that page. Teaching it for the first time? How to train an AI ticket bot is the order that works.

What commands can members use?

Anyone in the server can run these.

CommandWhat it does
/ticket openOpens a ticket by picking the panel and category, the same as pressing the button
/myticketsYour own tickets and their transcripts. In a DM with the bot, from every server
/helpEvery command by topic, or one command in detail
/ai overviewWhether the AI is ready in this server
/inviteLinks to add the bot, get support and open the dashboard
/aboutWhat the bot is, with live numbers
/pingWhether the bot, its database and its AI are answering
/voteVote for the bot and win free Premium time or AI tokens

Members also have /ticket close in their own ticket, unless you turned that off. Staff with Open tickets for others can name a member in /ticket open, which skips the questions and opening hours. Ticket history covers /mytickets.

Why does everyone see the staff commands?

Because Discord can only hide a command behind its own permissions. The bot hides /panel, /language, /whitelabel and /subscription from people without Manage Server. It cannot hide anything behind Claim tickets or See stats, because those belong to the bot. And /ticket, /ai, /staff and /qr are each one group to Discord, shown or hidden whole, while /ticket open and /ai overview are for everyone.

So a member who types /ticket sees claim, close and transfer. If they run one, they get a private reply naming what is missing, and nothing happens.

Your first hour, in commands

  1. Build the basics

    Run /setup. You get a panel, a category and a staff role

  2. Give your team powers

    Run /staff roles and tick what each role may do

  3. Teach the AI

    Run /ai train with your rules and common answers

  4. Test like a member

    Run /ticket open, ask something, read the reply

  5. Close it

    Run /ticket close and open the transcript from /mytickets

Day to day it is the same loop: members open, the AI answers first, staff step in with the commands above.

Where the commands stop

Good fit

  • Every command works on the Free plan unless marked Premium or Pro
  • Each command checks permissions on every run, whatever Discord shows

Not the right call

  • Members see most staff commands in the picker and are refused at runtime
  • /whitelabel, /staff stats and /ticket inactivity need Premium
  • Connecting your own AI provider in /ai model needs Pro

Some names people type do not exist. Adding or removing someone is /ticket people, not /ticket add. Ratings are /ticket feedbacks, not /feedback. Testing the AI is /ai ask, there is no /ai test. Wiping what it learned is Delete all inside /ai memory.

Frequently asked questions

Usually one to set it up, one to build panels, a set staff run inside a ticket (claim, close, transfer, add someone), a search and stats, and a few for members. AI Ticket Bot has 42 slash commands in total, including eight for its AI. Type /help in your server to see them all by topic.

Run /ticket open, pick the panel and then the category, and the ticket opens exactly as if you had pressed the panel's button. Anyone can run it. Staff with the Open tickets for others permission can also name a member to open a ticket on their behalf.

Discord can only hide a command behind its own permissions, such as Manage Server. Staff permissions like Claim tickets belong to the bot, so Discord shows those commands to everyone. A member who runs one gets a private message saying what is missing, and nothing happens to the ticket.

Run /staff roles, add the role your staff have, and tick what it may do: Work on tickets, Claim tickets, Close tickets, Move tickets and so on. Anyone with Manage Server can already run every command, so you only need this for staff who are not admins.

Staff only. It needs Manage Server, or a staff role with the Ask the AI permission. Every question spends the same AI allowance your tickets use, which is why it is not open to members. Members reach the AI by opening a ticket or asking in an AI FAQ channel.

Run /mytickets. It needs no permission and only ever shows tickets you opened yourself, with their transcripts. In a server it lists that server's tickets. In a direct message with the bot it lists every server you have opened one in.

See it on your own server.

Add the bot free, teach it a few of your most common answers, and watch it clear the repeat tickets on its own.

Free plan, no card. Premium is free for 14 days once your tickets are live.