How to set up a ticket bot on Discord
A ticket bot gives every request its own private channel. A member presses a button, a channel opens for them and your team, and when the matter is settled the channel closes and a transcript is kept. On SCNX there are two ways to run them: a free module of your bot, and Support Bot for larger teams.
Updated 2026 m. lapkričio 18 d.12 min read
On this page
The short version
- Members open a ticket with a button under a message you write.
- The ticket module of your bot is free and takes about ten minutes to set up.
- Support Bot adds claiming, topics, forms and auto-close, and is part of our paid plans.
What you need
- Your own bot on SCNX. Creating one takes about two minutes
- A category for ticket channels and a text channel for the ticket message
- A staff role and a private channel for transcripts
- For Support Bot: one of our paid plans and a second Discord application
Two ways to run tickets on SCNX
SCNX has two ticket systems. The first is the ticket module of your bot. It is free, lives in the same bot as your welcome messages and levels, and does the core job: button, private channel, transcript.
The second is the ticket system of Support Bot. Support Bot is a separate bot that only does support, built for teams that share a queue.
| Ticket module | Support Bot | |
|---|---|---|
| Runs on | Your bot, as a module | A second bot with its own name |
| Plan | Every plan, including our free Starter plan | Our paid plans |
| Opening a ticket | Button under a message | Button, dropdown menu or /ticket open |
| Several kinds of tickets | One message and button per category | Ticket topics in one message |
| Claiming | No | Yes |
| Forms before a ticket | No | Yes |
| Closing inactive tickets | By hand | Automatic, with an optional warning |
| Adding other members | No | /ticket users add |
| After closing | Transcript link in your log channel | Log with optional AI summary, star ratings from members |
Start with the ticket module if one or two people answer tickets and a handful come in per week. Move to Support Bot when two moderators keep answering the same ticket, when requests need to reach different teams, or when you want members to fill in a form before a channel opens.
You can run both at the same time, but members are better served by one place to ask.
Prepare your server
Both systems need the same things in Discord. Create them first, because the dashboard only lets you pick channels and roles that already exist.
Create a category for tickets
Every ticket becomes a channel inside it. Give the bot Manage Channels in this category, otherwise it cannot create or delete ticket channels. Keep other channels out of it: a Discord category holds 50 channels at most.
Create a channel for the ticket message
Something like #support, as a normal text channel. Take away the permission to send messages for @everyone so the message with the button stays the only thing in it.
Create a private log channel
This is where the bot posts a summary of every closed ticket with the link to its transcript. Only your team should see it. The bot needs View Channel, Send Messages and Embed Links there.
Decide which role answers tickets
A role like Moderator or Support. Its members are pinged for every new ticket and can read all of them, so keep it to people who should see private requests.
Option 1: Set up the ticket module
Switch on the module
Open Modules in the Discord-Bot section of your dashboard, find Ticket-System and switch it on. Save your changes. The bot reloads once.
Open the configuration
Click Open configuration on the module, or go straight to the ticket configuration. Every entry in it is one ticket category. If the list is empty, click Add new Ticket-Category.
Fill in the ticket category
Set Ticket create category to your tickets category, Ticket creation channel to #support, Ticket Roles to your staff role and Log channel to your log channel. The next section explains every field.
Write the ticket message
Ticket created message is what members read above the button. Say what tickets are for and what to include, for example an order number or a screenshot. One or two sentences are enough.
Save and reload
Save. The dashboard asks whether to reload your configuration. Confirm with Reload configuration now. The bot then posts the ticket message with its button in the channel you picked.
Test it with a second account
Press the button as a normal member. Check that the channel opens in the right category, that your staff role is pinged, and that closing it puts a transcript in your log channel.
Illustration. The real interface may look different.
For separate tickets for ban appeals and general questions, add a second ticket category. Every category posts its own message with its own button and has its own staff roles and log channel. Several categories cannot share one message.
What each setting does
| Setting | What it does and what to pick |
|---|---|
| Name | The name of this kind of ticket, for example Support or Ban appeal. It shows up in the ticket and in the log. |
| Ticket create category | The Discord category new ticket channels are created in. |
| Ticket creation channel | The text channel where the bot posts the message with the button. On every reload the bot edits that message, so you can change the text later without ending up with two. |
| Ticket Roles | These roles are pinged in every new ticket and can read and write in it. Leave it empty and nobody is notified. |
| Copy category permissions | Off by default. When on, a new ticket copies the permission overwrites of the category, and @everyone still cannot see it. Useful if a role should read every ticket without being pinged. |
| Log channel | Where the summary of a closed ticket goes, with the transcript link. If you leave it empty, the bot uses its general log channel. |
| Send log messages silently | Posts the log message without a notification sound. |
| Ticket created message | The message above the button in the ticket creation channel. |
| Send user DM after ticket is closed | Off by default. When on, the member gets a DM after the ticket closes. Worth switching on, because the ticket channel is gone by then. |
| User DM | The text of that DM. %transcriptURL% inserts the link to the transcript, %type% the name of the category. |
| Ticket-Created Message | The first message inside a new ticket. |
| Ticket create button, Ticket close button | The labels of the two buttons. The defaults are Create ticket 🎫 and ❎ Close ticket. |
The default texts come in the language of your bot. If they show up in English on a German server, change the bot's language in its settings.
What members and your team see
A member presses the button and gets a reply only they can see, with a link to their new channel. The channel carries their username. They can have one open ticket per category: pressing the button again points them to the one they already have.
Inside, the bot posts the first message, pings your ticket roles and pins the message. Only the member, your ticket roles and the bot can see the channel. Everyone in it can attach files and post links.
Illustration. The real interface may look different.
The Close ticket button sits under that first message. The member and your staff can both press it. The bot then locks the channel, writes the transcript, posts the summary in your log channel and deletes the channel about 20 seconds later.
The transcript is a link to an encrypted page. Attachments are not part of it, so save important files before closing.
A closed ticket cannot be reopened. The member opens a new one.
Tickets from a right-click
The module adds two commands to Discord's right-click menu for messages. Create Ticket About Message opens a ticket about the selected message and quotes it in the ticket, which is handy when a member wants to report something another member wrote. It uses your first ticket category. Close Ticket closes the ticket you are in and needs the Manage Channels permission.
Both are switched off by default. Turn them on in Commands on the Message tab, save, and reload the configuration. Members then find them by right-clicking a message and opening Apps.
Option 2: Set up the Support Bot ticket system
Support Bot runs as its own bot next to the one you already have. It needs one of our paid plans and its own Discord application. Do not reuse the token of your first bot.
Create a second application
Open the Discord Developer Portal and click New Application. Open Bot in the menu on the left, click Reset Token and copy the token. Only ever paste it into the SCNX dashboard.
Create the Support Bot
Open the Support Bot setup in your dashboard, paste the token and click Create Support Bot. SCNX checks the token and sets up the hosting.
Invite the bot
Click Invite Bot to Server, pick your server in Discord and authorize. The setup continues by itself once the bot has joined.
Choose the Ticket System
The setup asks How would you like to support your community? Select Ticket System and continue. Modmail is another mode, where members write to the bot by DM. You can switch it on as well, now or later.
Fill in the basics
Under Set Up Ticket System, pick your Staff Roles, the Ticket Category and the Log Channel. Under Ticket Open Message, pick the channel for the message, set the Button Label and write the text members read above it. Click Save & Continue.
Add what your team needs
The next screen, Want to take it further?, offers Ticket Topics, Claiming, Support Feedback, Forms and Opening Hours. Each can also be set up later from the dashboard. Finish with Go to Dashboard.
- Ticket Topics
- Members choose a topic when they open a ticket. Each topic can have its own category, staff roles, ticket message and required form. Add them under Ticket Topics with Add Ticket Topic.
- Ticket Claiming
- A moderator takes a ticket with a button, and the others see that it is handled. You can lock the channel until someone has claimed it. Set it up under Ticket Claiming.
- Forms
- Ask for the order number or the username before the conversation starts. A form can be required per topic, or sent into a running ticket with
/ticket form. Create them under Forms. - Auto-close
- Tickets without activity close by themselves after a time you set. The bot can warn the member before it happens.
Illustration. The real interface may look different.
From here on your team works in ticket channels much like before, with more tools at hand. These are the parts most teams switch on first.
Support Bot commands for your team
A command only shows up when its feature is switched on and the person has permission for it.
| Command | What it does |
|---|---|
| /ticket open | Opens a ticket without the button, if you allow members to open tickets by command. |
| /ticket admin-open | Staff open a ticket with a member they select. |
| /ticket close | Closes the ticket. The button under the ticket message does the same. |
| /ticket schedule-close | Closes the ticket after a set time. |
| /ticket hold | Pauses a ticket that waits on someone else. Auto-close stops and the channel is locked until you run the command again. |
| /ticket transfer | Moves the ticket to another topic and releases it for claiming. |
| /ticket users add | Gives another member access to the ticket. /ticket users remove takes it away. |
| /ticket rename | Changes the name of the ticket channel. |
| /ticket form | Sends one of your forms into the ticket. |
| /blocklist add | Blocks a member from opening tickets, with an optional reason and duration. |
When something does not work
- The ticket message does not appear
- Reload the configuration after saving. Check that Ticket creation channel is a normal text channel the bot can see and write in. If the bot cannot find the channel, it disables the ticket module.
- Pressing the button does nothing or shows an error
- The bot needs Manage Channels in the ticket category. Also count the channels: a category holds 50 and a server 500. Old tickets that were never closed fill a category quickly. On our free Starter plan, also check that the bot is online. A short ad video every 14 days keeps it running.
- Nobody is pinged in new tickets
- Ticket Roles is empty for that category. The first message in the ticket then says that no pings are configured.
- No transcript shows up
- Set a Log channel for the category and give the bot View Channel, Send Messages and Embed Links in it.
- A member says they cannot open a ticket
- They most likely have one open already in the same category. The bot tells them so and links it. Close the old ticket first.
- The texts inside the ticket are in the wrong language
- Those are the default texts, and they follow the language of your bot. Change the bot's language in its settings.
Other ways to do it
There are bots that do nothing but tickets, and several of them are good. You invite them and configure them on their own dashboard. What you take on is another bot in your member list with someone else's name, and another place to maintain settings. Check which features their free version includes, transcripts in particular.
Writing it yourself is a reasonable first project in discord.js: on a button press, create a channel with permission overwrites for the member and your staff role. Transcripts and hosting are the parts that take longer than expected.
Common questions
- Is the ticket bot free?
- The ticket module is part of your bot and free on our Starter plan, with several ticket categories if you want them. Support Bot, the larger system, is part of our paid plans.
- Can I have more than one kind of ticket?
- Yes. In the ticket module you add a ticket category for each kind, and each one posts its own message with its own button. In Support Bot you create ticket topics, and members pick one when they open a ticket.
- Who can close a ticket?
- In the ticket module, the member who opened it and your staff, with the Close ticket button under the first message. In Support Bot, your staff close tickets with the button or
/ticket close, and you decide whether members may close their own. - Are closed tickets kept?
- The channel is deleted and the transcript stays. The ticket module posts the link to it in your log channel, together with a summary of the ticket.
- Can a member have several tickets open?
- In the ticket module, one per category. With two categories a member can have two tickets open, one in each. Support Bot lets you set the limit yourself, for the whole system and per topic.
- Can staff add another member to a ticket?
- The ticket module has no command for it. A moderator can change the channel permissions by hand. Support Bot has
/ticket users add. - Can I move from the ticket module to Support Bot later?
- Yes. Set up Support Bot, test it, then switch off the ticket module and delete its old message. Close the open tickets of the module first, because the two systems do not share tickets.
- Can members open a ticket by DM?
- A ticket system works in channels on your server. For DMs, Support Bot has Modmail: members write to the bot by DM and your team answers from a private channel.
Start with a free bot
Log in with Discord, add your server and create your bot. The dashboard walks you through each step.
Get started for freeFree on our Starter plan. A short ad video every 14 days keeps the bot online.