Nouveau-25% on Premium with the code NOEL25, until December 31
Documentation Community

Tickets

A panel with buttons: each member opens a private channel with staff, with the right reason and the right info from the start.

3 min read 4 sections 17 commandes

In short
/ticket creates and configures your panels. The dashboard adds a visual editor.
In this guide
  1. Setting up tickets
  2. Opening rules
  3. Inside a ticket
  4. The visual editor

01Setting up tickets

/ticket opens a three-step screen. The easiest way: pick your team, then click "Install all".

  1. Your team: the roles that see tickets and answer them.
  2. The panel channel: where members click to open a ticket.
  3. Go online: "Install all" creates the panel channel, the tickets category and a logs channel reserved for the team, then puts the panel online.

A panel can offer several ticket types (Support, Report, Partnership...), one button per type. Each type has its text, its welcome message, questions asked before opening and its category. Once the panel is online, your changes are applied to it automatically.

The Settings button holds the rest, all optional, grouped by moment: opening a ticket, during the ticket, closing a ticket, panel appearance.

02Opening rules

In Settings, the "Opening a ticket", "During the ticket" and "Closing a ticket" screens add:

  • a delay between two tickets and a maximum number of open tickets per member
  • a minimum account age
  • opening hours (Paris time), with an out-of-hours message
  • a mandatory reason on closing
  • a private rating on close: the author rates the staff member who handled their ticket from 1 to 5, with an optional comment, only once
  • a reminder to staff if nobody has replied, and closing after inactivity

/config ticketuserblacklist prevents a member from opening tickets.

03Inside a ticket

CommandEffect
/tickettools claimClaim it, like the ticket's button. Depending on the panel's setting, the other staff members keep access, can no longer write, or can no longer see the ticket
/tickettools unclaimGive the ticket back to the team: no more owner, the whole staff has access to it again
/tickettools ticketpriorityLow, medium, high or urgent
/tickettools ticketassignAssign the ticket to a staff member
/tickettools ticketnoteInternal notes, invisible to the author
/tickettools transcriptHTML file of the conversation, also sent on closing
/tickettools ticketreopenReopens a closed ticket

Private claim: in a panel's settings (Appearance screen, or the dashboard), "Claim" offers three modes. Disabled: the whole staff keeps access. "Prevents other staff from speaking": they read without writing. "Prevents other staff from seeing": only the one who claimed the ticket still sees it, with its author and the administrators.

  • The mode applies to the button, to the command and to automatic claiming (the first staff member who replies takes the ticket, if the option is on).
  • Assigning the ticket to someone gives them access. To give it back to the whole team: /tickettools unclaim, reserved for the one who claimed it and for those with Manage Channels.
  • In a ticket opened as a thread, the mode changes nothing: a thread has no per-role permissions.

04The visual editor

In the dashboard, Tickets tool, each panel has an editor with live preview: title, text, image, color and style of the message, and the buttons (text, emoji, color, drag-and-drop order). You see the result as it will appear on Discord before saving it.

Commands in this guide

Options and permissions for each command

Something unclear? Tell us on the support server, and the guide will be fixed.