Tickets

Quick Start (Slash Commands)

The fastest way to get a working ticket system running without touching the dashboard:

1. Run /server-setup and open Tickets, then Panels & Types.
2. Click New Panel and give it a title and, if you want, a description. This is the message members will see and click to open a ticket.
3. Click Add Type to create at least one ticket type, like "Support," with a label and an optional emoji.
4. Open that type and set a Category so its tickets land in the right place, and a Staff Role Override if you want a specific role to see it instead of your default Mod/Admin roles.
5. Back on the panel, click Post / Repost and choose a channel to publish it to.

Members can now click the panel to open a ticket. Full details on every panel and type option are under Panels & Types below.

From the Tickets menu, click Settings to tune server-wide behavior:

1. Defaults turns the whole ticket system on and sets a fallback category and welcome message for types that don't set their own.
2. Staff & Claiming lets you set a role to ping when a ticket opens and decide whether staff can claim a ticket to work it exclusively.
3. Limits & Auto-Close caps how many tickets one member can have open and auto-closes tickets after a period of inactivity.
4. Under Closing, you can require a reason and/or confirmation before a ticket closes, and DM the owner when it does.
5. Rating & Controls adds a post-close star rating and lets you choose which staff control buttons appear inside ticket channels.

See In-Ticket Controls and On Close below for what each setting affects.

Commands

Panels & Types

A panel is a message you post to any channel, in one of three styles: Buttons (default, up to 25 ticket types), Dropdown (a select menu, up to 25 types), or Commands (just points members at /ticket open).

Each type you configure has its own label, emoji, button color, description, destination category, staff role(s) (falls back to your Mod/Admin roles if left blank), ping role, custom welcome message, channel name format, and up to 5 pre-ticket questions asked in a modal before the channel is even created.

Opening a Ticket

• Default limit of 1 open ticket per member (raisable up to 50 per member).
• Hard server-wide cap of 50 open tickets at once.
• 30-second cooldown between opens per member.
• A private channel is created — visible to the opener, resolved staff role(s), and Aegis only — named from your format template (default ticket-{username}-{number}, with a persistent incrementing ticket number).

In-Ticket Controls

The opening message always has Close; the rest are independently toggleable (all default on except Claim):

Closing shows a confirmation button by default, and can optionally require a reason via modal.

On Close

Aegis generates a browsable HTML transcript (viewable and searchable from the dashboard), logs the close with opener/closer/reason, optionally DMs the ticket owner a close notice and/or a 1–5 star rating request, then deletes the channel after a short delay.

Auto-Close

Optional — force-closes a ticket after a configurable number of hours (default 48) of no new messages, checked every 15 minutes across all servers.

Dashboard

Build panels and types visually, tune all the toggles above under Tickets → Settings, and view/manage every currently-open ticket plus rating stats from a live ops panel.

Everything here is also reachable without leaving Discord: run /server-setup and pick Tickets for the same panel/type builder and settings, driven by buttons and dropdowns instead of the dashboard's forms. Both read and write the same data, so a panel built one way can be edited from the other.