Skip to main content
The Tickets cog provides a full-featured ticket system with panels, autoresponders, transcripts, and in-ticket management actions.

Concepts

  • Panel — a configured set of ticket types that users can open from a posted embed/button. Multiple panels can exist per guild.
  • Ticket — an individual support channel created when a user opens a ticket from a panel.
  • Transcript — an HTML log of all messages in a ticket, generated on close or delete.
  • Autoresponder — a keyword-triggered automatic reply within ticket channels.
  • Blacklist — per-panel or server-wide lists of users prevented from opening tickets.
  • Priority — a label (low / medium / high / critical) that can be set on a ticket.

Commands

All commands are nested under /ticket.

Ticket Management

CommandDescription
/ticket manageOpens the interactive ticket panel manager for creating, editing, and posting panels.
/ticket autorespondersOpens the interactive autoresponder manager (ticket channels only).

In-Ticket Actions

CommandDescription
/ticket closeCloses the current ticket, generates a transcript, and archives the channel.
/ticket openRe-opens a previously closed ticket.
/ticket deleteDeletes the ticket channel after generating a transcript.
/ticket escalateEscalates this ticket to another panel, sending that panel’s welcome message.
/ticket transcriptGenerates and sends an HTML transcript of the ticket without closing it.
/ticket claimClaims the ticket, assigning yourself as the handler.
/ticket unclaimUnassigns yourself as the ticket handler.
/ticket renameRenames the ticket channel. Omit the name argument to reset to the default.
/ticket addAdds a user to the ticket channel.
/ticket removeRemoves a user from the ticket channel.
/ticket prioritySets the priority label on this ticket (low / medium / high / critical).
/ticket closerequestRequests that this ticket be closed (notifies the opener for confirmation).
/ticket blacklistManages ticket blacklists.

Permission Requirements

In-ticket management actions require the user to be ticket staff (a role configured per panel) or have Administrator. Opening and closing requests are available to the ticket opener.