New: sell roles. Bond takes no cut.

See how

Bond vs Ticket Tool and Tickets

Bond is a Ticket Tool alternative that sets up tickets from one message: a button in #support opens a private thread for the member and your Support team, with a close button and a log of closed tickets in a staff-only channel. Bond also runs the rest of the server. Ticket Tool and Tickets are two ticket bots with similar names, each set up on a web dashboard.

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

1M 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 52 permissions.

invite link in Discord's application record
Tickets

Asks for Administrator. 18 of 52 permissions.

invite link on invite.tickets.bot
Bond

No Administrator. 51 of 52 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.

Ticket ToolNo Administrator
9 of 52 permissionsinvite link in Discord's application record
TicketsAsks for Administrator
18 of 52 permissionsinvite link on invite.tickets.bot

Its docs say you can untick Administrator, as long as no channel category denies the bot's roles.

docs.tickets.bot/setup/invite
BondNo Administrator
51 of 52 permissions
  • 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

  1. 1Invite the bot and keep the permissions it asks for.
  2. 2Create or pick a Support Team role.
  3. 3Log in to the dashboard and open Panel Configs.
  4. 4Create a panel.
  5. 5Send the panel to a channel.
docs.tickettool.xyz/general/setup

Tickets

  1. 1Invite the bot.
  2. 2Make yourself an admin of the bot with /addadmin.
  3. 3Go to the web dashboard.
  4. 4Make a ticket panel.
  5. 5Back in Discord, add your staff with /addsupport.
docs.tickets.bot/setup/introduction

Bond

  1. 1Add Bond to your server.
  2. 2Mention @Bond and say what you want.
  3. 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. The free Tickets plugin posts the panel, opens a private thread per member for up to five staff roles, and puts a close summary and a transcript of the last 100 messages in a staff log. Anything it does not cover, you ask for in a sentence.

  • @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

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

Recorded 30 Oct 2026 on a test server · 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.

See the whole run

Where 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
  • Tickets has separate support teams for each panel, and collects user feedback ratings.tickets.bot

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, feedback ratings, full transcripts of long tickets or a channel per ticket.

  • You need the full transcript of long tickets. Bond's transcript covers a ticket's last 100 messages.
  • 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.