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 lists a plan requirement. Each command says who can run it: /close is open to the ticket creator too, and the rest are for staff. Staff means anyone holding one of the staff roles selected in the dashboard under Staff → Staff roles.
Every command on this page must be run inside a ticket channel (/add and /remove can also target a ticket you have access to 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. After a team transfer, staff must be on the receiving team.
- If Only staff can close is on in the dashboard (Closing tickets → Closing rules), the creator cannot close their own ticket unless they are also staff or an administrator (TC002). On a ModMail server the switch decides whether the member can close their ticket from their DMs. Panels and ModMail each keep their own setting, and the switch changes the one for the mode the server uses.
inandsilentcannot be combined (TC018).inonly works in ModMail tickets (TC017). Any new message from the customer or staff cancels the scheduled close. When the time comes, the ticket closes with steps 2 to 5 below, using the same settings as closing it straight away.
What happens, in order:
- Unless Close without asking first is on in the dashboard (Closing tickets → Closing rules), 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, if After closing is set to Delete the channel, a deletion notice is posted and the channel is deleted 5 seconds later). - The creator receives a DM with the close notice if Message the member is on, for panel and ModMail tickets alike. Changing the wording of the close DM on Messages does not turn it on.
silent:Trueskips this DM. - A transcript is generated if the Transcripts block (Closing tickets → Transcripts) is on, and posted in the transcripts channel, or in the logs channel when there is none (before the channel is deleted, when it is set to be deleted). The post carries the transcript file and a View online button that opens it in the browser for those allowed to read it online. The ticket log channel receives an entry, and any configured webhooks fire.
If the transcript cannot be posted, for example because the server has neither a transcripts channel nor a logs channel, a channel set to be deleted is kept instead, so the conversation is not lost. Set the channels under General → Where the bot posts.
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; the ticket was transferred to a team you are not on; 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 |
/escalate
Transfer an open channel ticket to another support team. The ticket number, channel and conversation stay the same.
- The bot owner adds Escalation destinations under Staff → Staff roles: a team name, receiving staff roles, optional destination category, and the roles allowed to transfer there. Leave the allowed roles empty to allow any staff member who can access the ticket.
- Run
/escalateinside the ticket and choose a team, then submit the required reason. The menu lists only the teams you are allowed to send the ticket to, and never the team that already has it. The dashboard has the same action in the ticket's More menu. - The receiving team gets access to the full conversation and the reason. A notice in the ticket names the team, who transferred it and why, mentions the team's roles, and has a Claim button. The current claim is released so the new team can claim it.
Requires Basic or higher and a regular channel ticket. Threads and ModMail are not supported. The bot needs Manage Channels and Manage Roles, as well as access to the ticket and destination category.
By default, the previous team's managed role access is replaced. Enable Keep the previous team on a destination to retain it. Explicit participants and Discord administrators retain their access, but only the receiving team can claim, close or reopen the ticket or accept or deny its application. Dashboard access remains a separate server-wide setting. Transferred tickets keep their team on reopening, and automatic sorting does not reroute them.
If teams are set up but none of them is open to you (or the only one is the ticket's current team), /escalate answers with TC011 "There is no other team you can transfer this ticket to." When no team is set up at all, it asks you to have the bot owner configure them.
This team transfer is separate from Atlas's Talk to Staff button and the AI/SLA escalation queue.
/reopen
Reopen a closed ticket. Has no options.
/reopenWho can run it: staff (the server owner and administrators count as staff). After a team transfer, staff must be on the receiving team. A ticket creator who is not staff cannot reopen their ticket; they ask staff instead. ModMail tickets cannot be reopened; the member's next DM to the bot opens a new ticket.
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 staff, or the ticket was transferred to a team you are not on |
| TC011 | The server is not set up with this bot |
| TC015 | The ticket is already open |
| TC017 | The channel is not a ticket |
| TC018 | The ticket is a ModMail ticket, which cannot be reopened |
| 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. After a team transfer, only staff on the receiving team can claim the ticket.
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. With Claim mark in channel names on, the channel name gets a 👤 in front. - If exclusive claims are enabled for the server, other staff lose access to the channel until it is unclaimed. The Claim button asks you to confirm first;
/claimclaims straight away, and its reply says other users were removed. Thread tickets and ModMail tickets are not affected: every staff member keeps access. - The reply shown only to you has a Draft a reply button on Pro and Enterprise when Atlas and the AI Help drafts card are on and Atlas is not kept away from the ticket. It opens an AI Help draft for the ticket.
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, or the ticket was transferred to a team you are not on |
| TC015 | The ticket is already claimed (by you or someone else), 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 👤 claim mark (if your server uses it) leaves the channel name, 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.
With Auto-unclaim on, the bot releases a claim the same way when the member has waited too long for a staff reply.
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. You are offered the open tickets you have access to; type a ticket number to find an older one |
Provide exactly one of user or role.
Who can run it: staff. A ticket creator who is not staff cannot add people to their own ticket. With the ticket option, staff need access to that ticket: one closed to them by an exclusive claim, a button's Allowed staff roles, or a team transfer answers TC002. Server owners and administrators are not limited by this.
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 staff, the ticket you named is closed to you, 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. You are offered the open tickets you have access to; type a ticket number to find an older one |
Provide exactly one of user or role.
Who can run it: staff. A ticket creator who is not staff cannot remove anyone from their ticket. With the ticket option, staff need access to that ticket: one closed to them by an exclusive claim, a button's Allowed staff roles, or a team transfer answers TC002. Server owners and administrators are not limited by this.
What happens: the user or role loses view and send permissions on the channel, and a notice is posted in the ticket, even when you ran the command from another channel with the ticket option. You get a private confirmation.
In a ModMail ticket, the member who opened it cannot be removed: they never had access to the staff channel and write from their DMs, so /remove refuses with TC018. Close the ticket instead, or block them in Opening tickets → Who can open tickets.
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 (Supervisor roles under Staff → Claiming 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. In a ModMail ticket the creator cannot be removed.
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 staff, the ticket you named is closed to you, 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 |
| TC018 | The target is the member who opened a ModMail ticket |
/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: staff. A ticket creator who is not staff cannot rename their ticket.
What happens: the channel becomes name-XXXX, where XXXX is the original ticket number, so any name works, including words like support or staff. Pin, claim, and priority markers in front of the name are kept.
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 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. The buttons work for 7 days. After that, or once the ticket has been reopened since the request, the creator sees TC015 and you can send a new request.
- If they close it, the normal close flow runs (rename, move, transcript, DM).
In a ModMail ticket, the card is sent to the member's DMs instead, because they cannot see the staff channel, and you get a private confirmation that it was sent. When they close the ticket from their DMs, the usual ModMail close runs and the closing DM replaces the card. When they keep it open, the card is removed from their DMs and a notice in the staff channel tells you. If the member's DMs are closed, nothing is sent and you see TC002.
Example
/closerequest reason:Your issue looks resolved. Please confirm.Errors you can see
| Code | When |
|---|---|
| TC002 | You are not staff, a non-creator pressed the answer buttons, or (ModMail) the member's DMs are closed |
| TC015 | The ticket is already closed or not in the open state, or (creator) the request is more than 7 days old or the ticket was reopened since |
| TC017 | The channel is not a ticket |
Common questions
Why can't I close my own ticket? The server has Only staff can close turned on. 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 After closing is set to Delete the channel and the channel is already gone, the ticket cannot be reopened, but its transcript is still in the transcripts channel (or the logs channel) if Transcripts was on.
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 (Closing tickets → Auto-close and reminders) 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.
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