Sunsetting Tickets

It is with a heavy heart I am announcing that we will be discontinuing Tickets as of the 5th of March 2025. This means that the bot will permanently go offline. However, it's not all bad news.

Why?

We have some really great volunteers providing support, for which words can't describe my gratefulness. But behind the scenes, it's a one-man show. I just don't have the time to dedicate to running the bot anymore and have fallen out of love with it over the past couple of years. I can't dedicate enough time to continue maintaining it and keeping up to date with the changes in the bot ecosystem. It's a personal decision, I never intended for the bot to become *this big*, but it's time to move on.

What about my data?

We have created a data export tool available at export.ticketsbot.net, which provides the option to download all ticket transcripts, server data & bot configuration for any server that you own. This data can then be directly imported to other instances of the bot (such as ticketsbot.cloud), so that you can continue to use all of your existing data with similar / identical functionality.

I have a premium subscription, what happens?

We have now disabled billing on both Patreon on Discord. You won't be charged again. If you have a monthly subscription, it will run its course, and we will additionally extend it until the 5th of March free of charge.
If you have an annual subscription, things are a bit different. Whitelabel bots will continue to run until their expiry, up to a year away. Patrons with annual premium subscriptions have been given a free upgrade to whitelabel, and will need to configure a whitelabel bot before the main bot goes offline on the 5th of March. You can read the whitelabel setup guide here. Pro-rata refunds for the newest subscriptions will be made after the 5th of March. There will be no new feature development, etc. within this time. We will still provide support however.

Alternatives

All the code is open source on [Github](https://github.com/TicketsBot). It's good tech, we run the entire bot on just a few GB of RAM and a few CPU cores. We have created a #self-hosting channel in our support server where we will be around to provide some limited support on self-hosting the bot: I'll also open-source the Kubernetes manifests soon. There's a lot of moving parts and is suited for a Kubernetes environment, so it's probably not for the faint-hearted / those who just want a support bot for a single server. Some members have had success in self-hosting & composing a docker-compose file.

ticketsbot.cloud

One of our admins has created a new instance of the bot, available at ticketsbot.cloud. This is a new bot, that you will need to invite to your server separately, but it functions in the exact same way as the original Tickets bot. It's a great alternative if you're looking for a new support bot. They have also created a data import tool, which allows you to import all of your data from the original Tickets bot to the new one. You can find the data export tool at export.ticketsbot.net, and the data import tool on the dashboard at ticketsbot.cloud. ticketsbot.cloud

Finally, I'd like to thank all of our volunteers for the unwavering support over the past 6 years, as well as all of the patrons, and everyone else who has helped out.