Tickets
Support tickets from a panel reaction.
Product overview: Ticketsβ why it exists. This page is the setup guide.
Overview
π« opens a private channel under a category. !close closes it. Optional support role and log channel. With transcripts on, a plain-text history file is posted to the log channel (up to 500 messages).
Who may open
Optional allowed_role_ids: if set, the opener must hold at least one of those Discord roles. Empty = anyone who can react may open. Denied users get deny_message in the panel channel.
Priority by role
priority_rules map Discord roles to placement. When multiple rules match, the highest priority wins. Each rule may set name_prefix (channel name), category_id, support_role_id, and a short label. Open message placeholders: {user}, {priority}, {label}.
[
{"role_id":"ROLE_VIP","priority":100,"name_prefix":"vip","label":"VIP","category_id":"","support_role_id":""},
{"role_id":"ROLE_PARTNER","priority":50,"name_prefix":"p","label":"Partner"}
]Staff inbox
Open tickets appear under Dashboard β Server β Tickets (same guild). Staff can filter by status, claim (assignee), set open / claimed / waiting / closed, and add notes. Conversation stays in Discord; !close marks the row closed. Tickets opened before this feature only appear if re-opened after deploy.
Configure
Dashboard β Settings β Tickets. Set panel, category, support role, allow-list, priority rules, log channel, and transcripts. Overview: Tickets.