Auto-Close on User Leave
Close a member's open tickets automatically when they leave, are kicked, or are banned
When a member leaves your server, is kicked, or is banned, TicketCord can close every open ticket they created. Staff stop spending time on conversations that can no longer be answered, and the tickets go through your normal close flow (transcript, closed category, channel deletion) instead of sitting open forever.
It is a single switch, Also close when the member leaves, inside the Auto-close card of Closing tickets → Auto-close and reminders. It works separately from the inactivity timer on the same card.
Closing tickets when the member leaves needs the Basic plan or higher. Accounts that configured auto-close before it became a paid feature keep it under Grandfathered access. On Free the Auto-close card shows a Basic+ badge and cannot be turned on, and saving the setting returns "Auto-close requires a Basic, Pro, or Enterprise plan."
Setting up
Open Auto-close and reminders
Turn on the Auto-close card
The member-leave switch sits inside the Auto-close card, which only shows its settings while its own switch is on. Turning the card on also starts the inactivity timer at Close after 1440 minutes (1 day); set the time you want (15 minutes to 30 days).
Turn on the switch
Enable Also close when the member leaves ("Closes their tickets right away, including after a kick or ban.").
Save
Click Save changes or press Ctrl/⌘ + S. It applies to the next member who leaves.
Settings
| Setting | Allowed values | Default |
|---|---|---|
| Also close when the member leaves | on or off | off |
There is no delay, grace period, or per-category option. In Closing tickets → Auto-close and reminders the switch is only reachable while the Auto-close card is on, so the inactivity timer on the same card (15 minutes to 30 days) is set up alongside it. The two act separately: the timer closes quiet tickets, and this switch closes a departing member's tickets. Turning the Auto-close card off turns this switch off too.
What happens
- The member leaves, is kicked, or is banned.
- The bot waits about 1.5 seconds. Discord reports a kick and a voluntary leave identically, and a ban arrives as a separate event; the short wait lets the bot tell a ban apart from a leave so the notice is accurate.
- Every open ticket created by that member on that server is closed. The closer is recorded as the system, not a staff member, so nobody gets resolution credit for it in analytics.
- A system card is posted in each ticket stating why it was closed, with the member's display name (no ping) and the ticket number:
- Left: grey, "user left" notice
- Banned: red, "user banned" notice
- The member's access to the channel is removed and the ticket is moved to your closed category, if you have one.
- Your close settings run as usual: the channel is deleted when After closing is set to Delete the channel in Closing tickets → Closing rules, and a transcript is posted (before any deletion) when Closing tickets → Transcripts is on, in the transcripts channel or, when there is none, the logs channel. Pinned tickets are never auto-deleted; the notice says so. If the transcript fails, a channel set to be deleted is normally kept; the exception is a ticket whose member access could not be removed, which is still deleted so the departed member cannot keep reading it.
Limits and gotchas
- Only tickets created by the departing member close. Tickets they were added to, or that they claimed as staff, are not touched.
- A kick is reported as left. Discord does not tell bots the difference, so the orange "kicked" notice is only used when the bot can tell a kick apart, which today it cannot. Expect grey for kicks.
- ModMail tickets created by the member are included, since they are open tickets with that creator.
- With this switch off, a ModMail ticket stays open after its member leaves. Unless they still share another server with the bot, staff replies can no longer reach them. The first reply that fails posts a Staff reply not delivered notice in the ticket with a Close Ticket button.
- Rejoining does not reopen anything. Staff can
/reopena ticket by hand if the member comes back and the channel still exists. - The plan is checked on the bot owner at the moment of the event. If the check fails, the tickets stay open rather than being closed by mistake.
- If the bot is offline when the member leaves, the event is missed and the tickets remain open. Use the inactivity timer as a safety net.
The wait before closing is fixed at roughly 1.5 seconds and cannot be extended. If you want departing members to have a chance to come back before their tickets close, leave this switch off and rely on the inactivity timer instead.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Tickets stayed open after a member left | The switch is off, the owner's plan is Free without grandfathered access, or the bot was offline at the time | Check Also close when the member leaves and the plan; close the tickets by hand or wait for the inactivity timer |
| Only some of the member's tickets closed | The others were already closed, or the member was a participant rather than the creator | Expected; participant tickets are not affected |
| The notice says "left" but the member was kicked | Discord reports kicks and leaves the same way | Expected; check your server's audit log for the real reason |
| The channel was not deleted | After closing is set to Move the channel, the ticket is pinned, or the transcript failed (for example with neither a transcripts channel nor a logs channel) | Set After closing to Delete the channel in Closing tickets → Closing rules and a logs channel under General → Where the bot posts, or unpin and delete manually |
| No transcript was saved | Transcripts is off | Turn it on in Closing tickets → Transcripts. Staff can also run /transcript in the closed ticket |
| "Auto-close requires a Basic, Pro, or Enterprise plan." | Free plan without grandfathered access | Upgrade at ticketcord.com/pricing |
| A staff member's tickets closed when they left | They had created tickets of their own | Expected; the rule is based on the ticket creator |
Common questions
Which tickets close when someone leaves? Every open ticket that the departing member created on that server. Tickets they merely took part in are left alone.
Is there a grace period in case they rejoin?
No. Tickets close about 1.5 seconds after the leave event. If the member comes back, staff can /reopen a ticket whose channel still exists.
Does it work for bans? Yes. A ban closes the member's tickets with a red "banned" notice instead of the grey "left" notice.
Why does a kicked member show as "left"? Discord sends the same event for kicks and voluntary leaves, so the bot cannot distinguish them. Only bans are reported separately.
Does it save a transcript first? Only if Transcripts is on in Closing tickets → Transcripts. The close runs your normal close settings.
Do I need auto-close timers on for this to work? In Closing tickets → Auto-close and reminders, yes: Also close when the member leaves is inside the Auto-close card and only shows while that card is on, which also turns on the inactivity timer. Once both are on they act separately: the timer closes quiet tickets, and the member-leave switch closes a departing member's tickets right away.
Which plan do I need? Basic or higher, or grandfathered auto-close access from before it became a paid feature.
Join our Discord server for support
Was this page helpful?
Last updated on