Polls, Honeypot and Automations: Tickety's Biggest Update Since v3

This update adds three new layers to Tickety. Polls, a Honeypot module that every server gets for free, and Autoresponders rebuilt into full Automations. Underneath all of it, this is also the biggest speed pass the bot and the dashboard have ever had. Here is everything that changed.

Polls, built the way you want them

Polls are a module of their own now, not a message with reactions on it. You write the message, you write the answers, and you decide every setting: how members vote, when results become visible, how long it stays open, and who is allowed to take part.

• Two ways to vote. A button beside each answer, or one dropdown under the list. Buttons let an answer be as long as you like, because the button carries no label of its own.
• Results when you want them. Live as votes land, only after somebody has voted, or held back until the poll closes.
• Scheduling for everyone. Setting a poll to post later is free, because a poll tool that makes you stay up to press send is not a poll tool.

Free servers get 5 answers per poll and 5 polls running at once. Premium raises that to 25 answers, unlimited running polls, hidden results, multiple votes per member, and answers your members add themselves.

Polls that run themselves

Set a poll up once and it can come back on its own schedule, every few hours, days, weeks or months. That alone keeps a quiet channel moving without anybody remembering to post.

Give a repeating poll a topic and AI writes it from there. Every time it comes around it gets a fresh question and a fresh set of answers on that topic, so a weekly community poll never repeats itself. It runs on your AI credits, so you only spend on the polls that actually post.

Honeypot, free on every server

A honeypot is a bait channel. Real members have no reason to post in it, so anything that does is almost certainly a compromised account or a bot working through your member list. Tickety watches that channel and acts the moment somebody takes the bait.

• Pick the punishment. Ban, softban, kick, mute, or log the catch and leave the account alone.
• Clean up the damage. A ban or a softban can wipe the account's recent messages across your whole server, not just the one in the bait channel.
• Tell them why. The caught account gets a DM explaining what happened, with a rejoin button for somebody whose account was simply compromised.
• Keep your staff safe. Exempt roles, and your Tickety admin role, are never caught.
• Stay hidden. The bait channel can rename itself daily from a list of ordinary names, so it does not read as a trap.

The trap, every action, the exemptions, the warning message, the DM, the counter and the log channel are all free, on every plan. A safety feature behind a paywall is one nobody installs, and the server that does not install it is the one that gets raided. Premium adds the extras around the catch: putting the account on your blocklist, quoting the message into a staff channel, and holding the punishment back for a moment so a moderator can step in.

Ban appeals that actually reach people

Once somebody is banned, a button in a channel and a slash command are both useless to them. They are outside your server, so there is nothing left to press. A link still works.

Point a honeypot ban at one of your application panels and the ban DM carries a link to that panel's public form. A member whose account was compromised can fill it in and make their case, and it lands in the same review queue as every other application, with the same questions, the same reviewers and the same decisions.

Entry requirements, free on every plan

Raids and ticket spam almost always come from accounts that were made this week and joined ten minutes ago. You can now ask for a minimum account age and a minimum time in your server before somebody is allowed to open a ticket, submit an application, or enter a giveaway.

Set it per ticket panel, per application panel, per giveaway, or on every giveaway at once from the giveaway settings. It costs nothing on any plan, because it is the cheapest spam filter there is.

Autoresponders are now Automations

Autoresponders answered a keyword with a message. Automations keep every one of those triggers and turn the response into a flow: a list of steps that run in the order you put them.

There are 21 actions to build with, and more on the way:

• Messages. Reply, alert another channel with a jump link, react, pin, or delete the message that set it off.
• Roles. Hand out roles or take them away.
• Tickets. Open one from a regular channel, then close, request a close, claim, unclaim, rename, move, transfer, or set the priority.
• The rest of Tickety. Post an answer straight off an FAQ panel, DM somebody an application, or block a member from tickets, applications, giveaways, polls or the whole bot.

More of it is free than before. Replying, deleting the trigger, reacting, pinning, and both halves of closing a ticket all run on the free plan, so a close keyword works on any server without paying for it. What premium buys is the steps that reach beyond the message in front of them: roles, opening tickets, moving them around, and everything that drives another module.

Steps that use another module are not second implementations of it. An FAQ answer is read off its panel on every fire, so editing it there changes what the automation posts. An application started by a flow is held to the same cooldown, role and pending limit rules as one started from its own panel. Nothing here is a way around your own settings.

Five new ways to set one off

An automation no longer has to wait for somebody to type something. On top of commands, keywords, regex, whole channels and panels, a flow can now fire when:

• A member joins your server.
• A role lands on somebody.
• A role comes off somebody.
• A button on another automation's message is pressed.
• Honeypot catches an account.

That last one is where the two new modules meet. A catch can hand out a role, post to a staff channel, or start any flow you have built, so what happens after a raid attempt is yours to decide.

Ratings get their own tab

Ticket ratings used to be a number. They are a whole analytics tab now: your score breakdown, how many of your closed tickets actually get rated, what each staff member earned, which panels score best, and every written comment in one place instead of buried in a log channel.

Faster everywhere

A large part of this update went into performance rather than features. The gateway, commands, tickets and the dashboard all respond noticeably quicker than they did, and the heaviest dashboard pages load in a fraction of the time. The dashboard also picked up new animations and transitions, and a long list of small rough edges got sanded off while we were in there.

Smaller changes worth knowing

• Roles on claim and unclaim. Ticket panels already handed out and removed roles when a ticket opened or closed. They can now do it the moment one is claimed or unclaimed.
• Milestone card backgrounds. Welcomer milestone cards can carry your own background image.
• Reminders anywhere. The reminder command is user installable, so it works in servers that do not have Tickety.
• New statistics placeholders. Your poll, honeypot and welcomer numbers can be printed into any message, and they are all listed in the dashboard picker.

How to get it

There is nothing to install and nothing to migrate. Everything above is already live on every server running Tickety, and your existing panels, tickets and settings keep working exactly as they did. The new modules are waiting in the dashboard whenever you want to switch them on.

If Tickety is not on your server yet, add it here, follow our setup guide, and read the documentation for a deeper look at every module.