What Happened to TicketsBot? The Shutdown Explained, and What to Use Now
TicketsBot went permanently offline on 5 March 2025, and ticketsbot.net no longer loads. What happened, what to do if it is still in your server, what became of your data, and how to replace it.
Tickety TeamNovember 21, 20265 min readIf you have typed ticketsbot.net into your browser recently and got nothing back, you are not alone. Tickets, the bot most people call TicketsBot, was one of the most popular ticket bots on Discord for years. It was discontinued on 5 March 2025, and the bot went permanently offline that day.
This page explains what happened, what it means if the bot is still sitting in your server, what became of your data, and how to replace it without losing a week of support.
What happened to TicketsBot
In early 2025 the creator announced that Tickets would be shut down. Their explanation was simple: despite a team of volunteers helping with support, the bot itself was essentially run by one person, and they no longer had the time to keep it maintained and up to date with Discord's changes.
The shutdown was handled carefully. Here is the timeline, from the official announcement page:
| When | What happened |
|---|---|
| Early 2025 | The shutdown was announced. Billing was switched off, so nobody was charged again. |
| Before the shutdown | A data export tool let server owners download their transcripts, server data and bot configuration. |
| 5 March 2025 | The main bot went permanently offline. Monthly premium had been extended free until this date. |
| After 5 March 2025 | Annual subscribers had been moved to whitelabel bots, which kept running until their subscription expired, up to a year later. Pro rata refunds went to the newest subscribers. |
| Today | The ticketsbot.net website, its dashboard and the export tool no longer respond. |
That last whitelabel detail explains a question we still see: if your server's own branded Tickets bot stopped working some time in early 2026, that is when its paid year ran out.
If TicketsBot is still in your server
A lot of servers never removed it. It shows up as an offline member, and its old panels still sit in your channels looking like they work. They do not: pressing a button gives members "This interaction failed", and they conclude your staff are ignoring them.
- Delete the old panel messages so nobody presses them.
- Remove the bot from your member list, or under Server Settings, then Integrations.
- Clean up the leftovers. Check your ticket categories for old ticket channels, and delete the bot's role once the bot is gone.
- Fix your links. Rules, FAQs and pinned messages that point members at the old panel or the old dashboard now lead nowhere.
What happened to your data
The export tool was the way to keep your transcripts and settings, and it was available before the shutdown. In November 2026 we could not reach the website, the dashboard or the export tool. If you did not export at the time, assume that data is no longer available. Transcript links saved in your log channels point at a domain that no longer responds.
Your settings are easier to rebuild than they sound. Most servers had one or two panels, a few support roles and a short form, which takes minutes to recreate in any modern ticket bot.
Is there a TicketsBot v2?
Sort of. The original code was released as open source, and the announcement mentioned that one of the old team's admins had started a new instance of the bot from it. That project carries on today as a separate bot, often called Tickets v2. It is not the original bot: you invite it fresh, it is run by different people, and the original team is not behind it.
The open source code also means you could host the bot yourself. The original announcement was honest that this suits people comfortable running a Kubernetes cluster, not a server owner who just wants tickets to work.
What to look for in a replacement
TicketsBot did nothing wrong in how it shut down. It gave notice, an export and refunds. But the reason it shut down is worth learning from: a bot that your community depends on should not depend on one person's free time. When you choose a replacement, check:
- Who runs it, and what happens to your server if they stop.
- Where your transcripts live, and what happens to them if you remove the bot or the bot goes away.
- What the free plan covers. Claiming, transcripts and forms are the basics of a ticket bot, and you should not have to pay for them.
- Whether it is still being built. Look for recent updates, not a changelog that stopped two years ago.
Moving from TicketsBot to Tickety
Tickety is a ticket bot used in over 250,000 servers, it ships updates all year round (see our V3 update), and most of what you used on Tickets is on its free plan. Here is how the familiar features map across:
| If you used this on Tickets | In Tickety |
|---|---|
| Ticket panels with buttons | Ticket panels, 25 on the free plan and unlimited on premium |
| Forms before a ticket opens | Ticket forms, 3 questions on the free plan and 5 on premium |
| Claiming | Free, and on by default |
| Transcripts | Free, with no message cap, viewable on tickety.top and searchable in the dashboard |
| Close requests and autoclose | Premium |
| Several panels in one message | Supported |
| Whitelabel bot | The Custom Bot add-on, on premium |
Tickety also includes applications, verification, giveaways, a honeypot channel against spam and FAQ panels, so you may be able to remove a couple of other bots at the same time.
- Add Tickety to your server and open the dashboard.
- Create a ticket panel. On your first panel, a short setup wizard walks you through the essentials.
- Recreate your form questions and support roles, then set a log channel for transcripts.
- Post the panel, open a test ticket yourself, and close it to see the transcript.
- Delete the old TicketsBot panel and remove the old bot.
Our step by step setup guide covers each of those in detail, and our ticket bot comparison is there if you want to weigh up the options first.
Frequently asked questions
Is TicketsBot shut down?
Yes. Tickets, usually called TicketsBot, was discontinued on 5 March 2025 and the bot went permanently offline that day. Whitelabel bots of annual subscribers kept running until their subscription year ended.
Why is ticketsbot.net not working?
The bot was shut down in March 2025. In November 2026 the ticketsbot.net website, its dashboard and its export tool no longer respond.
Can I still get my TicketsBot transcripts?
An export tool was offered before the shutdown. It no longer responds, so if you did not export your data at the time, assume it is no longer available.
Is Tickets v2 the same as TicketsBot?
No. It is a separate bot started from the open source code by one of the original team's admins. You have to invite it separately, and it is run by different people from the original.
What is the best replacement for TicketsBot?
Look for a bot with claiming, transcripts and forms on the free plan, transcripts that are kept somewhere you can reach, and recent updates. Tickety covers all of those, and moving takes about ten minutes.