Community
Tickets
Members open a private ticket channel from a panel. Optionally restrict who may open, route VIPs by role, then !close with optional transcripts.
- Panel reaction open
- Role allow-list
- Priority rules
- Private channels
- !close + transcripts
Why teams turn it on
Structured support
No more DMs vanishing into staff personal inboxes — tickets are server channels with roles.
Role-aware routing
Allow only certain Discord roles to open, and map roles to priority prefixes, categories, or staff roles.
Clear lifecycle
Open → help → close. Transcripts keep a record when you enable them.
How it works
1. Panel reaction
Member reacts on the ticket panel (e.g. 🎫). Optional allow-list checks Discord roles first.
2. Priority plan
Matching priority rules pick category, channel name prefix, support role, and label (highest priority wins).
3. Close + transcript
!close archives the flow. With transcripts on, a text history (up to 500 messages) can post to a log channel.
Real situations
Ban appeals
Private channel per appellant with staff-only visibility.
VIP / partner support
Higher roles open into a VIP category with a vip- channel prefix and a dedicated staff role.
FAQ
How long are transcripts?
Plain-text history up to 500 messages when transcripts are enabled — see the setup guide.
Can only Premium members open tickets?
Yes — set allowed_role_ids to the Discord roles that may open. Empty list means anyone.