Tickets

The Tickets tab sets up private support tickets. Members press Open a ticket on a panel the bot posts, and the bot creates a private channel for them and your team. The tab also shows a preview of the panel, a way to post it, a count of your tickets and a list of the latest ones.

Press Save changes after editing. Saving restarts the bot so it picks up the change, and the preview updates once you have saved.

Panel title

The heading of the ticket panel. It cannot be left empty. A new bot starts with Need help?.

Panel text

The text shown under the title on the panel, for example what members should open a ticket about. You can use several lines. It can be left empty, in which case the panel shows only the title and the button. A new bot starts with Open a private ticket and a team member will respond.

Ticket channel name

What new ticket channels are called. The bot adds a four-digit ticket number, so ticket gives channels such as ticket-0001, ticket-0002 and so on.

Use lowercase letters, numbers and hyphens only, up to 30 characters. It cannot be left empty. A new bot starts with ticket.

Ticket handler role

Members with this role can see every ticket channel and answer in it, and can use /ticket claim and /ticket close.

Superusers and anyone at moderator level or above can also claim and close tickets. However, the bot only adds the ticket handler role to each new ticket channel, so the Moderator and Admin roles are not added. If your moderators should read tickets, give them this role too. Setting or changing this role affects tickets opened after you save, not tickets that are already open.

If set to None, no role is added to ticket channels, so each ticket is visible only to the member who opened it, the bot, and anyone whose own Discord permissions let them see every channel.

Ticket category

The Discord category new ticket channels are created in. It must be set before members can open tickets or the panel can be posted. This is the same setting as on the Channels tab.

Ticket log

Where closed tickets are logged, with the conversation attached as a TXT file. It must be set before tickets can be closed. This is the same setting as on the Channels tab.

Preview

Shows the panel as the bot will post it: your title, your text, the footer with your bot's name and Support, and the Open a ticket button. The coloured edge uses your bot's main embed colour.

Posting the panel

You can post the panel in two ways.

  1. From the dashboard. Under the preview, choose a channel in Post it in and press Post panel. The bot posts the panel in that channel as itself. The list shows only your own server's text and announcement channels. This needs a ticket category to be saved first, and the bot must be running; until then the tab tells you what is missing instead of showing the form. Start the bot on the Power tab. If the bot cannot post in the channel you chose, you are told to check it can view the channel, send messages and embed links there.
  2. From Discord. As a superuser, type your prefix followed by panel in the channel where the panel should go, for example ,panel. The bot deletes your message and posts the panel. See General for the prefix.

There is no slash command for posting the panel.

You can post the panel in more than one channel. If you change the title or text later, save, then post the panel again to show the new wording; panels already posted keep their old wording, but their button still works.

Opening a ticket

When a member presses Open a ticket:

  • if they already have an open ticket, the bot points them to it instead of opening a second one;
  • otherwise the bot creates a new channel in the ticket category, visible to that member, the bot and the ticket handler role, and posts a welcome note in it.

Members do not need any access level to open a ticket, and this works even while the setup lock is on. See Access.

Claiming a ticket

A ticket handler types /ticket claim in the ticket channel to mark it as theirs. If someone else has already claimed it, the bot says who. Claiming only records who is dealing with it; it does not change who can see or answer the ticket.

Closing a ticket

A ticket handler types /ticket close in the ticket channel and gives a reason, which is required. The bot then:

  1. reads the conversation;
  2. posts a Ticket #N closed card in your ticket log, with who opened it, who closed it and the Resolution, and the conversation as a TXT file;
  3. sends the member a direct message with the reason and the TXT file;
  4. deletes the ticket channel.

If transcript links are turned on, the log card and the direct message also include a link to a web page of the conversation. See Transcripts.

If the member has direct messages turned off, the ticket still closes and the person closing it is told the transcript is in the log. If the log cannot be posted, the ticket is not closed, so you can fix the ticket log and try again.

Listing tickets

/ticket list shows your own tickets. Ticket handlers can name a member to see theirs.

At a glance

Three numbers about your bot's tickets:

  • Open now, including how many of those are claimed;
  • Closed in the last 30 days;
  • Tickets ever.

A bot that has never been started shows no tickets. If the dashboard cannot read your bot's tickets, it says so instead of showing numbers.

Recent tickets

A table of your ten latest tickets, newest first, with the ticket number, the Discord user ID of the member who opened it, its status (Open, Claimed or Closed), when it was opened and closed, and the closing reason. Times are shown in UTC.

The dashboard only shows tickets. Replying, claiming and closing all happen in Discord.