UtilitiesDocs

Tickets

Panels

Set where tickets go, who answers them and what they ask.

#Setting up a panel

/panel create and /panel edit open the same editor. Everything about a ticket is set on its panel.

,panel edit (name)

#Choose where tickets go

Categories sets up to 5 each for open, closed and claimed tickets. A new ticket goes in the first one with room.

A category holds 50 channels. When every one you picked is full, people are told All categories are full.

#Choose who answers them

Permissions sets the Support roles and Manager roles that see every ticket, and what they and the opener can do in one, like attach files.

#Add options and questions

Edit embed and options writes the panel's message, in the same editor as Embeds, and adds up to 10 options. Each option can ask up to 5 questions before its ticket opens.

#Use threads or buttons instead

Style switches tickets from Channels to Threads, and the panel from a Dropdown to Buttons. On a thread panel, Categories becomes Channel: where threads open, the panel's own unless you pick another.

Thread tickets can't be claimed, so the claim settings are hidden until you switch back to channels.

#More settings

Naming

The channel's name when opened, closed and claimed. Only {ticket} (its number), {user} (the opener's username) and {dropdown} (the option picked) work.

  • Opened starts as {ticket}-{user}-{dropdown}.
  • Closed starts as closed-{ticket}-{user}-{dropdown}.
  • Claimed starts empty, so claiming doesn't rename it.
Permission switches
  • Allow ticket deletion lets managers delete tickets. Off by default; support roles can always delete.
  • Allow ticket close lets the opener close, reopen and rename their ticket. On by default.
  • Allow claim override lets support roles unclaim a ticket a manager claimed. On by default.

The opener can always see the ticket, send messages and read its history.

Behaviour
  • Transcript channel: where transcripts are posted.
  • Max tickets open: how many one person can have open from this panel. 3 by default; 0 stops new tickets.
  • Claiming, Auto-pin (pins the first message) and Auto-close (closes a ticket when its opener leaves the server).
Buttons

The label, emoji and color of a ticket's Open, Close, Delete, Claim and Transcript buttons. With Reason ticked, Close, Open, Delete and Claim ask why first and show it under the notice.

Messages

The wording of a ticket's notices, like when it's closed or someone is added. Reset puts the bot's wording back.

Greeting message

The first message in every ticket, Welcome! {user.mention} by default. Display questions shows the opener's answers under it, and Allow mentions lets it ping.

Questions

Up to 5 per option, each with a title, placeholder, answer length and whether it's required.

Settings for one option

An option can have its own naming, permissions and configuration, which replace the panel's for its tickets. Reset clears them.

#Managing panels

#Redraw a posted panel

Redraws the last panel you sent, or the one at a message link. New tickets already use your changes.

,panel update (name)

reqon

,panel update support

UtilitiesApp

@reqon: Panel support updated in # tickets.

#Delete a panel

The bot asks first. /panel list shows every panel.

,panel delete (name)

reqon

,panel delete support

UtilitiesApp

@reqon: Press confirm to delete support!
All commands6
,panel create (name)Manage Server

Create a new ticket panel

,panel edit (name)Manage Server

Edit an existing panel

,panel delete (name)Manage Server

Delete a panel

,panel listManage Server

List all panels

,panel send (name)Manage Server

Send a panel to a channel

,panel update (name)Manage Server

Update the last sent panel message