🎫 Tickets

Let members open a private channel with your team from a panel: a message with buttons or a menu.

Set it up

Go to Members → Tickets in the dashboard.

1. Panels → New panel: pick a ready-made panel (Support, Appeals or Applications: message, buttons and every category with its form, ready to publish) or start from scratch and choose Buttons (visual, up to 5 categories) or a Dropdown menu (up to 25, with a description under each). Either way, pick the channel it's posted in.
2. Design the panel's message with the embed builder, and check it under As a member sees it.
3. Add categories: what a member picks, like "General support" or "Billing". Each one can have its own emoji, description, Discord category, extra staff roles, an opening form (up to 5 questions asked before the ticket opens) and a welcome message.
4. Save and publish. Edits go live with Save and republish.

Categories you use often can be saved as presets and added to any panel in one click, from the panel's category list or from the preset library (Add to panel; with no panel yet, it creates one). Every server starts with three: General support, Report a member and Purchases & orders.

Tickets open in the Discord category you pick for their category, else the one in Settings. If neither is set, Vaqun creates a Tickets category the first time and uses it from then on (you can change it in Settings).

Inside a ticket

Only the member, your staff roles (plus the category's) and supervisors can see it. The ticket has Claim and Close buttons. Staff can also use /claim, /close, /ticketadd @member and /ticketremove @member.

• Claim: a soft claim just marks who's handling it; an exclusive claim leaves other staff read-only (supervisors can still take over).
• Close: makes a transcript (an HTML file of the whole conversation), then archives the channel (the member loses access, and staff can Reopen it) or deletes it, as set in Settings.

Flows (Premium)

A step-by-step conversation before a ticket opens: messages, menus, buttons, forms and a final confirmation. Build it in Flows (with undo/redo), try it in the preview, then pick it for a category.

Steps run in order, and reaching the end (or the Cut here line) opens the ticket. An option set to Jump to the cut goes to the steps after that line instead, which end without a ticket. That's handy for questions the FAQ already answers.

Settings

Channels & team, channel names (with {numero}, {usuario}, {apodo}, {staff}, {categoria}, {panel}), close & reopen, transcripts, the satisfaction survey (Premium), limits (open tickets per member, blocked members) and closing inactive tickets (Premium).

Turning a panel off takes its message down and stops new tickets, but keeps everything. Deactivating the ticket system (Settings) deletes every panel, category, flow, preset and ticket record. Channels of open tickets are left alone.