October 2026

Panels, multi-panels, ticket welcomes, claim, unclaim, transfer, dashboard staff replies, and tags can now be sent as Discord Components V2 layouts. Leave the switch off and the message stays a classic embed.

What you can place

• Text, with Discord markdown, mentions, and the placeholders that message already supports.
• Containers, which are colored cards. You can stack more than one, each with its own accent color.
• Sections, with up to three text parts and an image, a link, or one ticket button beside them.
• A gallery of up to ten images, an uploaded file, a separator, and up to five link buttons.
• Ticket buttons stay under the bot. You can move them. You cannot invent a button the bot does not handle.

Multi-panels

In button mode, each bundled panel gets its own ticket button. The button uses that panel's button text, color, and emoji, and you can move each button on its own, including onto a section. A button can only appear once. Discord rejects a message that repeats the same button action. Dropdown multi-panels stay one menu.

Footer

Components V2 has no embed footer icon. The footer text sits at the bottom of the card, above the buttons. Free servers keep the locked "from ticketsbot.org" line, with the same premium notice as embeds. Premium servers can change the footer text.

Question marks next to each block explain it on hover. The live preview follows the toggle. Save again to update a message that is already posted.

Servers can create guild API keys from Dashboard, Settings, and call a read-only HTTP API. The API covers the guild, tickets, a single ticket, transcripts, panels, tags, teams, and the blacklist.

• Keys are shown once at creation. Store them outside the dashboard.
• Requests authenticate with the key and are rate limited per key.
• The API is read-only. It does not open, close, or edit tickets.
• Available on every plan. Full request examples are in the Developer API docs.

Support team members can now run /blacklist, not only dashboard admins. They can block a user from opening tickets in that server. Unblacklist still asks for confirmation.

/add and /remove now work inside thread tickets, the same as channel tickets. If someone deletes the thread instead of closing the ticket, the bot closes the ticket record so that member is not stuck at the open-ticket limit.

Forum posts are no longer counted toward Discord's 50-channel category limit, so a busy forum does not make ticket creation look full.

Discord sign-in no longer retries by itself after an OAuth error. Those retries were sharing one token limit across every visitor and keeping login broken. The sign-in page waits for you to try again.

Channel dropdowns on panels, multi-panels, and settings now ask the bot that is in the server for the list. If that read fails, the picker shows "Couldn't load channels. Try again." instead of looking empty.

The access control dropdown is no longer transparent, and the panel edit menu no longer slips behind the panel card below it when a server has several panels.

Multi-panel buttons now keep the color set on each single panel. They were falling back to blue.