How to Set Up a Discord Ticket Bot (Complete 2026 Walkthrough)

Most ticket bot setups fail in the same two places: permissions that look right but are not, and a panel nobody can find. This walkthrough covers both.

What you need before you start

• Manage Server permission on the Discord server, or the owner doing the invite for you.
• A rough idea of your categories. Two or three is plenty to start. "General help", "Report a player", "Billing" beats a single catch-all.
• A staff role that already exists. Do not create a new one for the bot; use the role your team already has.

Step 1: Invite the bot with the right permissions

The permissions that actually matter for a ticket bot:

The common mistake is inviting with a stripped permission set to be cautious, then spending an hour debugging why tickets do not open. Grant the set above, and restrict by channel afterwards if you want to.

Our permissions guide covers each failure by symptom if something is already broken.

The shortcut: one command instead of steps 2 to 4

Before the manual walkthrough, the short version. On AI Ticket Bot, /setup builds the whole thing in one go: a panel, sensible categories, the staff role wiring and the permissions, then tells you what it created and links you straight to it.

Two things happen when that panel goes live that are worth knowing in advance. Members can immediately open tickets, and your server's 14 days of Premium start, automatically, with no payment method at any point. It ends by itself and the server drops back to the free plan with nothing deleted.

The rest of this guide is the manual version, which is also what you want if you are setting up a different bot.

Step 2: Create your ticket panel

A panel is the message with the button members press. Put it somewhere obvious. The two placements that work:

• A dedicated #support or #open-a-ticket channel, near the top of your channel list.
• Pinned in your existing #help channel, if you already have one members use.

What does not work: burying it in a rules channel nobody scrolls, or a channel only members with a specific role can see, when the people who need support are usually the ones without roles.

You also choose channel mode or thread mode. Channel mode creates a private channel per ticket and is what most servers want; it is familiar and staff can scroll back. Thread mode keeps things tidier in large servers, but threads archive.

Step 3: Add categories

Categories are the buttons on your panel. Each one can route to different staff and behave differently.

Keep the list short. Every extra button is a decision you are asking a confused member to make before they can ask their question. Three is usually right, five is the ceiling.

Use the description on each category to pre-answer the first question in it. A "Billing" category whose description reads "refunds within 14 days, have your order ID ready" removes the first two round trips from every billing ticket even when a human still handles it.

One thing worth knowing: routing is deterministic. The member picks a category and that decides which staff role gets involved. The AI does not silently re-route tickets somewhere else, which means what you configure is what happens.

Step 4: Wire your staff roles

Give your existing staff role access, then set what it can actually do. Granular permissions matter more than they look:

On AI Ticket Bot that is fourteen permissions in four groups, and /staff roles opens the whole thing on one card. Four ready-made sets get a role working in one tap, so you only go permission by permission when you want to.

The four that are worth thinking about hardest are the ones that reach beyond a single ticket: reading transcripts, seeing stats, teaching the AI, and managing the blacklist. A new role gets none of them by default.

There is a role hierarchy guard on unclaiming, so a junior staff member cannot yank a senior's claimed ticket.

Step 5: Turn on transcripts

Transcripts save the conversation when a ticket closes and give you a link. Turn them on before you need them, not after an argument about what someone was told.

Retention is plan-bound: 90 days on the free plan and 730 days on every paid plan. If you ever need to audit a support conversation, that number is the one to check, not whether transcripts exist. There is also a server-wide switch to turn transcripts off entirely, on every plan, if your community would rather nothing were retained. Our transcripts guide covers the privacy side.

Step 6: Open a test ticket yourself

Do not skip this. Open a ticket from a second account, or ask a staff member to.

Five minutes here saves a week of members quietly failing to get help.

The step most servers skip

If your ticket bot has AI, teach it before you announce it. A bot that has been told nothing will politely escalate every single ticket to your staff, which is worse than no bot at all, because now there is an extra step.

With AI Ticket Bot this is the /ai train command. You state the answer in plain language, or paste a URL, which it crawls through the site's sitemap rather than reading a single page, or attach up to ten files per message. Five minutes of feeding it your most repeated answers is the difference between a bot that resolves tickets and a bot that files them.

Start with the five questions your staff are sick of answering: your refund window, your rules, how to get a role, your hours, where the download link is. We wrote a full guide to training that covers what makes a fact usable versus useless.

How long should this take?

About ten minutes for the mechanical setup, plus however long you spend on categories and training. With a one-command setup it is closer to two. Any bot claiming a thirty-second setup is describing the invite, not the configuration.

Common setup mistakes