DocsTickets
Tickets
Open, claim, move, close and search tickets. What your staff use every day.
22 commands. Tap one to open it.
- Every plan
Open a new ticket from a panel, or open one on a member's behalf (staff).
Options
paneltextrequiredWhich ticket panel to open from
Suggested as you type: published panels in this server
categorytextrequiredCategory within that panel
Suggested as you type: categories of the chosen panel
open_formemberoptionalStaff only: open the ticket on behalf of this member
Who can use it
- Anyone in the server
Opening a ticket for yourself needs a published panel and no active block. Opening one for someone else needs Manage Server, or a staff role that can claim or close.
What happens
A confirmation only you can see, with a button that jumps to the new ticket.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
Good to know
There is no limit on how many tickets a server can have, or on how many one member opens over time. The only limit is how many tickets one member can have open at the same time on one panel, which you set in /panel edit up to what the plan allows. Closing a ticket frees the slot right away.
When it says no
- You are blocked from opening tickets here
- The panel is not published
- You already have as many tickets open on this panel as one member is allowed at a time
- The category is full: Discord allows 50 channels in one category, and Premium can clone it automatically
- The bot cannot create channels in that category
- Every plan
Close the current ticket and generate a transcript.
Options
reasontextoptionalOptional close reason recorded on the transcript
Who can use it
- Inside a ticket
The person who opened the ticket can close it too, unless you turned that off in /ticket settings. Staff who can close, and anyone with Manage Server, always can.
What happens
A closing notice in the ticket, then the transcript is sent to the opener by DM and the channel is deleted.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
When it says no
- You are not in a ticket
- The ticket is already closed
- Members are not allowed to close their own tickets here
- Every plan
Ask the opener whether the ticket can be closed, and close it on a timer if nobody answers.
Options
hoursnumberoptionalHow long the opener has to answer before it closes itself (1 to 168, default 24)
reasontextoptionalWhy you want to close it, shown to the opener (optional, max 500 characters)
Who can use it
- Staff who can close
- Inside a ticket
Same rule as /ticket close: staff who can close, or Manage Server. Only the person who opened the ticket can answer.
What happens
The bot posts a Yes / No question in the ticket and DMs the opener a button that jumps to it. You get a private confirmation.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
Good to know
A pending request ends in one of four ways, and only one can win: the opener accepts and the ticket closes normally, they deny it and it stays open, they send any new message and the request is cancelled because they clearly still need help, or the deadline passes and the ticket closes itself. While a request is pending the inactivity timer leaves the ticket alone, so one quiet person never gets two different messages about the same silence. Running it again replaces the pending request and moves the deadline, and the Accept and Deny buttons still work after the bot restarts. Free on every plan, and you can rewrite the message per panel.
When it says no
- You are not in a ticket
- The ticket is already closed
- The ticket belongs to a connected bot
- A web chat with no Discord account, so there is nobody to ask
- Hours must be between 1 and 168
- The bot could not post in the channel, so nothing was scheduled
- Every plan
Claim the ticket so your team knows you have it. Run it again to unclaim.
Who can use it
- Staff who can claim
- Inside a ticket
To unclaim a ticket someone else claimed, your highest role must be at least as high as theirs, or you need Manage Server.
What happens
In a channel ticket, the channel moves to your claimed category. In a thread ticket nothing moves. Either way the buttons switch to Unclaim and a notice is posted in the ticket.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
When it says no
- Someone else already claimed it
- You are not in a ticket
- You cannot unclaim it: the person who claimed it outranks you
- Every plan
Move this ticket to a different category on the same panel.
Options
category_nametextrequiredPick a destination category
Suggested as you type: categories of the current panel
Who can use it
- Staff who can transfer
- Inside a ticket
What happens
The channel is renamed and moved, a notice is posted in the ticket, and the change shows in the audit log.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
When it says no
- That category is full (50 channels)
- The ticket is already in that category
- You are not in a ticket
- Every plan
Reply in the ticket as "Staff", without showing your name.
Options
messagetextrequiredThe message to send to the ticket opener as "Staff" (max 1900 characters)
Who can use it
- Staff who can claim or close
- Inside a ticket
What happens
You get a private confirmation and the bot posts your message in the ticket as "Staff: your text". The transcript shows it as Staff too, but the reply still counts as your work in the staff statistics. If the AI pauses when staff step in, it says a staff member joined without naming you.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
When it says no
- You are not in a ticket
- The ticket is closed
- You are not staff here: it needs Manage Server, or a role that can claim or close
- The bot cannot send messages in this channel
- Every plan
Add a user to this ticket so they can see / message in it.
Options
usermemberrequiredThe user to grant access to this ticket
Who can use it
- Staff who can claim or close
- Inside a ticket
What happens
The person can now see and write in the ticket. A confirmation is posted in the ticket and they get a DM with a jump button.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
When it says no
- That person opened the ticket, so they already have access
- That is a bot
- You are not in a ticket
- Every plan
Remove a previously-added user from this ticket.
Options
usermemberrequiredThe user to remove from this ticket
Who can use it
- Staff who can claim or close
- Inside a ticket
What happens
Their access is removed and they get a DM saying so.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
When it says no
- That person opened the ticket
- You are not in a ticket
- Every plan
DM the ticket opener a jump-back button (with an optional note).
Options
notetextoptionalOptional short message that appears in the DM
Who can use it
- Staff who can claim or close
- Inside a ticket
What happens
You get a private confirmation. The opener gets a DM with a jump button, or you are told their DMs are closed.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Once a minute per ticket
When it says no
- The opener has DMs turned off
- You are not in a ticket
- Every plan
Set this ticket's priority level (low / normal / high).
Options
levelpick onerequiredPriority level
Low, Normal, High
Who can use it
- Staff who can claim or close
- Inside a ticket
What happens
A private confirmation. The priority shows on the ticket from then on.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
When it says no
- You are not in a ticket
- Every plan
Give this ticket a clearer name, for example urgent-payment-bug.
Options
nametextrequiredThe new name for this ticket (1 to 100 characters)
Who can use it
- Staff who can claim or close
- Inside a ticket
Staff who can claim or close, or Manage Server. There is no separate rename permission.
What happens
The channel or thread is renamed, a short notice is posted in the ticket, and you get a private confirmation. The new name shows on the dashboard and in the transcript too.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
Good to know
Discord is renamed first and whatever name it settles on is what gets recorded, so the dashboard never shows a name the channel does not actually have. Discord allows about two renames per channel every 10 minutes; hitting that gives a "try again shortly" message rather than a hang, and the cooldown here is deliberately gentle so a typo can be fixed.
When it says no
- You are not in a ticket
- The ticket is closed
- You are not staff here
- The name has no usable characters, for example only emoji
- Renamed too recently: Discord allows about two renames every ten minutes
- The bot is missing Manage Channels
- Every plan
Turn five server-wide ticket behaviours on or off: who can close, the Claim button, auto-close when the opener leaves, transcripts, and cloning a full category.
Who can use it
- Manage Server
What happens
A form with five Yes / No choices. A choice your plan does not include is skipped and the rest is saved; the reply tells you which one.
Plan and limits
- Plan
- Works on every plan; the clone-category choice needs Premium.
- How often
- Up to 5 times a minute per person
Good to know
The per-member open-ticket limit is not here: it is per panel, set in /panel edit under Ticket limit, and capped by your plan. Clone category when full needs Premium or above; the other four are free on every plan. There is a sixth server-wide ticket setting, protection against ticket sniping in DMs, which has no command and is set on the dashboard.
When it says no
- You need Manage Server
- Every plan
Connect the AI to another ticket bot you already use, so it answers inside the tickets that bot opens. Run it again on the same bot to disconnect.
Options
botmemberrequiredThe other ticket bot to connect (run again on the same bot to disconnect). Must be a bot account and not our own bot.
Who can use it
- Manage Server
What happens
A private confirmation. On connect it warns you if the bot is missing View Audit Log, which it needs to notice which bot created a channel. The bot also has to be able to see and write inside the other bot’s ticket channels; if it cannot, you get a DM saying what to grant when the first ticket opens.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
Good to know
External tickets count toward your totals and use your AI settings and token budget, but they store no messages, no transcript and no staff activity, and closing stays with the other bot. A staff message pauses the AI there the same way it does anywhere else. If our bot cannot see or write in the channels the other bot creates, the AI cannot answer anyone in them, so we DM whoever ran this command with the exact permissions to grant. One DM per connected bot, not per ticket, and it resets once access works, so a permission that breaks again later is reported again.
When it says no
- You need Manage Server
- That is not a bot
- You cannot connect the bot to itself
- Every plan, more on paid
Server-wide ticket statistics for a chosen window.
Options
periodpick oneoptionalTime window (Free plans only see Last 7 days)
Today, Last 7 days, Last 30 days, Last year, All time
Default: last 7 days
paneltextoptionalRestrict stats to one panel
Suggested as you type: panel names
Who can use it
- Manage Server
What happens
A card only you can see: ticket counts, response times and the AI block on Premium and up. On Free the AI block is replaced by what Premium would add. An empty window shows an empty state, not a wall of zeros.
Plan and limits
- Plan
- Works on every plan; the limit depends on it. Free (the last 7 days only) / Premium+ (every window + AI metrics).
- How often
- Up to 10 times a minute per person
When it says no
- That period needs Premium
- Every plan
Search this server’s tickets by status, priority, opener, panel, source and more.
Options
periodpick oneoptionalTime window
Today, Last 7 days, Last 30 days, Last year, All time
Default: last 30 days
statuspick oneoptionalFilter by current status
Open, Claimed, Closed
prioritypick oneoptionalFilter by priority
Low, Normal, High
paneltextoptionalFilter by panel name
Suggested as you type: panel names
usermemberoptionalTickets opened by this user
claimed_bymemberoptionalTickets claimed by this user
closed_bymemberoptionalTickets closed by this user
sourcepick oneoptionalWhere the ticket came from
Discord, Web chat, Another bot
aipick oneoptionalFilter by what the AI did on the ticket
AI replied, AI never replied, Closed without staff, Handed over to staff
has_transcriptpick oneoptionalOnly show tickets that have a saved transcript
Yes, No
texttextoptionalSearch text in the close reason
Who can use it
- Staff who can claim or close, or Manage Server
Staff who can claim or close, or Manage Server. Results are private to you and last ten minutes.
What happens
A page of results with a dropdown to open one ticket. Each row shows the channel name, status, priority, panel, opener and age; web chats and connected-bot tickets are marked. Opening a ticket shows more, including a pending close request and whether auto-close is paused.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 10 times a minute per person
Good to know
Every status, priority and source reads as a word in your server's language. The panel filter is capped by your plan: a panel hidden by a downgrade is not offered and is not accepted if you type it, and it answers exactly like a panel that does not exist. Tickets that came from a hidden panel still show in unfiltered results, because history is never hidden. An anonymous web chat has no Discord opener, so it reads as “Website visitor”.
When it says no
- You are not staff here
- No panel with that name
- Every plan
See the tickets you opened yourself, and open their transcripts.
Who can use it
- Anyone in the server
No permission needed. It only ever shows tickets you opened yourself.
What happens
A private list, one row per ticket with its name, status and date. Pick one to see more: a button to the ticket while it is open, and a button to the transcript once it has one.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
Good to know
The only ticket command that works in a DM, and the only one anyone can run. Inside a server it lists your tickets there; in a DM with the bot it lists your tickets across every server. It shows what you already lived through: which server, the channel name, the panel and category you picked, when it opened and closed, and the transcript. It deliberately does not show who claimed or closed it, the staff close reason, or the priority, because those are staff notes and a server may be running anonymous staff replies. A transcript that has aged out says so instead of linking to a dead page.
- Every plan
Browse the star ratings members left when their tickets closed.
Options
ratingpick oneoptionalOnly show ratings with this many stars
⭐ 1 star, ⭐⭐ 2 stars, ⭐⭐⭐ 3 stars, ⭐⭐⭐⭐ 4 stars, ⭐⭐⭐⭐⭐ 5 stars
Who can use it
- Manage Server
Manage Server only, because feedback can be candid. Members can always leave a rating, on every plan.
What happens
A private list, five per page, with the total and the average at the top. Each entry shows the stars, the ticket, who opened it, their note and the date.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 10 times a minute per person
- Premium and up
Pause this ticket's inactivity auto-close timer.
Options
reasontextoptionalWhy you're pausing the timer
Who can use it
- Staff who can claim or close
- Inside a ticket
What happens
A private confirmation and a notice in the ticket. The auto-close timer skips this ticket until you resume it.
Plan and limits
- Plan
- Needs Premium, Pro or Enterprise. Your first published panel starts 14 days of Premium free.
- How often
- Up to 5 times a minute per person
When it says no
- Your plan does not include smart inactivity
- You are not in a ticket
- Premium and up
Resume this ticket's inactivity auto-close timer.
Who can use it
- Staff who can claim or close
- Inside a ticket
What happens
A private confirmation and a notice in the ticket. The timer counts again.
Plan and limits
- Plan
- Needs Premium, Pro or Enterprise. Your first published panel starts 14 days of Premium free.
- How often
- Up to 5 times a minute per person
When it says no
- You are not in a ticket
- Premium and up
Show this ticket's inactivity timer (paused state, time until warn / close).
Who can use it
- Inside a ticket
What happens
A private card with the timer and the exact times it would nudge and close, shown in your own time zone.
Plan and limits
- Plan
- Needs Premium, Pro or Enterprise. Your first published panel starts 14 days of Premium free.
- How often
- Up to 10 times a minute per person
When it says no
- You are not in a ticket
- Every plan
Re-enable the AI on this ticket after a previous disable (staff only).
Who can use it
- Staff who can claim or close
- Inside a ticket
What happens
A notice in the ticket. The AI answers again from the opener’s next message.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
When it says no
- The AI is already on
- You are not in a ticket
- The server is out of AI tokens for now
- Every plan
Disable the AI on this ticket (staff only).
Who can use it
- Staff who can claim or close
- Inside a ticket
What happens
A notice in the ticket. The AI stops answering.
Plan and limits
- Plan
- Works on every plan, Free included.
- How often
- Up to 5 times a minute per person
When it says no
- The AI is already off
- You are not in a ticket