Server
Tickets
Support panels with topics, forms, transcripts, ratings and auto-close.
Setup menu#
/ticket setup opens one menu with every ticket setting: ticket category, archive category, transcript channel, ticket logs, support roles, claiming, staff pings, welcome message, channel names, limits, auto-close, ratings and more. Pick a setting from the dropdown — channels, categories and roles use pickers, text opens a form, switches flip instantly — and every change is saved at once. Create one for me makes a private channel or category, and Post panel here posts a ready-to-use ticket panel.
The options (/ticket setup category: support_role: …) still work for a one-line setup.
Free servers get 3 panels with up to 5 topics each; Premium raises that to 15 panels and 25 topics.
Quick start#
/ticket setup category:Support support_role:@Staff(transcripts on by default)/ticket panel channel:#support title:"Need help?" categories:"general:General:🎫;billing:Billing:💳"(key:Label:emoji, separated by;)- Members click the panel button (or
/ticket create). Staff use the buttons in the ticket.
- Make it yours:
/ticket optionsand/ticket topic(below)./ticket settingsshows everything.
Topics (per panel)#
Every panel button/menu entry is a topic, and each topic can have its own:
| Setting | Example |
|---|---|
| Extra staff roles | /ticket topic edit panel:Support topic:billing staff_role:@Billing (pick again to remove) |
| A form before opening (up to 5 questions) | questions:"What's your order ID? | What went wrong?" (none clears) — answers appear in the ticket |
| Its own Discord category | category:#Billing tickets |
| Its own channel names | naming:billing-{number} |
| Its own welcome message | welcome:"Hi {user}, billing will reply within a day." |
/ticket topic add panel: label: … adds one, remove deletes one, list shows every panel and its topics. The panel message updates itself right away.
Options (whole server)#
/ticket options — fill in only what you want to change:
| Option | What it does |
|---|---|
auto_close_hours | Tickets nobody wrote in for N hours get a warning with a Keep it open button, then close by themselves (0 = never) |
transcript_dm | DM the member their transcript when the ticket closes |
feedback | The closing DM asks for a 1–5 rating and an optional comment; ratings show in /ticket stats and the ticket log |
ping_support | Mention the support roles when a ticket opens |
require_reason | Closing needs a reason (the close form makes it required) |
staff_only_close | Only staff can close |
cooldown · max_open | Seconds between tickets per member · open tickets per member |
naming · welcome | Default channel names ({number} {username}) and welcome message |
Commands#
| Command | Who | What |
|---|---|---|
/ticket create subject: | Anyone | Open a ticket |
/ticket close reason: · reopen | Opener or staff | Close (saves a transcript) / reopen |
/ticket claim · unclaim | Staff | Take ownership |
/ticket add user: · remove user: | Staff | Bring people in |
/ticket rename · priority · status | Staff | Organise |
/ticket transcript | Staff | HTML transcript now |
/ticket delete | Staff | Transcript, then delete the channel |
/ticket block user: | Managers | Block/unblock someone from opening tickets (no user = list) |
/ticket stats | Managers | Open now, last 30 days, average time to close, average rating, top staff |
/ticket options · topic add|edit|remove|list | Managers | Fine-tuning and per-topic settings (above) |
/ticket setup · panel · settings | Managers (Manage Server) | Configuration |
Transcripts are self-contained HTML files; retention is configurable.
Still stuck? Ask in the support server — real people answer.