Marks the current ticket for closing with a countdown. If the member who opened it does not reply before the deadline, the ticket closes on its own.
The bot first applies the server's Command Access rules for /ticket closerequest 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 request a close: Manage Server, the ticket's staff team or a role given access when the ticket opened. Others see "Only staff can request close." 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 closed ticket answers "This ticket is already closed."
The hours option defaults to 24 and is kept between 1 and 168 (1 hour to 7 days). The ticket's status becomes Close Requested and the bot posts an embed "🔶 Close Requested" for everyone: "This ticket has been marked for closure by @you.", then "If no response is received, it will be automatically closed <in N hours> (<date and time>).", then "Reply in this ticket to keep it open." Its text can be changed under "Messages when a ticket closes" on 3 Closing ("Close request from staff"). Under it sit 2 buttons, "Close now" and "Keep it open".
What cancels it: a message from the member who opened the ticket, or that member pressing "Keep it open". After a message the bot posts "Close request cancelled: the ticket owner replied." After the button the 2 buttons disappear and the bot posts "✅ Close request cancelled: @member wants to keep this ticket open." Either way the ticket goes back to waiting on staff. Anyone else who presses "Keep it open" sees "Only the ticket owner can keep it open." Messages from staff or from other members do not cancel the countdown.
In a ticket by DM the member sees neither this message nor its buttons, so the bot also tells them by DM: "The <server> team is about to close ticket #<number>. It closes <when>. If you still need help, write here." A message they then write to the bot cancels the request when it goes into the ticket, as a reply in the channel does, and the bot posts the same "Close request cancelled: the ticket owner replied." in the ticket. When the bot first asks which conversation the message is for, the request is cancelled once they pick this ticket. When that DM cannot be delivered, the bot says why in the ticket, once for each reason.
"Close now" closes the ticket at once, exactly like /ticket close: the same Command Access rules, the same rules on who may close and the same reason form, where the reason stays optional even on a panel that asks for one.
What happens at the deadline: the bot checks every 2 minutes. Once the deadline has passed the ticket closes automatically, the same way a normal close ends: the channel is locked or archived, the ticket's transcript is on the dashboard's History page and the log channel gets the same card as any close when one is set.
Good to know
- 3 Closing can start the same countdown on its own under "Quiet tickets": it asks to close a ticket nobody has written in for the hours you set, then closes it a set number of hours later unless the member replies.
- An automation rule on the Automations page can start it too, with the action "start the close countdown", when the member has not answered staff or has left the server.
- Every close request, whichever of these started it, carries the same 2 buttons, and a message from the member cancels it the same way. In a ticket by DM the member is told about each of them by DM.
- /ticket close closes at once instead.
- The request is recorded in the ticket's "Activity log".