How to set up a free Discord ticket bot

What a ticket bot does

A ticket bot gives every request its own private place. A member presses a button, and a channel opens that only they and your staff can see. The conversation stays out of your public channels and out of moderators' DMs, and when it is done the channel closes and a transcript is kept.

Servers use tickets for support questions, staff applications, player reports, ban appeals and orders: anything that needs a private conversation with whoever is on duty.

Before you start

• Manage Server in the Discord server. Discord asks for it before any bot can be added.
• A staff role. The people who answer tickets, for example @Support. You can have one role per kind of ticket.
• A channel for the panel, such as #support, where members can see it but not write.

Setting it up

This uses TicketCrew, which is free for every server with no paid plan. The steps are much the same for any ticket bot.

1. 1

   Add the bot to your server

   Press Add to Discord and choose the server. Discord lists every permission before you confirm. TicketCrew needs 6; the rest are optional and explained in Discord ticket bot permissions, explained.

2. 2

   Open the dashboard

   Sign in to the website with Discord. You will see every server where you have Manage Server, and which of them already have TicketCrew. Everything below is done there, with no commands to memorise.

3. 3

   Build a ticket panel

   The panel is the message members press. Give it a title and a line of text, then add a button for each kind of ticket: Support, Apply for staff, Report a player. A preview beside the form shows the message exactly as Discord will. What to write on it is in How to make a ticket panel.

4. 4

   Choose who answers each kind of ticket

   For each button, pick the staff roles that are let into the ticket and pinged when it opens. Recruiters can see applications without seeing reports. If you want answers before a ticket opens, use a dropdown panel and give an option a few questions: they appear in a Discord pop-up and the answers are posted at the top of the ticket.

5. 5

   Publish, and open a test ticket

   Choose the channel and publish. Press one of the buttons yourself: a private channel opens with you and the staff role inside. Close it with the Close button or /ticket close, and the transcript appears on the dashboard.

Once it is running

• Transcripts are saved automatically when a ticket closes, readable by staff on the dashboard for 30 days and downloadable as HTML, text or JSON. A panel can also post a summary to a transcript channel.
• Inside a ticket, staff can add or remove members, rename the channel, lock it so the member cannot reply, and leave notes only staff can read.
• Knowledge base. Short articles can be offered before a ticket opens, so common questions are answered without one. The dashboard shows how often that works.
• Ratings. After a ticket closes, the member can be asked to rate it in a direct message.

Every server gets the same limits: unlimited tickets, 50 panels and 7 kinds of ticket. They are all on the pricing page.

If something does not work