# Vetox vs Tickets

> Tickets is a ticket specialist with no applications system at all. Vetox pairs free tickets with a free application reviewer sharing one question model.

- Canonical: https://discordbots.blog/blog/vetox-vs-tickets-bot
- Published: 2026-09-09
- Author: The Field Guide desk
- Competitor facts checked: 2026-08-31
- Sources:
  - tickets.bot (https://tickets.bot/) — checked 2026-08-31
  - tickets.bot — premium (https://tickets.bot/premium) — checked 2026-08-31
  - docs.tickets.bot — forms (https://docs.tickets.bot/dashboard/forms) — checked 2026-08-31
  - docs.tickets.bot — premium perks (https://docs.tickets.bot/premium/perks) — checked 2026-08-31
- Publication: The Field Guide, an independent site not affiliated with Discord Inc.

---
## The distinction that decides which bot you need

Tickets — the bot at tickets.bot, not to be confused with the now-dead `ticketsbot.net` it moved from
— is a single-purpose ticketing specialist, and it is the most helpdesk-shaped product examined in
this research: staff teams with per-team channel permissions, a knowledge base, tags, exit surveys and
a dashboard staff can reply from directly. What it does not have, at any price, is an applications
system — no submission queue, no accept-or-deny workflow, no role granted on a decision. Vetox treats
tickets and applications as one connected system with a shared question model, so a server running
staff recruitment or event sign-ups gets both a support queue and a review workflow from the same
dashboard. The question worth asking is whether tickets alone cover what the server needs, or whether
recruitment, sign-ups or a moderated submission process are also part of the job.

## How this comparison was built

Every capability and price below was read from Tickets' own site and documentation on 31 August 2026.
It is **not** weighted by install count or App Directory position — the comparison covers what each
free tier actually includes, what claiming and transcripts cost, and what happens once a server needs
more than a support queue.

## What Vetox covers

Vetox is a 41-system platform where tickets and applications share infrastructure rather than sitting
as separate products:

- **Tickets** — 3 panels with 200 concurrent tickets free on Starter, rising to 25 panels at Max.
- **Applications** — a free reviewer queue with filters, search, decisions and CSV export, plus a
  **completely free application analytics funnel**, on Starter.
- **8 question types and 14 workflow actions** across the application system.
- **Moderation, leveling, self-roles and giveaways** — all free or partly free on Starter.
- **40 games**, free on every tier.

## What Tickets does well

Tickets earns its reputation as the most helpdesk-shaped ticket bot examined in this research, and its
free tier is genuinely the strongest ticket-only tier found here. **Claiming, unclaiming and transfer
are free** — a workflow several competitors reserve for a paid tier — alongside **automatic
transcripts**, stored and searchable by ticket ID, username, closed-by, panel, star rating and
color-coded labels, with the ticket opener always DM'd a link to their own transcript on close. **Staff
teams** route specific panels to specific roles or individuals, with **ten individually toggleable
per-team channel permissions** — a level of access control not found documented anywhere else in this
category. Forms support **8 field types free**, including user, role, channel and mentionable selects,
plus a String Select whose options can be fetched live from an external API — the richest form field
support in the ticket category. The product is **MIT-licensed, open source and self-hostable**,
ships roughly 45 interface languages through a community CrowdIn project, and is actively developed
with public changelogs through March 2026.

**What is worth stating precisely:** these are ticket-open questionnaires, not applications. There is
no submission queue outside an open ticket, no accept-or-reject decision, and no role granted on a
result. The free tier caps at **3 ticket panels** and **1 panel with support hours**, the knowledge
base caps at 5 articles and 3 categories free, and statistics require voting on a bot list — a
recurring chore rather than a one-time unlock. Transcript retention is not stated anywhere in the
documentation, which a compliance-minded server cannot answer from public information.

## Where the two differ

| Category                        | Vetox                                             | Tickets (tickets.bot)                                                       |
| ------------------------------- | ------------------------------------------------- | --------------------------------------------------------------------------- |
| Free ticket panels              | 3                                                 | 3                                                                           |
| Free concurrent tickets         | 200                                               | Unlimited (no cap stated)                                                   |
| Ticket claiming                 | Free                                              | **Free** — claim, unclaim, transfer                                         |
| Automatic transcripts           | On Starter                                        | **Free, vendor-hosted, 8 search filters**                                   |
| Form field types                | 8 question types (application system)             | **8 field types**, including API-backed dropdown options                    |
| Applications system             | **Free reviewer queue + free analytics funnel**   | **Not offered** — forms attach to ticket opening only, no decision workflow |
| Per-team channel permissions    | Not offered                                       | **10 toggleable permissions per staff team**                                |
| Open source / self-hostable     | Not offered                                       | **Yes — MIT licensed**                                                      |
| Moderation, leveling, giveaways | 41 server systems, free or partly free on Starter | Not offered — single-purpose                                                |
| Entry paid price                | $4.99/mo Basic                                    | $2.99/mo Premium (per server)                                               |

## Pricing compared

Tickets' Premium is $2.99/month per server, billed through Patreon, and Whitelabel — a fully branded
instance — is $6.99/month per bot instance. Vetox's Starter tier is $0 and includes tickets and
applications together indefinitely; Basic is $4.99/month or $44.99/year, which raises ticket panels to
10 and unlocks form customization and priority; Max is $7.99/month or $69.99/year, raising panels to
25; Black, which adds AI, is $17.99/month or $149.99/year.

## What each gives you before you pay

Tickets' free tier is genuinely strong on workflow: unlimited concurrent tickets, free claiming,
automatic vendor-hosted transcripts, 8 form field types, and staff teams with per-team permissions, all
at $0. Vetox's free Starter tier matches the panel count at 3 but adds a system Tickets does not have
at any price: a full **application reviewer queue with filters, search, decisions, CSV export and a
free analytics funnel**. Of the ticket and application bots examined in this research, only one other
competitor has any application analytics at all, and none has it entirely free.

## Vetox's applications system in depth

Applications is not a bolt-on form — it shares the ticket system's question model and reuses the same
configuration surface, so a server does not learn two vocabularies for two systems. On Starter, the
free authoring allowance is narrow — 1 panel, 5 questions, 1 workflow action per stage, 1 apply
button — but the **reviewer surface is unrestricted from day one**: the full queue, filters, search,
accept-and-deny decisions, CSV export, and a complete analytics funnel tracking how many applicants
started, completed, and how they were distributed across outcomes. Eight question types and 14 total
workflow actions give a review process real shape — auto-deny rules, eligibility roles and role grants
on decision are available as the server moves up tiers, at Basic and Max. Because applications and
tickets share infrastructure, a decision on an application can feed directly into the same moderation
actions — kick, ban, timeout — the ticket system already uses, and a server running staff recruitment
does not need a second bot, a second dashboard, or a Google Form to get a real review workflow.
Tickets has no equivalent at any price; a server that wants both a support queue and a recruitment
pipeline currently needs two products to get what Vetox ships as one.

## Which to choose

**Choose Tickets if** support ticketing alone is the job — claiming, transcripts, staff teams and rich
form fields, all free, with an open-source and self-hostable option if you outgrow or distrust a hosted
service.

**Choose Vetox if** your server also runs staff applications, event sign-ups, or any submission process
that needs a decision and a role granted on the outcome — the reviewer queue and analytics are free,
and both systems share one configuration surface with everything else the platform runs.

## Frequently asked questions

**Does Tickets have an applications system?**
No — forms only attach to ticket opening. There is no submission queue, no accept-or-deny decision,
and no role change on a result, confirmed against its full documentation and command list.

**Is ticket claiming free on Tickets?**
Yes — claim, unclaim and transfer are all free, which several ticket bots in this category reserve
for a paid tier.

**How many ticket panels does each give free?**
Both give 3 free. Tickets does not publish a concurrent-ticket cap; Vetox caps at 200 free,
unlimited from Max.

**Does Vetox's application system cost anything?**
The reviewer queue, filters, search, decisions, CSV export and analytics are entirely free on
Starter. The authoring allowance — panels, questions, workflow actions — is narrow free and expands
at Basic and Max.

**Is Tickets open source?**
Yes — MIT licensed and self-hostable, a genuine option for a server that wants to run its own
instance rather than a hosted one.

**Which has richer ticket forms?**
Tickets — 8 field types including API-backed dropdown options is its own specialism in this category. Vetox's 8 question types serve the application system rather than ticket-open forms
specifically.

## Method

Every capability and price above was read from Tickets' own site and documentation on 31 August 2026.