Skip to main content

Documentation

How to set up Discord Tickets

Step-by-step guides, from the first panel to access for your team. Every guide comes with a video — a recording of our dashboard doing exactly the steps written under it.

Contents
  1. 01Getting started
  2. 02Your first panel
  3. 03Topics
  4. 04Intake form
  5. 05Welcome message
  6. 06Rules, limits and closing
  7. 07Tickets
  8. 08Access for your team
  9. 09Settings, commands and bot permissions
  10. 10Need help?

01

Getting started

Three steps, about a minute, nothing to host.

1. Sign in with Discord. The site asks for two OAuth scopes only — identify (who you are) and guilds (which servers you are in). No email, no messages, nothing done on your behalf.

2. Pick a server. The list shows servers where you have Manage Server or Administrator. The rest are hidden: you can’t configure what you don’t manage.

3. Add the bot. “Add bot to server” opens Discord’s invite screen. As soon as the bot joins, the dashboard shows the server’s real channels, categories and roles — time for the first panel.

The dashboard has five tabs: Overview (numbers), Panels (what members open tickets from), Tickets, Settings and Access. On your first visit a short tour shows what lives where; replay it from the menu on the left.

Until the bot is on a server, its page shows only the invite: the dashboard shows what really exists in Discord and never invents data.

02

Your first panel

A panel is a message in a channel that members open tickets from.

A panel has one trigger: a button — one queue, or a select menu — the member picks a topic first. Here you also choose where tickets open: a private channel in a category or a private thread in a parent channel. It is one place for the whole panel — all its topics open the same way.

The panel message is built right in the preview, the way Discord will show it. Two formats: Blocks (Components V2) — text, sections with an image, galleries, separators and containers; Content + embeds — a classic message with plain text and up to 10 embeds. Click any block to edit it where it is shown; the “+” between blocks adds a new one.

A server can have up to three panels — say, one each for support, reports and applications.

Video: a panel with a button, created and published

Step by step

  1. Open the Panels tab and click New panel.
  2. Type a Panel name — it tells panels apart in the dashboard and in the ticket list.
  3. Choose the Channel the bot posts the panel to, and the Panel language — the bot speaks it to everyone who comes through this panel.
  4. Keep Opens as → Private channel and pick the Category for ticket channels. For threads, choose Private thread and a parent channel.
  5. Set the Log channel — the bot reports this panel’s opened and closed tickets there.
  6. Build the Panel message in the preview, then set the Button label and its Style.
  7. Click Publish: the panel is saved and the message appears in the channel right away.

03

Topics

A topic sends each request to the right people.

Each topic has its own label, emoji and description — that is how it looks in the panel’s menu. Admin roles get access to the topic’s tickets, a mention when one opens and the right to close it. Blocked roles cannot open the topic at all.

A menu panel has a Menu placeholder — the text in the closed menu until a topic is picked. A button panel uses its first topic.

Topics also carry an intake form and a welcome message — see the next sections. Changed something on a panel that is already live? Click Update in Discord and the message in the channel is updated in place.

Video: a new topic added to a live panel

Step by step

  1. Open the panel, click Add topic under Topics and expand the new topic.
  2. Set the Label and pick an Emoji — the picker has search, standard emoji and your server’s own.
  3. Write a Description — it shows under the label in the topic menu.
  4. In Admin roles, start typing a role name and pick it from the list.
  5. Click Update in Discord — the topic appears in the panel’s menu.

04

Intake form

Questions a member answers before the ticket even exists.

The intake form is a Discord window that opens after a topic is picked. The ticket is created only once it is sent, so the team starts with context instead of “hi, what happened?”.

A form holds up to 5 fields — Discord allows no more. Types: Text (a line or a paragraph), Dropdown, Single choice, Checkboxes, Checkbox, Pick members, Pick roles, Pick channels and Static text — a note with nothing to answer. At least one field must take an answer.

The form is edited right in the window’s preview: click any text to change it, ⚙ for required, the placeholder, answer length, choices and more. An answer can go into the welcome message or the channel name with {field:Question}.

Video: a two-question form for a topic

Step by step

  1. Expand a topic and find Intake form — a preview of the window the member will get.
  2. Click “+” in the empty form and pick a field type — for example Text.
  3. Type the question right in the window and press Enter.
  4. Hover the gap under the field — a “+” appears for the next question.
  5. Click Update in Discord.

05

Welcome message

The first message the bot posts in a new ticket.

The Welcome message is built like the panel message: Components V2 blocks or text with embeds. Leave it empty and the bot sends its standard “Someone from the team will be with you shortly…”.

Tokens: {opener} — a mention of the opener, {topic} — the topic, {number} — the ticket number, {field:Question} — an answer from the form. With “Include the intake answers” on, the bot adds all answers to this same message.

Under it sits a Claim button: an admin takes the ticket, and it turns into “Claimed by …” next to Close ticket.

Video: a welcome that mentions the opener

Step by step

  1. Expand a topic and find Welcome message.
  2. Click “+” in the empty message and pick Text.
  3. Write the welcome; the bot replaces {opener} with a mention of whoever opened the ticket.
  4. Click Update in Discord — new tickets of the topic start with this message.

06

Rules, limits and closing

Advanced settings keep the queue in order.

All of this lives in the panel’s Advanced settings and applies to every topic of the panel. The defaults suit most servers — you can publish without touching them.

Quick close reasons are up to 20 ready answers an admin picks instead of typing. They apply when only admins close and a reason is required. Up to five show as radio buttons in the close form, six or more as a dropdown; “Other” is always last.

SettingWhat it does
Channel nameTemplate for the ticket channel’s name: <code>{counter}</code>, <code>{username}</code>, <code>{topic}</code>, <code>{field:Question}</code>
Who can closeOpener or admins · Admins only · Opener only
Max tickets per memberOpen tickets one member can have at once, 0–50
Max tickets on this panelOpen tickets the whole panel can have at once, 0–500
Cooldown between ticketsSeconds to wait before the next ticket, up to a day
Mention the openerPings the opener in the ticket’s first message
Pin the first messageThe welcome gets pinned in the ticket
Require a close reasonNo closing without a reason; it goes to the log and the Overview
DM the opener why it was closedThe opener learns how the request ended
Delete the channel on closeOff — the channel stays as a read-only archive. Threads are always locked instead
Include the intake answersThe answers are added to the welcome message
Video: a ticket limit, a cooldown and a quick close reason

Step by step

  1. Expand the panel’s Advanced settings.
  2. Set Max tickets per member and the Cooldown between tickets in seconds — 0 means no limit.
  3. Under Who can close, choose Admins only; “Require a close reason” is on by default.
  4. Quick close reasons appear below: click Add reason and type one.
  5. Click Update in Discord.

07

Tickets

What happens in Discord and what the dashboard shows.

In Discord. A member clicks the button or picks a topic, answers the form — and the bot creates a private channel or thread only the opener and the topic’s roles can see. An admin clicks Claim, replies and closes it with Close ticket. The bot reports opening and closing to the panel’s log channel.

In the dashboard. Overview has time to first response and to close, open tickets, the share closed with a reason, opened tickets over 24 hours, 7 or 30 days, the share answered within 30 minutes, the month’s topics and busy hours. The Tickets tab lists them with an “All · Open · Closed” filter; a row opens the ticket’s card: who opened and closed it, when, first response, duration and close reason.

Reading a ticket’s conversation in the dashboard (transcripts) is still in the works — for now the card says so in its place.
Video: the overview, the ticket list and a closed ticket’s card

Step by step

  1. Open Overview — the server’s numbers for the chosen period.
  2. Go to Tickets and pick the Closed filter.
  3. Click a row to open the ticket’s card. Esc closes it.

08

Access for your team

Who else can run tickets in the dashboard.

A server’s dashboard opens for people with Manage Server or Administrator in Discord. Without an entry of their own they get Panels and Transcripts; the server owner always has everything.

The Access tab grants rights to a member or a whole role — a role gives them to everyone who has it. Rights are switched in the entry’s row; the bin icon takes access away.

RightWhat it gives
PanelsPanels, topics, publishing and server settings
TranscriptsTicket history
/ticket banThe Discord command that bans a member from opening tickets. With Manage Roles it works without the tick too
AccessThe Access tab: granting and removing rights
Video: a role gets the Panels right

Step by step

  1. Open Access and start typing a name, @role or ID in Member or role.
  2. Pick the role or member from the list.
  3. Tick the rights under What they get.
  4. Click Grant access — the entry appears in the list below.

09

Settings, commands and bot permissions

Server-wide values and what the bot needs.

Settings hold the bot language (the bot answers commands, writes errors and starts new panels in it), the staff roles pre-filled into new topics and ticket-banned roles: a member with any of them can’t open a ticket anywhere on the server.

Commands in Discord: /ticket setup — a new panel built step by step right in Discord (up to three per server); /ticket dashboard — the panel list (open any of them to edit and update it in Discord) and the basic settings: bot language, default staff roles, ticket-banned roles; for holders of the Access right also the Access section — give a member or a role the Panels, Transcripts, /ticket ban and Access rights, change or remove them, by the same rules as the tab on the site. Both need the Panels right (with Access alone, /ticket dashboard opens straight on the Access section). /ticket help — the commands and who may use them, for everyone. /ticket ban — bans a member from opening tickets for a time (30m, 12h, 7d, 2w or forever) with a reason: the bot gives them the ban role from the settings.

The invite asks only for what tickets need. You can remove the bot at any time in your Discord server settings.

Since 2026 Discord requires a separate Pin Messages permission to pin — Manage Messages is no longer enough. The invite now grants it; if the bot joined your server earlier and the welcome isn’t pinned, give the bot’s role Pin Messages or invite the bot again.
PermissionWhy
Manage ChannelsCreate a channel per ticket, and delete it on close if that is on
Manage RolesKeep the ticket channel private — only the opener and the topic’s roles see it. And give the ban role with /ticket ban
Manage Threads · Create Private Threads · Send Messages in ThreadsThe Private thread mode
View Channels · Send Messages · Embed Links · Attach Files · Add ReactionsPost panels, welcome messages and log entries
Read Message History · Manage MessagesDiscord lets a bot grant in a ticket channel only rights it has itself — the opener and staff need these
Pin MessagesPin the welcome in the ticket when “Pin the first message” is on

10

Need help?

Short answers live in the FAQ, longer conversations in Discord.

The FAQ on the home page covers pricing, privacy and languages. For anything else, join the Discord Tickets server with your server ID, and the ticket number for ticket questions.

Discord Tickets is an independent RootCore project, not affiliated with Discord Inc. We also make discord-webhook.com, a free webhook and embed builder.