Ticket Panels

A ticket panel is a message with a button (or select menu) that users click to open a ticket channel.

Creating a panel

1. Go to Ticket Settings → Panels
2. Click Yeni Panel
3. Configure:

- Title / Description — what users see

- Button label — e.g. "Open a Ticket"

- Category — where ticket channels are created

- Support roles — who gets pinged and can see new tickets

1. Send the panel to a public channel

Panel anatomy

Each panel has independent settings:

• Buttons — up to 5 buttons per row, multiple rows
• Forms — optional questions users answer before ticket opens
• Permissions — who can open tickets (role gate)
• Categories — which Discord category hosts the channels
• Transcripts — auto-save logs when ticket closes

Multi-panel setup

Premium servers get up to 20 panels vs 2 on free. Each panel is independent — changing one does not affect others.

Common multi-panel patterns:

• Support (general help) + Reports (player reports) + Appeals (ban appeals)
• Language-specific panels (English / Turkish / Arabic)
• Role-gated panels (VIP-only, staff-only)

Button types

• Primary (blue) — default action
• Secondary (gray) — alternative
• Success (green) — positive action (e.g. confirm)
• Danger (red) — destructive action (e.g. close ticket)
• Link (gray with arrow) — external URL

Permissions reference

A ticket has four role tiers with different permission states (opened/closed):

• Support team — can see all tickets, always has full access
• Additional roles — staff-like access (e.g. moderators)
• Owner (ticket opener) — can see their own ticket
• Everyone else — no access

You can fine-tune view/send/attach permissions per tier × state in Ticket Settings → Permissions.

Transcript files

When a ticket closes, a full transcript is saved to guilds/<guild>/tickets/<channel>.html. The bot pins the URL in the channel before deletion and in the log channel (if configured).

Retention: 30 days default — configurable per panel.