Docs / Tickets / Commands / /ticket reopen
Moderation Server only

/ticket reopen

Reopen the current ticket

Usage

Generated
/ticket reopen

This command takes no options.

Who can run it

Generated
Discord defaultEvery member
Command Access presetModerator roles
Always allowedThe server owner and, by default, Administrators
Change itDashboard, Services, Tickets, Commands

The Moderation preset limits it to the roles you mark as moderators. Server owners and Administrators can always run it. How Command Access works.

What the bot needs

Generated

Tickets is granted these permissions by the invite link. A command that finds one missing replies privately with what it could not do and changes nothing.

Manage ChannelsView ChannelSend MessagesEmbed LinksRead Message HistoryManage RolesManage ThreadsCreate Private ThreadsSend Messages in Threads

Behaviour

Checked against the code 2026-10-08

Reopens a closed ticket in the current channel and gives the member their access back.

The bot first applies the server's Command Access rules for /ticket reopen and checks that Tickets is enabled ("❌ Tickets is not enabled for this server."). The command only works inside a ticket channel or thread ("No ticket found in this channel."). Only staff may reopen: Manage Server, the ticket's staff team or a role given access when the ticket opened. Others see "Only staff can reopen tickets." When the panel keeps the ticket actions to the claimer ("Taking a ticket" on 2 Answering), everyone except the claimer, the ticket's owner and server managers sees "Only @<claimer>, who claimed this ticket, or a server manager can do that." A ticket that is not closed answers "This ticket is already open."

The ticket becomes open again, with nobody holding its claim. In a text channel the member who opened it gets back the access the panel gives under "The member who opened it can" (1 Opening, "Who can open tickets, and what they can do"), and the channel moves to the panel's open tickets category when one is set. A channel renamed on claim or on close gets its open name back. In a thread the thread is unarchived and unlocked. The welcome message's buttons return to Claim, Close and Note. The bot then posts an embed "Ticket Reopened" with "Reopened by @you"; its text can be changed under "Messages when a ticket closes" on 3 Closing ("Ticket reopened"). If unarchiving a thread fails, you get a private note: "Reopened, but I could not unarchive the thread - check my Manage Threads permission."

A ticket by DM reopens the same way for your team, but its member is still not let into the channel. The bot tells them by DM instead: "The <server> team reopened ticket #<number>. You can answer here." What they write to the bot from then on goes into the reopened ticket when that is the only conversation it can be for. If they have another ticket by DM open, or share another server that takes tickets by DM, the bot asks "Which conversation is this for?" the next time they write, even in the middle of another conversation. It then remembers the answer for 15 minutes after their last message that went into that ticket. When the DM about the reopening cannot be delivered, the bot says why in the ticket.

Good to know

  • The Reopen button on a closed ticket's welcome message does the same thing and follows the same Command Access rules.
  • Reopening cancels a channel delete that "After it closes" on 3 Closing had scheduled, and the ticket's staff thread opens again.
  • The confirmation can take a few seconds because the bot changes channel permissions before it replies.
  • The reopening is recorded in the ticket's "Activity log" on its dashboard page.
YourBot docs Reference tables are generated from the code that is running. Ask in Discord Suggest a correction