🤖

Full Automation

Set it up once, let it run forever. Aix Tickets handles the repetitive work so your team can focus on helping people — not managing channels.

⏱️ Auto-Close

Tickets with no activity are automatically closed after a configurable period. A warning message is sent before closure so users can respond if their issue isn't resolved.

How to configure

Go to CategoriesNavigate to your guild dashboard → Panels → Categories.
Edit a categoryClick the category you want to configure auto-close for.
Set auto-close hoursEnter the number of hours of inactivity before the ticket auto-closes. Set to 0 to disable.

💡 Tip: A warning message is sent when the ticket is about to be closed. Users can reply to cancel the auto-close.

🔔 Inactivity Reminders

When a ticket goes quiet, the bot automatically sends a reminder ping — to the opener, the assigned staff, or both — to keep the support process moving.

Reminder targets

Opener — Reminds the user to respond if they haven't
Staff — Nudges the claimer if they've gone silent
Both — Pings both parties

💡 Tip: Reminders fire before auto-close, giving everyone a chance to continue the conversation.

📂 Auto-Move Channels

Ticket channels are automatically moved between Discord categories based on their current state. This keeps your server organized without any manual effort.

Channel states

Unclaimed → Placed in the default category channel
Claimed → Moved to the "claimed" category channel
Inactive → Moved to the "inactive" category channel

How to configure

In your category settings, set the Discord Category IDs for each state:

    // Category settings

    Discord Category ID (Unclaimed): 123456789

    Claimed Category ID:             987654321

    Inactive Category ID:            111222333

⚠️ Note: The bot needs Manage Channels permission to move channels between categories.

🔁 Auto-Rename

Channel names update automatically when a ticket is claimed. Use custom name format templates with placeholders that fill in dynamically.

Available placeholders

    {number}      → Ticket number e.g. 0042

    {username}    → Opener's Discord username

    {display_name}→ Opener's display name

    {staff}       → Claimer's username

    {category}    → Category name

    {status}      → Current ticket status

Example formats

    Pre-claim:  ticket-{number}          → ticket-0042

    Post-claim: {staff}-{number}         → notdeko-0042

    Custom:     🎫-{category}-{username}  → 🎫-support-john

📑 Auto-Transcripts

When a ticket is closed, a full HTML transcript is automatically generated and delivered to multiple destinations.

Delivery destinations

Opener DM — Sent directly to the user who opened the ticket
Log Channel — Posted to your configured transcript log channel with an embed summary
Dashboard — Viewable in the Transcripts section of the web dashboard

Transcript formats

HTML — Full styled transcript with avatars, timestamps, and embeds
TXT — Plain text version for simple archiving

💡 Tip: Enable/disable transcript DMs and log channel posting in your guild Config settings.

⭐ Auto-Feedback

After a ticket closes, the opener is automatically sent a DM asking them to rate their experience. Scores are tracked per staff member and shown in the Analytics leaderboard.

How it works

Ticket closesThe bot closes the ticket and generates the transcript.
DM sent to openerA feedback embed is sent with 1–5 star buttons.
Score recordedThe rating is saved and attributed to the staff member who closed the ticket.
Shows in AnalyticsAverage ratings appear in the staff leaderboard on the dashboard.

💡 Tip: Feedback is optional — users who don't respond are simply not counted. No spam.

🚫 Cooldowns & Limits

Prevent ticket spam and manage load by setting limits on how many tickets a user can open and how frequently.

Settings

Max open per user — Maximum number of tickets one user can have open at the same time in a category. Default: 1.
Cooldown (seconds) — How long a user must wait after closing a ticket before opening a new one. Set to 0 to disable.

Where to configure

Both settings are per-category. Go to Categories in your dashboard and edit the relevant category.

    Max open per user: 1    → Only 1 open ticket at a time

    Cooldown:         3600 → 1 hour wait between tickets

🛡️ Blacklist

Block specific users from opening tickets in your server. Supports temporary bans with automatic expiry.

Features

Per-guild — Blacklists are scoped to each server independently
Reason tracking — Record why a user was blacklisted
Expiry — Set an optional expiry date for temporary bans
Instant — Blacklisted users see an error immediately when clicking a ticket button

How to blacklist a user

Use the Discord slash command in your server:

    /blacklist add user:@username reason:Spam expires:24h
  

💡 Tip: Admins are never affected by the blacklist — they can always open tickets.