June 2026

You can now fully control the messages your bot sends when a ticket is claimed, when it is unclaimed, and when a staff member sends a message into a ticket from the dashboard. Each one gets its own editor with the same rich embed controls you already know from the Tags editor.

✏️ Message Settings

Open the new "Message settings" button on the Tickets page to configure all three message types. Each message can be sent as plain text or as a full embed, with control over the title, color, description, author (name, URL and icon), thumbnail and large image, footer (text and icon), and up to 25 fields — each with its own inline toggle.

🧩 Placeholders

Messages support placeholders so they stay personal: %sender% (the staff member), %opener% (the ticket opener mention), %user% (their username), %ticket% (the ticket number) and %server% (your server name).

🔔 Safer Pings

Dashboard-sent messages now support targeted ping tokens — @opener, @claimer and @staff — so you can notify exactly the right people. @everyone and @here are blocked from dashboard messages so an accidental mass-ping can never escape the dashboard.

👥 Staff-Accessible

Both admins and support staff (see Staff Dashboard Access below) can open the Message settings modal, so the people actually working tickets can tune the messages they send.

Until now the dashboard was admin-only. With Staff Dashboard Access you can let your support staff into the dashboard to work tickets — without handing them the keys to your whole configuration.

🎟️ Tickets Tab Only

When enabled, members who hold a role in any of your Support Teams can open the dashboard and are restricted to the Tickets tab only. They can view, claim, close and send messages on tickets. Settings, panels, teams, analytics and every other admin area stay hidden and blocked at the route level.

🔐 Opt-In & Role-Based

It is off by default. Turn on "Allow support staff dashboard access" in Settings → Tickets. Access is resolved from your existing Support Teams — anyone with a support-team role is granted staff access automatically, with no separate list to maintain. Full admins (added via /admin addadmin) keep complete access as before.

Previously every transcript landed in one server-wide channel. You can now point each ticket panel at its own transcript channel, so support, bug-report and billing transcripts can each be archived where the relevant team is watching.

🗂️ How It Works

Set a "Transcript Channel" on any panel under Ticket Properties (on both the create and edit pages). When a ticket from that panel closes, its transcript is sent to the panel's channel. Leave it on "Use server default" to fall back to your server-wide transcript channel exactly as before.

You can now decide, per Discord role, who is allowed to open a ticket from each panel. Build an ordered allow/deny list in the panel editor and the bot enforces it every time a member tries to open a ticket — including through multi-panel dropdowns.

📋 First Match Wins

Entries are checked top to bottom and the first matching role decides access. @everyone always matches, so a trailing @everyone = Deny acts as a catch-all to lock a panel down to only the roles you allow above it. An empty list leaves the panel open to everyone, so existing panels are unaffected.

🧭 Interactive Onboarding Tour

First-time admins now get a guided, interactive walkthrough of the dashboard — a field-level tour of the create-panel form and teams setup that survives page loads and starts you in the right place. Skip it any time; it won't re-trigger once completed.

🎨 Redesigned Landing Page

Our public landing page got a full refresh with a cleaner, more modern look.

🗒️ Transcript Channel On Panel Creation

The per-panel transcript channel selector is available right on the panel create page, not just when editing — so you can set it up the moment you build a panel.

💬 Message Editor Matches Tags

The new Message settings modal uses the same embed editor UI as the Tags editor, so there's nothing new to learn.

Critical: @everyone Could See Ticket Channels After a Panel Switch

Fixed a serious permissions bug where switching a ticket's panel and then switching back could grant @everyone permission to view the ticket channel. Panel switches now preserve the correct private permissions.

Dashboard Close Skipped DM & Transcript Log

Closing a ticket from the dashboard now always sends the close DM to the opener and posts the transcript to the log channel, matching an in-Discord close.

Mass Pings Could Escape Dashboard Messages

Blocked @everyone and @here from being sent through dashboard messages, and added safe @opener / @claimer / @staff ping tokens instead.

Ticket View Wasn't Rendering Full Embeds

The dashboard ticket view now renders the complete embed — author, fields, images, footer and color — instead of just the basic text.

Empty Message Config Overrode Defaults

A saved-but-effectively-empty message configuration could blank out the default claim/unclaim messages. An empty config is now treated as "no config" so the sensible defaults are preserved.

Staff Access Edge Cases

Fixed several Staff Dashboard Access issues found during rollout: the wrong plan badge showing in the sidebar, premium status and timezone not being served to staff, staff being incorrectly blocked on ticket pages, a /settings 403 for transcript-access staff, and member-role lookups using the wrong token on whitelabel bots.

Onboarding Tour Reliability

Fixed the onboarding tour failing to survive page loads, starting on the wrong page, and occasionally re-triggering after it had already been completed.

/close Ignored the "Allow Users to Close" Setting

The /close command now respects the guild's allowUserClose setting, so non-staff can only close their own tickets when you've allowed it.

Privacy & Terms Typos

Corrected spelling on the privacy and terms pages.