AI Ticket Bot v2.4.13: close requests, your tickets, new embeds

AI Ticket Bot v2.4.13 is a wide one: three new slash commands, a redesign of most Discord embeds, tighter thread tickets, and another round of Nexus accuracy work. Everything below is live on every plan, including the free tier.

Ask before you close, with /ticket close-request

Staff can now run /ticket close-request instead of closing a ticket over the member's head, and the opener confirms it themselves. It is available on all plans, and the request embed is fully customizable in your dashboard so the wording matches the rest of your ticket copy.

Every member can see their own tickets with /mytickets

The new /mytickets command works both inside your server and in the bot's DMs, so a member can pull up their own ticket history without asking anyone for it. The same list is now on the web too: your account page got a redesign with a full ticket view, filtered by server and by status.

Vote straight from Discord

/vote brings voting into the server, so you can vote in a couple of seconds and spin the wheel for rewards without hunting for a link first. The vote page was redesigned as well, and it now shows how many rewards have actually been handed out.

Embeds redesigned around Discord's new buttons

Discord now allows buttons inside embeds, so we rebuilt most of the bot's embeds around that layout. Fewer stacked message blocks, actions sitting where you expect them, and a cleaner ticket channel overall.

Thread tickets are tighter

Thread tickets got a permissions pass, so normal users can no longer pull other members into someone else's thread ticket. When a thread ticket closes, the opener is now removed from it too, so finished tickets stop cluttering their thread list.

One thing worth doing on your side: on the parent channel of your tickets, deny Mention @everyone, @here and All Roles for every member role except your staff roles. Discord checks that at channel level, so this closes the last gap.

Related: if someone leaves your server and their ticket is closed afterwards, the bot no longer tries to DM them the transcript.

Sharper Nexus answers

We ran a long round of testing and analysis on Nexus this cycle and tightened its accuracy again, which cleared most of the issues you reported. The ones still open are cases where the current AI model runs into its own ceiling rather than something we can fix with better tuning, so we keep improving where improving helps, and we will move to a stronger model as soon as one is available.

A more stable bot

• /ticket search was reworked, so finding an old ticket is faster and the results are more accurate.
• Widget tickets now display properly and stay responsive on mobile.
• A batch of fixes for the errors reported since the last release.

Update now

Everything here rolls out automatically, with nothing to reinstall. /ticket close-request, /mytickets and /vote are already live in Discord, and the redesigned account view is waiting in your dashboard. The only manual step is the thread channel permission tweak above, and only if you use thread tickets.