Discord Ticket Commands
Commands for the ticket lifecycle: closing, reopening, claiming, access control, and renaming
These commands run inside a ticket channel and control what happens to that ticket. They are available on every plan. Unless a command says otherwise, the ticket creator and staff can both use it; staff means anyone holding one of the staff roles selected in the dashboard.
Every command on this page must be run inside a ticket channel (/add and /remove can also target a ticket by ID from anywhere in the server). Running one elsewhere returns TC017.
/close
Close the current ticket.
/close [reason] [in] [silent]| Option | Type | Required | Allowed values | Default |
|---|---|---|---|---|
reason | Text | No | Up to 1000 characters | none |
in | Text | No | A delay such as 30m, 2h, or 1d (up to 32 characters). ModMail tickets only | close now |
silent | Boolean | No | True or False | False (the creator is notified) |
Who can run it: the ticket creator, staff, server administrators, and the bot owner.
- If Staff-only close is enabled in the dashboard, the creator cannot close their own ticket unless they are also staff or an administrator (TC002).
inandsilentcannot be combined (TC018).inonly works in ModMail tickets (TC017). Any new message from the customer or staff cancels the scheduled close.
What happens, in order:
- Unless Skip Close Confirmation is enabled, you see a confirmation card showing the ticket number, the reason, and whether silent mode is on. Confirm to continue.
- The ticket is marked closed and the creator loses the ability to send messages.
- The channel is renamed from
ticket-XXXXtoclosed-XXXXand moved to the closed tickets category (or deleted straight away if auto-delete is enabled). - The creator receives a DM with the close notice, unless
silent:Truewas used. - A transcript is generated and posted to the transcript channel if transcripts are enabled, the ticket log channel receives an entry, and any configured webhooks fire.
Examples
/close reason:Issue resolved
/close silent:True
/close in:2h reason:Closing if we hear nothing moreErrors you can see
| Code | When |
|---|---|
| TC002 | You are not the creator, staff, an administrator, or the bot owner; or staff-only close is enabled and you are the creator |
| TC015 | The ticket is already closed |
| TC017 | The channel is not a ticket, or in was used outside a ModMail ticket |
| TC012 | The in delay is not a valid format like 30m, 2h, or 1d |
| TC018 | in and silent were combined |
/reopen
Reopen a closed ticket. Has no options.
/reopenWho can run it: the ticket creator or staff (the server owner and administrators count as staff). ModMail tickets cannot be reopened this way; continue the conversation in the ModMail channel instead.
What happens:
- The ticket status returns to open.
- The channel is renamed from
closed-XXXXback toticket-XXXXand moved to the open tickets category. - The creator regains permission to send messages.
Reopening keeps the full conversation history. Nothing is deleted when a ticket is closed and reopened.
Errors you can see
| Code | When |
|---|---|
| TC002 | You are not the creator or staff |
| TC015 | The ticket is already open |
| TC017 | The channel is not a ticket, or the ticket is a ModMail ticket |
| TC005 | Discord refused to rename or move the channel; try again |
/claim
Claim the current ticket so other staff can see who is handling it. Has no options.
/claimWho can run it: staff only. You cannot claim a ticket you created yourself.
What happens:
- Your name is recorded as the handler, a claim card showing who claimed the ticket and when is posted in the channel, and the Claim button on the welcome message turns into Unclaim.
- The ticket shows as claimed in the dashboard and in
/claims. - If exclusive claims are enabled for the server, other staff lose access to the channel until it is unclaimed; the confirmation tells you when this applies.
A ticket can only be claimed by one staff member at a time. Use /unclaim to release it first.
Errors you can see
| Code | When |
|---|---|
| TC002 | You are not staff |
| TC015 | The ticket is already claimed (by you or someone else), you are the ticket creator, or the ticket is closed |
| TC017 | The channel is not a ticket |
/unclaim
Release the claim on the current ticket. Has no options.
/unclaimWho can run it: the staff member who claimed it, or any other staff member.
What happens: the claim is removed, the claim card is deleted, the Unclaim button on the welcome message turns back into Claim, and if exclusive claims were in effect the other staff members regain access. Clicking Unclaim on the welcome message does the same.
Errors you can see
| Code | When |
|---|---|
| TC002 | You are neither the claimer nor staff |
| TC015 | The ticket is not claimed, or it is closed |
| TC017 | The channel is not a ticket |
/add
Give a user or a role access to a ticket.
/add [user] [role] [ticket]| Option | Type | Required | Notes |
|---|---|---|---|
user | User (autocomplete) | No | The member to add. Pick a suggestion, or type a mention, a user ID, or their exact username or nickname |
role | Role | No | The role to add |
ticket | Ticket (autocomplete) | No | The ticket to add them to. Defaults to the current channel when run inside a ticket. Staff are offered every open ticket, anyone else only their own |
Provide exactly one of user or role.
Who can run it: the ticket creator or staff.
What happens: the user or role receives view and send permissions on the ticket channel. Adding a user also posts a notice in the channel.
On thread-style tickets, a user is added to the thread. Discord threads cannot hold role permissions, so adding a role adds every member who currently has it. Members who get the role later are not added; run /add again or add them individually.
Rules
- Bots and the
@everyonerole cannot be added. - Users or roles cannot be added to a closed ticket.
- On thread-style tickets, a role must have at least one member and at most 100.
- On ModMail tickets, only staff members and staff roles can be added.
Examples
/add user:@JohnDoe
/add role:@Billing Team
/add user:@JohnDoe ticket:0042Errors you can see
| Code | When |
|---|---|
| TC012 | Neither or both of user and role were given, or you tried to add a bot or @everyone |
| TC002 | You are not the creator or staff, the target is not staff on a ModMail ticket, or the bot lacks the permissions to change the ticket's access |
| TC004 | The user, role, or ticket was not found, or the role has no members (thread tickets) |
| TC015 | The ticket is closed, or the target already has access |
| TC017 | Run outside a ticket channel without the ticket option |
| TC018 | A role with more than 100 members was added to a thread ticket |
/remove
Remove a user or a role from a ticket.
/remove [user] [role] [ticket]| Option | Type | Required | Notes |
|---|---|---|---|
user | User (autocomplete) | No | The member to remove. Suggestions list the people who have access to the ticket; you can also type a mention, a user ID, or their exact username or nickname |
role | Role | No | The role to remove |
ticket | Ticket (autocomplete) | No | The ticket to remove them from. Defaults to the current channel when run inside a ticket. Staff are offered every open ticket, anyone else only their own |
Provide exactly one of user or role.
Who can run it: the ticket creator or staff.
What happens: the user or role loses view and send permissions on the channel, and a notice is posted.
On thread-style tickets, a user is taken out of the thread. Removing a role takes out every thread member who has it, except the ticket creator, staff, and supervisors.
Rules
- Members holding a supervisor role (configured in the dashboard) cannot be removed.
- Bots cannot be removed.
- While a ticket is exclusively claimed, the staff member who claimed it cannot be removed. Unclaim it first.
- The
@everyonerole cannot be removed. - Removing the ticket creator asks for a second confirmation.
Errors you can see
| Code | When |
|---|---|
| TC012 | Neither or both of user and role were given, or a bot or @everyone was targeted |
| TC002 | You are not the creator or staff, the target is a supervisor, or the bot lacks the permissions to change the ticket's access |
| TC004 | The user, role, or ticket was not found, or the target does not have access to this ticket |
| TC015 | The ticket is closed, or the target holds its exclusive claim |
| TC017 | Run outside a ticket channel without the ticket option |
/rename
Rename the current ticket channel while keeping its number.
/rename <name>| Option | Type | Required | Allowed values |
|---|---|---|---|
name | Text | Yes | Up to 80 characters. Converted to lowercase; anything other than letters, digits, and hyphens is removed |
Who can run it: the ticket creator or staff.
What happens: the channel becomes name-XXXX, where XXXX is the original ticket number.
Examples
/rename billing-issue
/rename vip-supportDiscord allows only two channel renames per channel every 10 minutes. A third rename within that window waits until the limit resets (TC001).
Errors you can see
| Code | When |
|---|---|
| TC012 | The name is empty, longer than 80 characters, or has no valid characters left after cleanup |
| TC002 | You are not the creator or staff, or the bot lacks Manage Threads for a thread ticket |
| TC015 | The ticket is closed |
| TC017 | The channel is not a ticket |
/closerequest
Ask the ticket creator to confirm their issue is resolved and close the ticket themselves.
/closerequest [reason]| Option | Type | Required | Allowed values |
|---|---|---|---|
reason | Text | No | Up to 1000 characters |
Who can run it: staff only.
What happens:
- A card is posted in the ticket asking the creator whether the issue is resolved, with your reason if you gave one.
- Only the creator can answer. They can close the ticket or keep it open.
- If they close it, the normal close flow runs (rename, move, transcript, DM).
Example
/closerequest reason:Your issue looks resolved. Please confirm.Errors you can see
| Code | When |
|---|---|
| TC002 | You are not staff, or a non-creator pressed the answer buttons |
| TC015 | The ticket is already closed or not in the open state |
| TC017 | The channel is not a ticket |
Common questions
Why can't I close my own ticket? The server has Staff-only close enabled. Ask a staff member to close it, or wait for them to send a close request you can accept.
I closed a ticket by mistake. Can I get it back?
Yes. Run /reopen in the closed channel. If auto-delete is enabled and the channel is already gone, the ticket cannot be reopened, but its transcript is still in the transcript channel if transcripts were enabled.
Does /close silent:True skip the transcript?
No. Silent only skips the DM to the creator. Transcripts, logs, and webhooks run as usual.
Can I close a ticket automatically after some time?
For ModMail tickets, /close in:2h schedules a close that any new activity cancels. For regular tickets, use auto-close in the dashboard or /auto-close, which closes tickets after a period of inactivity.
Why can't I add a role to this ticket?
On thread-style tickets, /add role adds the role's current members one by one, so it only works for roles with 1 to 100 members. For a larger role, add the individual members instead.
Why does /claim say I cannot claim my own ticket?
Claims are for staff handling someone else's request. If you opened the ticket, another staff member needs to claim it.
I renamed the channel but the name looks different from what I typed. Discord channel names are lowercase and allow only letters, digits, and hyphens. Spaces and other characters are removed, and the ticket number is appended automatically.
Join the support Discord and ask the team
Was this page helpful?
Last updated on