Docs / Guides / Set up a support desk

Set up a support desk

In short

You will have a posted ticket panel, a staff team, questions members answer first, a log channel with transcripts and a tested ticket from open to close.

Before you start, make sure the bot has the Manage Channels permission. Setup stops without it.

1. Turn on Tickets

Open the dashboard and choose your server. On the Services page, turn on the Tickets switch.

While Tickets is off

Every ticket command and every panel button answers "The Tickets service is switched off in this server." If you have Manage Server, a button under that answer switches Tickets on.

2. Run setup

On the Tickets Home page, press Run setup. On the Setup page that opens, press Run setup again and confirm. Setup makes what the server is missing in one go and posts a first panel.

What setup makes

Run setup shows on Home while the server has no panel. Setup makes:

  • A category for new tickets and one for closed tickets. New ones are hidden from @everyone. A category named Support Tickets, Tickets or Open Tickets is reused for new tickets and hidden too. One named Closed Tickets or Archived Tickets is reused as it is.
  • A channel to open tickets from, where @everyone can read but not type. Without one to reuse, it makes #open-a-ticket.
  • A log channel: the one you already set, else one with ticket-log or support-log in its name, else a new #ticket-logs hidden from @everyone with only the bot let in. Give your staff access to it in Discord.
  • A "Support Staff" team, when the server has none, built from roles that look like staff roles.
  • A first panel called "General Support" (title "Need Help?", button "Open Ticket"), when the server has none, posted in the channel to open tickets from.

When the server has a text channel named support or one with open-a-ticket or create-ticket in its name, the Setup page asks first: "Use #support" or "Make a new channel". For a channel only named support, "Make a new channel" is picked at first. A log channel it finds gets the same question.

The bot needs the Manage Channels permission. Without it, setup stops before it changes anything. See Set it up for the full list.

3. Put your staff in the team

On 2 Answering, open the Who answers card and press New team or edit the team setup made. Give the team a name and add people by user ID or pick a role. Then pick the team under Who answers by default on 1 Opening.

Who sees and answers tickets
  • Team members get access to every ticket channel opened for their team. They count as staff for claim, close, note and the other staff commands.
  • Pick a Ping role if the team should be pinged on new tickets.
  • Without a team, a new ticket is opened to the roles with Manage Server, unless the button or menu option that opened it lets a role in.

4. Ask the questions you need

On 1 Opening, open the Questions card and build a set of questions. Then pick it for the panel under Who answers by default, so members answer it before a ticket opens.

Question limits and types
  • A set asks up to 25 questions. They open in a Discord pop-up, up to 5 to a page. The member presses Continue between pages.
  • A section header takes a place on its page. A question that depends on an answer from its page moves to the next page.
  • A question can be short text, a paragraph, a number, a date, a choice and more. See Tickets features for the field types.
  • A dropdown or a yes or no question always needs an answer. The others can be required or not.

5. Check the panel

On 1 Opening, pick the panel and read its message, buttons and Where tickets open. Change the text or the buttons to fit your server.

How changes reach Discord
  • A bar on top of the editor says whether the panel is in Discord.
  • Button changes reach Discord by themselves. Text and look changes wait for Update in Discord.
  • If you made a new panel, pick a channel and press Post in Discord. The bot needs Send Messages and Embed Links in that channel.

6. Set the log channel and transcripts

Open the Settings page. In the Logs card, use Post the log in to pick a staff-only channel. Every closed ticket then posts a transcript card there.

Transcript options
  • The card has a View transcript button. Every saved transcript is also in History on the dashboard, newest first.
  • Saving a copy of the conversation is on by default for each panel. It is the Keep a copy of the conversation switch under Transcripts on 3 Closing.
  • To send the transcript cards to another channel, use Post transcripts in on 3 Closing.
  • Send the member a copy (off by default) DMs the member the transcript when the ticket closes.

7. Optional: Let members open tickets by DM

On 1 Opening, in the Every panel view, find the Tickets by DM card. Turn on Members can open a ticket by writing to the bot and pick a panel under A ticket by DM opens under.

Which panels work and where staff messages go
  • It is off until you turn it on.
  • The panel has to be on and open a private channel or a private thread. A panel that takes applications cannot be picked.
  • A ticket by DM uses that panel's team, category and limits. It skips the panel's questions.
  • What staff write in the ticket decides where staff messages go. With "Goes to the member" (the default), every message staff type goes to the member. With "Stays with staff", only replies made with /ticket respond or from the dashboard do.
  • See Tickets by DM for what members see.

8. Check that it works

Click the panel's button yourself and answer the questions. Claim the ticket with Claim, write a reply and close it with Close. Open History and confirm the transcript is there.

What you should see
  • The ticket opens as a private channel visible to you, the bot and the team. A message there mentions you and has the buttons Claim, Close and Note.
  • After the close, the log channel gets the transcript card with a View transcript button.
  • The same transcript appears under History.

Next

Was this page helpful?
YourBot docs Reference tables are generated from the code that is running. Ask in Discord