Auto-closing a Discord ticket means the bot closes it on its own after a set number of hours of inactivity, so abandoned tickets don't sit open forever. A ticket where the member asked one question, got an answer, and never came back should not still be an open channel three weeks later. Noxyr can auto-close a ticket after a configurable number of inactive hours, and separately can close a ticket the moment its opener leaves the server. This guide covers both, what "inactive" actually measures, and where auto-close can go wrong.
Why open tickets pile up without it
Ticket channels rarely get closed by accident on purpose - they get closed by nobody remembering to. A member's issue gets resolved in the last reply, everyone moves on, and the channel just sits there. Multiply that by a few hundred tickets a month and two things happen: the ticket category fills with clutter, and the "open tickets" number on any dashboard stops meaning anything, because half of it is actually done.
Auto-close fixes the second problem without staff having to manually sweep the list. It doesn't replace someone actively closing a resolved ticket right away - that's still the better habit - but it catches everything that slips through.
Setting an inactivity timer
The setting is auto_close_hours (called Auto-close on the dashboard's Tickets page). Set it to a number of hours and any ticket with no new messages for that long closes automatically, using the same close flow as a manual close - a transcript is saved, the DM goes out if that's on, and the channel is archived or deleted per your other settings. Set it to 0 to turn it off entirely, which is the default.
- Via the dashboard: Tickets page → Auto-close (hours). Set to 0 to disable.
- Via Discord:
/ticketsetup auto_close_hours:<number>, from 0 up to 720 (30 days).
"Inactive" is measured from the last message in the channel, not from when the ticket was opened - a ticket that's been open five days but had a reply an hour ago is not close to auto-closing.
Picking a number that doesn't annoy people
There's no universally correct number, but a few starting points:
- Fast-moving support (orders, quick questions): 24-48 hours. If nobody's replied in two days, the conversation is over either way.
- Longer investigations (bug reports, disputes): 72-120 hours. Give staff room to come back with an answer without the channel vanishing mid-investigation.
- Anything under 12 hours risks closing a ticket while the member is asleep and about to reply. Auto-close is for abandonment, not for pressuring a quick response - that's a different setting (support hours, or a manual close request).
If you want a warning before the axe instead of a silent close, staff can use /close countdown for a specific ticket to give a heads-up with a delay - that's a manual per-ticket countdown, separate from the always-on inactivity timer.
Closing a ticket when the opener leaves
A related but separate setting closes a ticket immediately if the person who opened it leaves the server, rather than waiting for the inactivity timer. This matters for servers where a leave usually means the person got what they needed (or gave up) and isn't coming back to that ticket - it clears the category instead of letting a now-orphaned channel wait out the full auto-close window with nobody left to answer.
Turn it on from the dashboard's Tickets page as Close ticket when opener leaves. Leave it off if members in your server sometimes get kicked accidentally, or if being removed and reinvited is common enough that you'd rather keep the ticket open for when they're back.
What happens to the transcript
An auto-closed ticket goes through the exact same close process as a manual one: a transcript is saved and viewable on the web, posted to the transcript channel if configured, and DMed to the opener if that's enabled. The close reason on an auto-closed ticket records that it timed out, so when you're reviewing transcripts later you can tell an abandoned conversation apart from one staff actually finished. See our transcripts guide for what gets saved and how to find it again.
Common questions
Does auto-close warn the member first? No, the timer closes the ticket directly once it fires; there's no automatic "still there?" nudge before it. If you want that, have a staff member send one before the window is up, or use a manual close-request countdown for a specific ticket instead.
Will auto-close ignore a ticket that's just waiting on staff? No - the timer only looks at when the last message was sent, not who sent it. If staff haven't replied in 48 hours and that's your threshold, it closes regardless of who's at fault. Set the number with that in mind.
Can I auto-close some panels but not others? The inactivity timer is a server-wide setting in the current version, not per-panel. If you need very different timers for different ticket types, note it in the panel's welcome message so staff know to close those manually instead.
Does auto-close cost anything? No, it's part of Noxyr's free ticket system.
What's a safe number to start with? 48 hours is a reasonable default for most support servers - long enough to not catch anyone mid-conversation, short enough to actually clean things up.
Set your auto-close hours on the ticket bot page, or check the full setup in the Tickets docs.