How to set up a Discord ticket bot

Open the invite link and choose your server from the dropdown. Discord will show the permissions being requested — leave them as they are. A ticket bot cannot work without Manage Channels and Manage Roles, because opening a ticket means creating a channel and giving specific people access to it.

One thing worth doing straight away: in Server Settings → Roles, drag the bot's role above your staff roles. Discord will not let a bot manage roles positioned higher than its own, and this is the single most common reason a ticket bot half-works.

Sign in with Discord. You will see every server where you have Manage Server and the bot is present; the rest are listed as invitable. Pick your server to open its configuration, which opens on Overview — empty for now, and the place your ticket counts and ratings will appear once things are running.

Go to Ticket Setup and enable Enable ticket system. Then, under Routing, choose the Discord category where new ticket channels should be created — the one you made earlier.

Two other switches on this card are worth a moment:

• Allow users to open multiple tickets at once — leave this off. One open ticket per person keeps conversations in one place and stops duplicates when someone gets impatient.
• Ask for a satisfaction rating when a ticket is closed — turn this on. It costs the member one click and gives you the only honest measure of whether your support is any good.

On the Staff & access card, set two things. Close ticket — required role controls who can close a ticket; leave it empty and anyone can, which is usually not what you want once a server grows. Dashboard ticket access — roles controls who can read and answer tickets from the dashboard rather than from Discord.

These are separate from the role that gets pinged for a given ticket, which you set per category in the next step. A small server points all of them at one staff role; a larger one gives each queue its own team.

A panel is the message members interact with: an embed with a dropdown of categories. Go to Ticket Panels and click Use a template. There are five — General support, Bug reports, Player reports, Partnerships and Billing — and each arrives with the embed text, three or four categories, and the questions worth asking before a channel opens, written in your server's ticket language. Most servers want General support first.

Then set the two things no template can guess. Open each category and pick the Role to ping when a ticket of that kind opens and the Discord category channel its tickets are created in. The panel list flags any category still missing one, so nothing gets posted half-configured.

Everything else is optional polish: rename a category, change its emoji, or edit its questions — each category can ask up to five, as text fields, dropdowns, checkboxes or an image upload, and the answers land in the ticket's first message so staff start with context instead of asking for it. The Panel / Form / Ticket preview on the right shows exactly what members and staff will see as you go.

Prefer to start from nothing? New panel gives you a blank embed and one empty category. Keep the list short either way — three or four categories that people understand beat ten that they guess at:

• General help — the catch-all, and it will be most of your volume.
• Bug report — routed to whoever can actually fix things.
• Report a member — moderators only, in a category the rest of staff cannot read.
• Partnership or business — routed to owners, and usually the quietest queue.

Save, then open the panel's Publish tab, pick the channel members will use — #support or #help — and post. The bot posts the embed and its dropdown, and that message is your ticket system as far as your community is concerned. When you change the panel later, the same tab offers Update message, which edits the posted message in place rather than posting a second copy.

Lock the channel so nobody can post in it. A panel channel with conversation in it stops working as a panel, because the panel scrolls away.

Use a second account, or ask a member of staff who is not an admin — admins see everything, so testing as one proves nothing about permissions. Then check the whole loop:

• The ticket channel is created in the right category, and @everyone cannot see it.
• The correct staff role was pinged.
• Staff can reply with /ticket reply, and the member sees it.
• Closing with /ticket close archives the channel and produces a transcript.
• The satisfaction prompt appears, and the rating lands on your Overview.

Now announce it.