New: sell roles. Bond takes no cut.

See how

How to make a ticket system in Discord

Add Bond, an AI Discord bot, and ask for tickets in one message. It installs a Tickets panel, a button in your support channel that opens a private thread for the member and your support team, with a close button and a summary in a staff-only log. Discord has no tickets of its own, and a support forum shows every post to everyone who can see it.

Verified 30 Oct 2026 on a test server · build b5ebc87

In Discord, without a bot.

Discord has no tickets. The nearest built-in shape is a forum channel, where each question is its own post.

  1. Right-click the channel list, Create Channel, choose Forum, and name it support.
  2. In Edit Channel, Permissions, let @everyone View Channel, Create Posts and Send Messages in Posts.
  3. Under the forum's Tags, add tags such as Open and Solved, so staff can filter what still needs an answer.
  4. Staff answer in each post, tag it Solved, and close it from the post's menu.

A forum post is public to everyone who can see the forum, so members cannot raise anything private there. A private ticket, one thread only the member and your team can read, needs a bot. Bond is an AI Discord bot that builds one from a single message, as the run below shows. For bots that only do tickets, see Bond vs Ticket Tool and Tickets. For the open help channels a support server runs beside its tickets, see the support server layout.

With Bond, in one message.

A real run, recorded on a test server: what was asked, what Bond asked you to approve, what it did, and what members saw afterwards.

  • @Bond Set up a ticket system: a button in #support that opens a private thread for the member and the Support team, and a log of closed tickets in a staff-only channel.

In #admin-chat

admin-chat
Y
you30 Oct 2026

@Bond Set up a ticket system: a button in #support that opens a private thread for the member and the Support team, and a log of closed tickets in a staff-only channel.

BondAPP30 Oct 2026

Install a plugin

for @You

Always allow stops asking about installing plugins · Expires in 10 minutes

Allow onceAlways allowDeny
BondAPP30 Oct 2026

Update permissions for @Support on #ticket-log

for @You

Allows View Channel and Read Message History. For @Support on #ticket-log.

Allow for this request covers Bond's other routine changes for this message. Anything bigger still asks.

Always allow stops asking about channel permission changes · Expires in 20 minutes

Allow for this requestAllow onceAlways allowDeny

What Bond did

Set up a ticket system: a button in #support that opens a private thread for the member and the Support team, and a log of closed tickets in a staff-only channel.

The ticket system is set up with the Tickets plugin.

  • Panel: posted in #support (#support) as a pinned message (ID 100000000000000022). It has one "Open ticket" button, which opens a form asking "What do you need help with?"
  • Tickets: each one is a private thread named ticket-<member>, with the member and the Support team added. A member can have one open ticket at a time.
  • Closing: the Close ticket button locks and archives the thread and posts a summary with a transcript in the log.
  • Log: #ticket-log (#ticket-log) is hidden from @everyone. The Support role can view it, and so can Bond and admins.
  • Support role: I created @Support (ID 100000000000000021) for the team. Add members to it so they receive tickets.

I also gave the Support role view and read-history access to #ticket-log. The installer had left it out, so without this the team could not have read the log.

Nothing has been tested yet. Try the button in #support with a test account to confirm a ticket opens, then close it to check the log entry.

Tip: if you want separate ticket types, such as bug reports or player reports, I can add them to the panel, each with its own button and team.

In #support, afterwards

support
BondAPP30 Oct 2026

Need help? Press the button and a private thread opens for you and the team.

Open ticket
BondAPP30 Oct 2026

Your ticket is open: #ticket-You

Only you can see thisDismiss message

What Open ticket asks

New ticket

What do you need help with?

My order never arrived and I would like a refund.

CancelSubmit

In the private ticket thread

ticket-You
BondAPP30 Oct 2026

@You @Support

Thanks for reaching out. Someone from the team will be with you soon.

My order never arrived and I would like a refund.

Close ticket
Y
you30 Oct 2026

Hi, it was order 4417, placed last Monday.

BondAPP30 Oct 2026

Ticket closed. The summary and transcript are in #ticket-log.

Only you can see thisDismiss message

In #ticket-log, staff only

ticket-log
BondAPP30 Oct 2026

Ticket closed: ticket-You

My order never arrived and I would like a refund.

Opened by

@You

Closed by

@You

Open for

1 min

Messages

2

Thread

#ticket-You

ticket-You.txt

Light tier · 1 message · 30 seconds · 58K tokens

Recorded on a Bond test server on the Light tier, the tier every free plan runs on. Server, channel and member IDs are placeholders, the test bot is shown as Bond, and the steps where Bond loads its own tools or pages through a long result are left out. The test server has no plan limits, so the plan limits a step reports are left out. The Always allow line on each approval card is reworded in plain words.

Recorded on version 5 of the Tickets plugin, which is now on version 9. Version 6 lets the support role view and read the #ticket-log the install creates, so Bond no longer has to add the role there afterwards, as it did in this run. A log channel you name yourself is left as it is. Version 7 lets up to five roles handle tickets instead of one, such as Support and Moderator. Each new ticket pings every one of them and adds their members, any of them can close it, and the #ticket-log the install creates lets each of them read it. A ticket kind can have its own team of up to five roles too. Version 8 changes nothing a member sees. It only records what was already true: Bond takes no requests inside a ticket. Version 9 adds Bond answers first, off until you turn it on, for every ticket or for one kind. A ticket it covers opens without pinging the team: Bond answers the member who opened it from your FAQ, rules, pins and past staff answers, at most 5 times a ticket, and pings the team when it can't help or the member asks for a person. It stops for good once staff write in the ticket.

Bond asked twice, and the recording pressed Allow once each time: to install the plugin, and then to let the Support role view and read #ticket-log. The test server already had #support, so Bond put the panel there and pinned it. It had no log channel and no Support role, so the install made the staff-only #ticket-log and a new Support role, and every ticket adds that role. The new log let in Bond but not the Support role, so Bond added the role there itself. After the install the same test account played the member: it opened a ticket through the form, wrote in it and pressed Close. That account is a bot, and the summary's Messages line names who wrote but leaves bots out, so here it is a count with no names. This page shows the transcript file's name and not what was in it.

The permissions it takes.

Bond checks every step against your own Discord permissions and role position before it acts, and what it reads back is only what you can already see.

What you need

  • List channelsNothing extra
  • List rolesNothing extra
  • List pluginsNothing extra
  • List flowsManage Server
  • Install pluginAdministrator
  • List channel permissionsManage Roles in that channel
  • Set channel permissionsManage Roles in that channel

Installing takes Administrator, the same bar as any automation, because an automation goes on acting as Bond long after you asked for it. Bond itself never needs Administrator.

What Bond needs

The tickets open and close as Bond, not as whoever installed them, so these are Bond's own permissions in each channel. Bond's invite grants all of them, and a channel's own permissions can still deny Bond's role there.

  • In #support: View Channel and Send Messages to post the panel. Create Private Threads and Send Messages in Threads to open each ticket: a ticket is a private thread, so Create Public Threads alone does not open one. Read Message History for the transcript, Manage Messages to take the Close button off, and Manage Threads to add your support team to each ticket and to lock and archive a closed one.
  • In the log channel: View Channel, Send Messages, Embed Links for the summary and Attach Files for the transcript.
  • A staff-only log channel has to let Bond's role in. The one the install creates does, as #ticket-log did in this run, and it lets your support role read it too. If you name a channel of your own that Bond cannot use, Bond refuses it and names the permission it lacks there.

What to watch for.

  • Bond adds everyone who holds one of the support roles to each new ticket, and its first message mentions each role, so the whole team is pinged for each new ticket. With Bond answers first on, the team is pinged only when Bond hands the ticket over.
  • If Bond cannot add some of the team, for example on a very large support role, the ticket still opens and the other roles are still added. The role mentions are their way in, and the close summary says how many were left out.
  • The support team has to be a role members can be given. Bond refuses its own role, or any other role Discord keeps for an app or for boosts, because such a role would add nobody to a ticket.
  • The install never makes a second channel or role with a name your server already uses. If you already have a Support role or a #ticket-log, Bond uses the one your request names, or asks you which to use.
  • A ticket's transcript holds its last 100 messages, each with its text, who wrote it and when. Older messages in a long ticket are not in it. A member who ran /opt-out still appears with who and when, but their text is left out of the transcript and the summary.
  • A member can have one open ticket at a time by default, and you can raise that to five.
  • A ticket nobody writes in is archived after 24 hours by default. You can set anything from one hour to seven days.
  • A ticket is for the member and your team, and Bond takes no requests inside one: a member who mentions it there is told to mention it in a text channel. With Bond answers first on, Bond answers only the member who opened the ticket, only until staff write, and only from your FAQ, rules, pins and past staff answers. While it is answering, a mention of Bond by anyone else in that ticket gets no reply. It never changes the server from a ticket.
  • Installing the plugin needs Administrator. Changing its settings later needs Manage Server.
  • The Tickets plugin does not use any of your automation slots. A server without a plan can have 5 plugins installed.

Questions people ask.

  • Why a private thread and not a channel per ticket?

    A thread keeps every ticket inside #support instead of adding a channel for each one, and it archives itself when it goes quiet. Only the member, the support team and anyone with Manage Threads can see a private thread.

  • Can staff see every ticket?

    The support role is added to every ticket, and anyone with Manage Threads can open any private thread. Closed tickets stay in #support as archived threads, and each close posts a summary and a transcript in the log channel.

  • Who can close a ticket?

    By default the member who opened it or anyone on the support team. You can limit closing to the support team.

  • Does Bond read what members write in tickets?

    Yes, at set points. Bond keeps the reason a member types into the ticket form, posts it at the top of the ticket, and quotes it in the close summary. With Bond answers first on, it reads the opener's messages as they arrive, to answer them, and never answers a member who ran /opt-out. When the ticket closes, it reads the thread's last 100 messages to count each person's messages, quote the last words and write the transcript; a member who ran /opt-out is still counted, but their text stays out of both. When staff press Save as FAQ on a close summary, it reads the ticket to fill the answer from the presser's own reply or the newest staff reply, never the member's words, and leaves out a staff member who ran /opt-out.

  • Is it free?

    Yes. Every tool works on the free plan. Setting it up uses tokens from your weekly allowance, and a free account gets 1M tokens a week. Opening and closing tickets uses none. With Bond answers first on, 25 answers a week are free. After that, answers use your Server plan's weekly tokens, then your server's token packs. With no Server plan, or once its weekly tokens and the server's token packs run out, Bond hands each new ticket straight to your team, with a ping, until the week resets on Monday at 00:00 UTC or the server has tokens again.

Ask for it in your own words.

Free to start. Bond never needs Administrator, and it shows you what it is about to change before it changes it.