Skip to main content

How to set up a ticket system in Discord: step by step

How to make tickets in Discord from scratch: add a ticket bot, build a panel, topics, an intake form and a welcome message, set the rules and test it yourself.

Discord Tickets team6 min read

A ticket in Discord is a private conversation between a member and your support team. The member clicks a button on a panel, and the bot opens a channel or thread that only they and your staff can see.

This guide covers the whole setup, from why tickets beat a shared help channel to a working panel you’ve tested yourself. We use Discord Tickets for the examples, but the decisions apply to any ticket bot.

Why tickets instead of a help channel

A shared help channel works while questions are few. After that:

  • questions get buried while a mod is busy answering someone else;
  • private matters go public: nobody wants to discuss a report or a ban appeal in front of everyone;
  • nobody knows who’s on what: two mods answer one person while another waits;
  • there’s no outcome: a week later it’s hard to tell how a conversation ended.

A ticket system fixes this with structure: every request gets its own space, a topic, a clear owner and an explicit close with a reason.

What to prepare

  • Manage Server or Administrator on the server.
  • A panel channel visible to all members, like #support.
  • A staff role, like Support.
  • A log channel hidden from members — the bot posts ticket opens and closes there.
  • A decision on where tickets live: private channels in a category or private threads in one channel. We compare both in ticket channels vs private threads.

Step 1. Add the bot to your server

Sign in to the site with Discord. It only asks for basic profile info and your server list, and the dashboard shows servers where you have Manage Server or Administrator. Pick a server and click Add bot to server.

Keep all the permissions on the invite screen: each one covers a specific job. We break them down in what permissions a ticket bot needs. Discord Tickets is free and runs as a separate Discord app, so there’s nothing to host.

Tip. If your ticket category or log channel is hidden from @everyone, allow View Channel for the bot’s role there. Starting November 16, 2026, Discord hides channels a bot can’t view from that bot entirely.

Step 2. Create your first panel

A panel is the message with a button or menu that members use to open tickets. You can have up to three per server.

In the Panels tab, create a panel and fill in the basics:

  • Panel name — for example, Support.
  • Channel — where the bot publishes the panel.
  • Panel language — RU or EN. The bot uses it for all default text: button and menu labels, the form, the welcome message, its buttons and replies. Your custom text isn’t translated.
  • Trigger — Button for a single queue that goes straight to the first topic, Select menu when members pick from several topics.
  • Opens as — Private channel in a category or Private thread in a parent channel, one choice per panel.
  • Log channel — each panel has its own.

You build the panel message right in the preview, exactly as it will look in Discord. A short heading, a line on when to open a ticket and a clear button label are enough: Need help? Open a private ticket that only you and our team can see. Button label: Open a ticket, style Blurple or Green.

Prefer to stay in Discord? /ticket setup builds a new panel right in Discord, and /ticket dashboard lists your panels and the basic server settings (both need the Panels right from the Access tab).

Step 3. Set up topics

A topic is a type of request. Discord menus fit up to 25 options, but 3–5 topics are usually enough.

Topic Menu description Admin roles
Server question Roles, channels, rules Support
Report a member Rule breaks, harassment, spam Moderators
Staff application I want to help run the server Admins

Each topic has a Label, Emoji, Description, Admin roles and Blocked roles. Admin roles get access to the topic’s tickets, a mention when one opens and the right to close it. Members with a blocked role can’t open that topic — handy for keeping current staff out of the applications queue. Name topics the way members talk: Problem with my role beats Tech issue.

Step 4. Add an intake form

The intake form is a Discord pop-up that appears before the ticket is created. The ticket opens only after it’s submitted, so staff see the actual issue instead of hi, I have a question. Discord allows up to 5 fields.

Example for Report a member:

  1. Pick members — Who are you reporting?
  2. Pick channels — Where did it happen?
  3. Text, paragraph — What happened? Describe it step by step.
  4. Checkbox — I have read the server rules.

Other types include Dropdown, Single choice, Checkboxes, Pick roles and Static text. Fields can be required and have a placeholder and min/max length. Answers go into the welcome message and channel name with {field:Question}. For ideas, see what to ask in a ticket intake form.

Step 5. Write the welcome message

The welcome message explains what happens next. Placeholders: {opener} mentions the member, {topic}, {number} and {field:Question} pull in the topic, ticket number and a form answer.

Hi {opener}! This is ticket #{number}, topic: {topic}.
If you have screenshots, attach them here.
A staff member will reply right here, no need to DM anyone.

Leave it empty and the bot posts a standard note. Under the message there’s a Claim button: a staff member claims the ticket, and a Claimed by note appears with a Close ticket button, so everyone sees who owns what.

Step 6. Set the rules

The panel’s Advanced settings apply to all of its topics:

  • Channel name — ticket-{counter} by default; you can add {username}, {topic} or {field:Question}.
  • Who can close — Opener or admins (default), Admins only or Opener only.
  • Max tickets per member — 1 by default; 0 removes the limit.
  • Cooldown between tickets, seconds — stops back-to-back tickets.
  • Require a close reason — on by default. If only admins close, add Quick close reasons like Resolved or Duplicate.
  • Delete the channel on close — off by default, so a closed channel stays as a read-only archive.

Step 7. Publish and test it yourself

Click Publish, then walk through it as a member — ideally from a second account without staff roles. Check that:

  • the button or menu works;
  • the form opens and required fields block an empty submission;
  • the ticket appears in the right place and the opener and topic roles see it (in threads, also anyone with Manage Threads);
  • the welcome message is filled in and pinned;
  • staff can Claim, then Close ticket with a reason;
  • the log channel shows the open and the close.

Changed a published panel? Click Update in Discord — the message updates in place.

Tip. After launch, check the Overview tab for first response time, time to close and which topics bring in tickets.

Video walkthroughs are in the docs, and panel settings are covered in the panels section. Stuck? Drop by our support server.

Read next

All posts →