← All articles

How to Set Up a Ticket System on Discord (Step by Step)

Published 27 Oct 2026

Also available in: Español · Português · Français · Deutsch

A support channel where everyone posts their problems at once works for about a week. After that, questions get buried, staff answer the same thing twice and nobody knows what was resolved. A ticket system fixes this by giving every request its own private channel that only the member and the right staff can see.

This guide walks through a clean setup using the Tickets module of MagnificBot, from the first panel to transcripts and ratings.

What a good ticket system needs

Before touching any settings, decide what you actually want. Most servers need the same five things:

  • One entry point: a message with buttons in a visible channel such as #support.
  • Ticket types: "Report a player", "Billing", "Partnership"… each one routed to the people who can handle it.
  • Private channels: the member and staff only, nobody else.
  • Ownership: a way to say "I've got this" so two moderators don't answer at once.
  • A record: a transcript saved when the ticket closes, so you can check what happened later.

If you only need the first three, the setup takes five minutes. The last two are what make it scale.

Step 1: Invite the bot and open the dashboard

Invite MagnificBot from magnificbot.com (it does not ask for Administrator), then log in to the dashboard with your Discord account and pick your server. Open Tickets.

Create two things in Discord first if you don't have them:

  1. A category where ticket channels will be created (for example "Tickets").
  2. A log channel visible only to staff, where opened and closed tickets and their transcripts are posted.

Step 2: Create the panel

The panel is the message members click. Give it a short title and a description that sets expectations, for example:

Need help? Pick the option that fits your issue. A staff member will reply in the private channel, usually within a few hours.

You can choose the panel colour so it matches your server. Then publish it in your support channel.

Step 3: Add ticket types (departments)

Each type becomes a button on the panel, with its own label, emoji and button colour. This is where routing happens: every type can have its own staff roles. A "Billing" ticket can be visible only to your admins, while "Report a player" goes to moderators.

Type Emoji Staff role Optional form
General help ❓ Helpers No
Report a player 🚨 Moderators Player name, what happened
Partnership 🤝 Admins Server link, member count

Global staff roles still exist for people who should see every ticket, such as owners.

The free plan has a starter limit on ticket types per server. If you need more departments, Premium raises that limit (see pricing).

Step 4: Decide whether to use a form

By default a ticket opens instantly, without a pop-up window. That is the friendliest option for "general help" buttons. For reports or applications, enable the optional form so members answer a couple of questions before the channel is created. Staff then start with context instead of "hi, what's the problem?".

Keep forms short. Two or three fields is plenty; long forms make people give up.

Step 5: Tune the details

A few settings make daily work smoother:

  • Max open tickets per user: one is a sensible default and stops duplicate tickets.
  • Channel name pattern: use {number}, {username} and {category}, for example report-{number}.
  • Close delay: a few seconds between pressing close and the channel being deleted, so people can read the last message.
  • Transcript by DM and rating request: the member receives a copy of the conversation and can rate the support from 1 to 5.

Step 6: Work the tickets

Inside a ticket, staff use buttons or the /ticket command:

  • /ticket claim to assign yourself.
  • /ticket priority to mark urgent issues.
  • /ticket add and /ticket remove to bring in another person.
  • /ticket rename to make the channel name descriptive.
  • /ticket close with an optional reason.

When a ticket closes, an HTML transcript is generated and posted to the log channel. You can open it in any browser, which is far easier than scrolling through a deleted channel that no longer exists.

Common mistakes to avoid

  • Ticket category visible to everyone. Make sure @everyone cannot see the category; the bot handles per-ticket access.
  • Too many types. Six buttons with overlapping names confuse people. Start with two or three.
  • No log channel. Without it, you lose transcripts and ratings, which are your best feedback on staff quality.
  • Giving helpers Discord permissions they don't need. The dashboard has access roles (for example Support) so staff can manage tickets without extra server permissions.

FAQ

Can members open a ticket with a slash command instead of a button?

Tickets are opened from the panel buttons. The /ticket command is for managing a ticket that already exists.

Where are transcripts stored?

They are posted as an HTML file in the log channel you choose, and optionally sent to the member by DM.

Is the ticket system free?

Yes. The Tickets module is included in the free plan with starter limits on ticket types per server. Premium and Pro raise the limits.

Can different teams see different tickets?

Yes. Each ticket type can have its own staff roles, so moderators and admins only see the requests meant for them.

If you are also tidying up moderation and logs, the guide on replacing several bots with one shows how the rest of the modules fit together.

Essayez MagnificBot gratuitement

Tous les modules inclus, configurés depuis un tableau de bord web. Sans carte, sans limite de durée.

Ajouter à Discord — c’est gratuit