Bond vs Ticket Tool and Tickets
Ticket Tool and Tickets are two different bots with similar names, and both do support tickets. Each is set up on a web dashboard. Bond sets up tickets from one message in Discord, as private threads, and does the rest of the server too.
We build Bond. Every price, limit and setup step below about Ticket Tool and Tickets comes from their own public pages.
Checked 2 Oct 2026 on both bots' own pages
Side by side.
- Where you set it up
- Ticket Tool
A web dashboard for panels, plus chat commands.
docs.tickettool.xyz - Tickets
A web dashboard, which its docs recommend, or slash commands.
docs.tickets.bot/setup/introduction - Bond
In Discord, in plain words. Bond lists each change and asks before it makes it.
- Free
- Ticket Tool
Unlimited panels, transcripts and support roles, with 10 tickets a minute.
tickettool.xyz/premium - Tickets
Unlimited tickets, forms and claiming. 3 panels.
tickets.bot/premium - Bond
600K tokens a week. Every tool works on it.
- Paid
- Ticket Tool
Premium adds unlimited tickets, full customization, ticket claiming and automatic closing. We could not read a fixed price on the page.
tickettool.xyz/premium - Tickets
Premium is $2.99 per server a month: unlimited panels, autoclose, exit surveys. Whitelabel is $6.99 a month.
tickets.bot/premium - Bond
From $7.99 a month, for a larger allowance and Ultra.
- Invite
- Ticket Tool
No Administrator. 9 of 51 permissions.
invite link in Discord's application record - Tickets
Asks for Administrator. 18 of 51 permissions.
invite link on invite.tickets.bot - Bond
No Administrator. 50 of 51 permissions.
| Ticket Tool | Tickets | Bond | |
|---|---|---|---|
| Where you set it up | A web dashboard for panels, plus chat commands. docs.tickettool.xyz | A web dashboard, which its docs recommend, or slash commands. docs.tickets.bot/setup/introduction | In Discord, in plain words. Bond lists each change and asks before it makes it. |
| Free | Unlimited panels, transcripts and support roles, with 10 tickets a minute. tickettool.xyz/premium | Unlimited tickets, forms and claiming. 3 panels. tickets.bot/premium | 600K tokens a week. Every tool works on it. |
| Paid | Premium adds unlimited tickets, full customization, ticket claiming and automatic closing. We could not read a fixed price on the page. tickettool.xyz/premium | Premium is $2.99 per server a month: unlimited panels, autoclose, exit surveys. Whitelabel is $6.99 a month. tickets.bot/premium | From $7.99 a month, for a larger allowance and Ultra. |
| Invite | No Administrator. 9 of 51 permissions. invite link in Discord's application record | Asks for Administrator. 18 of 51 permissions. invite link on invite.tickets.bot | No Administrator. 50 of 51 permissions. |
What each invite asks for.
Read from each bot's public invite link. Administrator lets a bot pass every channel permission you set, so it is marked on its own.
Its docs say you can untick Administrator, as long as no channel category denies the bot's roles.
docs.tickets.bot/setup/invite- Asked for
- Administrator
- Not asked for
Bond's invite is wide because its tools cover channels, roles, moderation, events and voice. It leaves out Administrator, so a channel that denies Bond's role still blocks it.
Setup, step by step.
Each bot's steps are the ones in its own docs.
Ticket Tool
- 1Invite the bot and keep the permissions it asks for.
- 2Create or pick a Support Team role.
- 3Log in to the dashboard and open Panel Configs.
- 4Create a panel.
- 5Send the panel to a channel.
Tickets
- 1Invite the bot.
- 2Make yourself an admin of the bot with /addadmin.
- 3Go to the web dashboard.
- 4Make a ticket panel.
- 5Back in Discord, add your staff with /addsupport.
Bond
- 1Add Bond to your server.
- 2Mention @Bond and say what you want.
- 3Approve the changes it lists.
The same kind of job, run by Bond.
Bond's tickets are one part of a bot that also handles channels, roles, moderation and automation. You ask for the panel in a sentence, Bond shows what it will create, and a ticket opens as a private thread inside your support channel.
@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 #support, afterwards
Need help? Press the button and a private thread opens for you and the team.
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.
In the private ticket thread
@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.
Hi, it was order 4417, placed last Monday.
Ticket closed. The summary and transcript are in #ticket-log.
Only you can see thisDismiss message
In #ticket-log, staff only
Recorded 28 Sept 2026 on a test server · Light tier · 1 message · 24 seconds · 155K 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 3 of the Tickets plugin, which is now on version 4. Version 4 adds everyone who holds the support role to each new ticket directly, where the recorded version relied on the role mention in the ticket's first message. A ticket whose thread is deleted no longer counts against the member's open-ticket limit. The setup and the panels shown above are unchanged.
See the whole runWhere Ticket Tool and Tickets go further.
Ready-made features Bond has no packaged version of. Some Bond can build as an automation. Some it cannot do at all.
- Ticket Tool opens each ticket as a private channel. Bond's tickets are private threads.docs.tickettool.xyz
- Ticket claiming, so one staff member takes a ticket. It is on Tickets' free plan.tickets.bot/premium
- Both save a transcript of each closed ticket. Bond's transcript lists who wrote and when, without the text of members' messages.tickets.bot
- Tickets has separate support teams for each panel, and collects user feedback ratings.tickets.bot
- Tickets sells a whitelabel bot with your own name and avatar.tickets.bot/premium
And if you do switch, in three moves.
Both bots can run at once. There is no import step and nothing to migrate.
Add Bond alongside
Ticket Tool keeps doing exactly what it does today. Bond joins without touching a single existing setting.
Move one thing across
Pick the part you like least. Describe what it does to Bond, approve the changes, and watch it run for a week.
Turn the old one off
Only once the new one has run. Repeat for the next part, or stop here and keep both.
When to stay on Ticket Tool or Tickets.
Stick with Ticket Tool or Tickets if tickets are the one job you need a bot for, and you want claiming, full transcripts or a channel per ticket.
- You need full transcripts with what members wrote. Bond cannot read that text.
- Your staff claim tickets, or you route panels to different support teams.
- You want each ticket to be its own channel, which is how Ticket Tool opens them.
- You want a bot that asks for as little as possible. Ticket Tool's invite asks for far fewer permissions than Bond's.
Both are good at support tickets opened from a panel, and there is no prize for switching a tool you are happy with. Add Bond for the jobs a ticket bot does not cover, and leave the rest where it is.
Sources.
Every statement about Ticket Tool and Tickets on this page was read at one of these on 2 Oct 2026, and each invite link was read the same day. Prices and limits change, so check the page before you decide.
Try Bond on one thing this week.
Free to start, and nothing you have set up in Ticket Tool changes when you add it.