Closes the ticket in the current channel. It opens a small form first, then locks the channel, saves the transcript and posts to the log channel when one is set.
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 its panel lets them: the panel's own "Who can close" on 3 Closing, else the switch for every panel there (on by default). Everyone else sees "You don't have permission to close this ticket."
Two more rules can apply. When the panel has "Only the claimer can use the ticket actions" on ("Taking a ticket" on 2 Answering) and the ticket is claimed, only the claimer, the member who opened the ticket and server managers may close it; anyone else sees "Only @<claimer>, who claimed this ticket, or a server manager can do that." When "Staff must claim a ticket before closing it" is on (3 Closing, "Who can close"), staff closing someone else's ticket need it claimed first, by anyone: "You must claim this ticket before closing it. Click the Claim button first." The member who opened the ticket never needs a claim.
Next comes a form titled "Close Ticket" with one field, "Reason (optional)", up to 500 characters. When the ticket's panel asks for a reason to close (3 Closing), the field is "Reason" and must be filled, and a reason of only spaces is refused privately: "Tickets from this panel need a reason to close. Try again and add one." Submitting it closes the ticket and posts an embed "⛔ Ticket Closed" with "Closed by @you" and the reason when one was given. Its text can be changed under "Messages when a ticket closes" on 3 Closing. 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 Reopen, plus 🗑️ Delete and 📜 Transcript for staff. In a text channel the opener loses access, or keeps read-only access when the panel says so under "When the ticket closes" (1 Opening, "Who can open tickets, and what they can do"). The member of a ticket by DM was never in the channel, and that choice does not let them in. Access your team gave them by hand with /ticket add is taken away. @everyone is denied view and send, and the channel moves to the panel's closed tickets category when one is set. A panel with a closed name (1 Opening, "Closed tickets and pinning") renames the channel, and the open name comes back if the ticket reopens. In a thread the thread is archived and locked and keeps its name. A staff thread (the panel's "Staff thread" card on 2 Answering) is archived and locked too. 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 bot saves a transcript of the newest 1000 messages to the dashboard's History page. The log channel gets a transcript card 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. The card carries the transcript as a web page file, and a "View transcript" button that opens it on the dashboard (staff need dashboard access). The file is never attached in a channel @everyone can see. Such a channel, a file over Discord's upload limit or a channel where the bot cannot attach files gets the button only and the card says why; 3 Closing can turn the file off. Every close posts this same card: from the dashboard, a close request, an automation or a member leaving too. When the ticket's panel keeps no transcripts (3 Closing), nothing is saved and the card says "No transcript is kept for this panel." with no file and no button. Files kept from the ticket (up to 10 files and 8 MB per ticket) go to a separate post in the same channel. The log channel is the panel's own ("This panel's log channel", on Settings with the panel picked under "Settings for"), else the server's, set under "Logs" on Settings. When "Post transcripts in" on 3 Closing names another channel, the card and the files go there and the log channel gets a shorter close summary with the View transcript button instead. Both posts are on by default; switch off Ticket closed or Transcript saved under "What gets logged" on Settings to stop them.
What the member sees: a DM titled "How was your support in <server>?" saying "Your ticket <title> has been closed." with 5 star buttons to rate the support, and a footer saying it is a one-time prompt shown once per ticket. It says who closed the ticket and the reason, and has a "View your ticket" button to the member's own copy when a transcript was kept. It is skipped when the server turned off "Ask members to rate their support", when the member turned ticket DMs off with /ticket dms off or when they already rated. While ratings are off, 3 Closing's "Send a close notice while ratings are off" sends a short DM instead: who closed the ticket, the reason and the link to their copy. With "Send the member a copy" on (3 Closing, "Transcripts"), the member also receives the transcript file and the ticket's files by DM, without the staff notes or the activity log.
A ticket by DM, one the member opened by writing to the bot, differs here, because the member cannot see the channel. The bot always sends them one close message by DM. It is the rating DM when ratings are on, the member has not rated this ticket yet and has not run /ticket dms off. In every other case it is the close notice, whatever "Send a close notice while ratings are off" and /ticket dms off say. While the server still takes tickets by DM and the member is still in the server, the message ends with "Write here again to open a new ticket." When they do, the bot asks its question again, as it did the first time. A ticket by DM that closes because its channel was deleted by hand sends a shorter message: that the ticket was closed, with no star buttons and no link. The transcript DM, when it is on, holds the conversation only: the member's own messages, the replies sent to them and the files on those messages.
The member of a ticket by DM closes it from their direct messages. Where the panel lets members close, the bot's receipt there has a "Close ticket" button. It opens a pop-up titled "Close ticket" with one field, "Reason (optional)", or "Reason" when the panel asks for a reason to close. Sending it in closes the ticket. Your team sees the same close message, transcript and log post as after any close, and the receipt changes to "Ticket #<number> with the <server> team is closed." Where only staff may close, the receipt has no button.
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.
- /ticket delete closes an open ticket and deletes its channel in one step.
- 3 Closing decides what happens to the channel afterwards, under "After it closes": "keep its channel" (the default), "delete its channel after a wait" (1 to 10080 minutes, which is 7 days) or "delete its channel right away". The channel is only deleted once the ticket has a saved transcript, and reopening the ticket before then keeps it.
- Kept channels are still deleted after the number of days on the line "Delete kept channels" in the same card (0 keeps them).