Skip to main content
Automatically close tickets when the ticket creator leaves, is kicked, or is banned from your Discord server.

​
Why Use This Feature?

When a user leaves your server:
  • They can no longer respond to their ticket
  • Tickets become unresolvable
  • Open tickets clutter your queue
  • Staff time is wasted on abandoned tickets
Auto-close on user leave solves this by:
  • Detecting when ticket creators leave
  • Automatically closing their tickets
  • Optionally saving transcripts
  • Keeping your ticket queue clean

​
How It Works

​
Setting Up

1

Navigate to Configuration

Dashboard → Configuration → Automation
2

Find Auto-Close Settings

Scroll to Auto-Close on User Leave
3

Enable Feature

Toggle the setting on
4

Configure Options

Set transcript and notification preferences
5

Save

Feature is now active

​
Configuration Options

​
Basic Settings

​
Close Message

Customize the closure message in the ticket:

​
Transcript Options

If generating transcripts:

​
Trigger Events

The feature triggers when a user: All events trigger ticket closure by default.

​
Configuring Events

You can enable/disable specific triggers:
  • Leave: Close when user leaves voluntarily
  • Kick: Close when user is kicked
  • Ban: Close when user is banned

​
Notification Options

​
Ticket Closure Embed

When a ticket is auto-closed, an embed is posted:

​
Log Channel

Optionally log auto-closures:
  • Send notification to log channel
  • Include ticket details
  • Track closure reasons

​
Multiple Tickets

If a user has multiple open tickets:
  • All their tickets are closed
  • Each gets its own closure message
  • Transcripts generated for each (if enabled)
  • Processed sequentially to avoid rate limits

​
Delay Option

​
Why Use a Delay?

  • User might rejoin quickly
  • Accidental disconnects happen
  • Gives grace period

​
How Delay Works

  1. User leaves server
  2. System waits configured delay (e.g., 5 minutes)
  3. If user hasn’t rejoined, tickets close
  4. If user rejoins, nothing happens

​
Configuring Delay

​
Staff Tickets

​
What Happens to Staff?

If a staff member leaves:
  • Their tickets remain open (if they created any)
  • Tickets they’re assigned to are unassigned
  • Configurable behavior

​
Staff Leave Options

​
Best Practices

Enable Transcripts Save transcripts before closing for record-keeping.
Use Short Delay 5-minute delay handles accidental disconnects without stale tickets.
Log Closures Track auto-closures in your log channel for awareness.
Review Settings Periodically check if settings match your support needs.

​
Interaction with Other Features

​
Auto-Close Timer

If both auto-close on leave AND timed auto-close are enabled:
  • User leave triggers immediate closure (or after delay)
  • Takes precedence over timed auto-close

​
SLA

When ticket is auto-closed due to user leaving:
  • SLA timer stops
  • Not counted as breach (user unavailable)
  • Marked as special closure reason

​
Troubleshooting

Check that the feature is enabled and your bot has proper permissions (Manage Channels if deleting).
Verify transcript options are enabled in the auto-close settings.
If the delay passed before they rejoined, ticket would close. They can open a new one.

Need Help?

Questions about auto-close? Join our Discord