Discord Ticket Close Requests: Ask First, Close on a Timer

Every support queue collects the same pile. Tickets where the work is finished, the answer has been given, and nobody has pressed close because the last message in the channel is yours and it feels wrong to end a conversation the other person has not left.

So they sit. A week later somebody clears them in a batch, and a handful of those people were still waiting on something.

What is a close request on a Discord ticket bot?

It is a question with a countdown behind it. One command inside the ticket, two optional choices, and the bot handles the rest.

What lands in the ticket is a short card with two buttons and the deadline written as a live timestamp, so everybody reads it on their own clock. The same question goes to the member by direct message with a button that jumps back to the ticket, because a question posted in a channel somebody has stopped watching is not a question, it is a formality.

The two buttons underneath read "Yes, close it" and "No, I still need help", and the wording of the card itself is one of the per-panel messages you can rewrite, on any plan, if that is not how your server talks. What the bot always adds on top is the pair of buttons and the deadline, so a rewrite cannot accidentally remove the answer.

The direct message is best effort. If the member has left your server, or has messages from server members switched off, nothing is delivered and the countdown runs anyway, which is the same rule the closing message follows. The card inside the ticket is always there.

The four ways a close request ends

Two of them close the ticket and two of them do not, and each one is recorded differently.

Only one of those can win. The No button, a message arriving and the deadline expiring can genuinely land in the same second, and the bot settles which one counts before anything visible happens, so a ticket never closes twice and never closes after somebody has already said no.

The Yes route is worth reading twice. It runs the ordinary close, which means it is recorded as closed by the person who opened it rather than by you, and the reason you typed when you asked rides along as the close reason. Your records end up saying the member agreed, which is a different fact from you deciding.

Why silence closes the ticket

This is the part people push back on, so it is worth stating plainly: if nobody answers, the ticket closes.

The alternative sounds kinder and achieves nothing. A request that leaves the ticket open on silence returns you to exactly the state you were in before you sent it, which is a finished ticket sitting in the queue with nobody willing to end it. The deadline is the entire feature. Everything around it is manners.

That is also why it is not a substitute for reading the ticket first. A close request on work you have actually finished is a courtesy. The same request on a ticket your team never answered is a countdown to being ignored, and members read it exactly that way.

How long should you give them?

The ceiling is 7 days for a structural reason rather than an arbitrary one. Discord archives an idle thread after a week at most, so a request outliving that would leave a thread ticket waiting on an answer inside a thread that has already dropped out of the channel list.

The number you choose is a message whether you intend it or not. An hour is fine when the member is clearly still there and you are tidying up in front of them. A day is the default because it survives one night of sleep in any timezone. A week is for the person who told you they would come back after the weekend, and setting it that long is how you avoid closing on somebody who did exactly what they said they would.

Running the command again on the same ticket replaces the pending request and restarts the clock, and the old buttons stop working, so a member can never be looking at two live questions at once. Use that to extend a deadline rather than to nag.

Who can ask, and who can answer

Asking uses the same rule as closing: Manage Server, or a staff role you granted the close permission to. If somebody is already trusted to end a ticket outright, asking first is strictly gentler, so there is no separate permission to hand out. Discord ticket bot permissions covers how those roles are put together.

Answering is narrower than most people expect. Only the account that opened the ticket can press either button. A staff member who clicks is told so and pointed back at the ordinary close command, and so is anyone else who was pulled into the channel. That is deliberate: the whole value of asking is that one specific person agreed, and a helpful colleague pressing Yes on their behalf would quietly destroy it.

The buttons keep working for as long as the request is live, including across a restart of the bot, which matters when the deadline is a week away.

What it does to auto-close and to your records

While a request is pending, the inactivity system skips that ticket entirely. No nudge, no ping, no automatic close on the usual window. One quiet person should never receive two different messages about the same silence from the same bot, and two systems should never race to close one ticket. Auto-close and inactivity settings is the longer version of what gets paused.

The two are worth telling apart, because they solve different problems and they are not priced the same.

An expired request is not a quiet close either. It runs the same sequence every other close runs: the transcript is written, the member is sent it by direct message along with the button that lets them rate how it went, your log channel and any webhooks are told, and the channel goes. The expiry check runs on a timer rather than to the second, so the close lands a few minutes after the deadline rather than on it.

The question and its outcome are both captured into the ticket's own record as they happen, so the transcript the member receives shows that you asked and shows what they said. That is the difference between a close somebody can query later and a close they can only remember.

Your audit log separates the two closing routes, and that separation is the only feedback you will get on the number you have been picking. A row of tickets closed by their openers means people are reading the question and agreeing with it. A run of expired requests means they are not seeing it, or the deadline is too short, or you are sending them on tickets that were never finished.

Roughly half of all tickets across every server running this bot close with no human replying at all. Those are the ones that sit open longest, because there was never a staff member watching to end them, and they are the population a close request is really for. Current figures are at /api/stats/global if you would rather check than take our word for it.

When not to send one

Two more limits worth knowing before you build a habit around it. There is no way to send, accept or deny one from the web dashboard: it shows you a pending request, who asked, their reason and when it runs out, but the answer belongs to the member in Discord. And closing is still final here, as it is on nearly every Discord ticket bot, so a Yes cannot be taken back. How to close a Discord ticket covers what a close actually removes and why there is no reopen.

Used properly this is a small feature that quietly fixes a real thing. Tickets stop piling up at the end of the week, nobody has to decide whether ending a conversation is rude, and the person who opened it gets the last word on whether they are done.