Docs / Tickets / Comandos / /ticket close
Moderation Server only

/ticket close

Close the current ticket

Usage

Generated
/ticket close

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

Comportamento

Checked against the code 2026-09-21

Closes the ticket in the current channel. It opens a small form first, then locks the channel, saves the transcript and posts to the ticket log channel.

The bot first applies the server's Command Access rules for /ticket close 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."). An already closed ticket answers "This ticket is already closed." Who may close: staff (Manage Server, the ticket's staff team, or a role given access when the ticket opened), and the member who opened the ticket when the Settings page switch "Allow users to close their own tickets" is on (it is on by default). Everyone else sees "You don't have permission to close this ticket." Staff who did not open the ticket also need the ticket to be claimed first, by anyone: "You must claim this ticket before closing it. Click the Claim button first."

Next comes a form titled "Close Ticket" with one optional field, "Reason (optional)", up to 500 characters. Submitting it closes the ticket and posts an embed "⛔ Ticket Closed" with "Closed by @you" and the reason when one was given. If someone else closed the ticket while the form was open: "This ticket is already closed."

What happens to the channel: the welcome message's buttons change to a single Reopen button. In a text channel the opener loses access, everyone else loses view and send, and the channel moves to the panel's closed tickets category when one is set. In a thread the thread is archived and locked. If a permission step fails the close still counts and you get a private note: "Closed, but I could not <what failed> - check my Manage Channels permission."

What staff see afterwards: the transcript is captured (up to 1000 messages) and saved to the dashboard Transcripts page. When a ticket log channel is set on the Settings page, the bot posts a transcript embed there for the ticket number, with the creator, status, priority, close reason, who closed it, when it opened, the first response time, up to 5 staff notes and up to 5 intake answers. Files kept from the ticket (up to 10 files and 8 MB per ticket) go to a separate post in the same channel.

What the member sees: a DM titled "How was your support in <server>?" saying "Your ticket <title> has been closed." with five star buttons to rate the support, and a footer saying it is a one-time prompt shown once per ticket. It is skipped when the member turned ticket DMs off with /ticket dms off or already rated. With the Settings page switch "DM the transcript to the member when their ticket closes" on, the member also receives the transcript file and the ticket's files by DM.

Good to know

  • The Close button on the welcome message does the same thing and follows the same Command Access rules.
  • /ticket reopen brings a closed ticket back.
  • /ticket closerequest closes with a countdown instead of at once.
  • Closed ticket channels are deleted after the number of days set in "Delete closed ticket channels after (days)" on the Settings page (default 7; 0 keeps them).
YourBot docs Reference tables are generated from the code that is running. Ask in Discord Suggest a correction