Tickets

The ticket system uses configurable panels to open private support channels with transcripts.

Commands

Command	Description
No slash commands	Tickets are opened via buttons on configurable panels

How It Works

Ticket Panels

In the admin dashboard, the Tickets page lets you configure each panel:

• Panel channel, category, and transcript channel
• Panel title, description, footer, and emoji
• One or more ticket types with labels, IDs, prefixes, emoji, and button style
• Support role per ticket type
• Optional auto-reply text and anonymous support
• Custom modal questions, including Steam ID validation

Users click a button on the panel to open a ticket. They may be prompted with a modal to provide additional information (e.g., a subject or description).

Ticket Lifecycle

1. Open — A private channel is created in a configured category. The user and staff have access.
2. Close Request — The user or a staff member can request closure via a button.
3. Close Confirmation — Staff confirm or decline the close request.
4. Closed — The channel is archived. A transcript is generated and stored in R2.

Staff Anonymity

Staff can participate in tickets anonymously. Messages sent via an anonymous staff thread are attributed to a shared staff identity rather than individual moderator names.

Transcripts

When a ticket is closed, an HTML transcript is generated and stored for later review. Transcripts are accessible via a public URL:

/transcripts/:guildId/:channelId

Attachments uploaded to tickets are also linked from the transcript:

/transcripts/:guildId/:channelId/media/:attachmentId/:filename

Limits

Tier	Max Panels	Ticket Types Per Panel
Free	0	0
Donor	Unlimited	Unlimited

The panel editor shows a live preview while you configure it, and the closed tickets list lets you reopen transcripts when needed.