v0.17.0Open BetaJuly 15, 2026
Meet the Ticket Desk — support, in order
A panel your members click, a private channel that opens, a transcript when it closes — and a console where your staff can work it from the dashboard.
Every server ends up doing support, whether it means to. A member has a problem, someone DMs a mod, the mod forgets, and the thread is gone. The Ticket Desk turns that into a room with a door and a record.
Your members see one thing: a panel, and a button. Click it, answer a short form if you ask for one, and a private channel opens with the people who can help. Your staff claim it, work it, and close it with a reason — and a transcript goes to the member and to your log, once, automatically.
The parts that make support work are free. Every guard, every rule, every setting — the only thing your plan changes is how many panels, categories, and forms you can have. Support is not where we put a paywall.
A panel, and a button — Build it in the dashboard beside a live preview, deploy it to a channel, and your members never learn a command.
Forms before the channel opens — Ask the questions that matter first, and the answers arrive pinned at the top of the ticket.
The agent console — Read, reply, claim, and close from the dashboard — in step with Discord, both ways.
It closes itself — Idle tickets get a visible warning, then close on their own, with the transcript sent where it belongs.
Everything in this release
New
- The Ticket Desk — a panel of buttons or a dropdown in a channel you choose; a member clicks, and a private channel opens with your staff and a ticket number.
- Categories — each one with its own emoji, destination, staff roles, ping list, opening message, naming scheme, and limits. Three free, ten on Premium, unlimited on Pro.
- Forms — ask up to five questions before the channel opens, require the ones that matter, and the answers arrive pinned inside the ticket. Two free, ten on Premium, unlimited on Pro.
- The agent console — a Live tab where your staff read the conversation and reply, claim, or close from the dashboard, in step with Discord in both directions.
- Claim and unclaim —
/ticket claimputs one name on a ticket, and a second person is told who already has it, rather than quietly taking it. - Add and remove —
/ticket addand/ticket removebring someone into a ticket who wasn't part of it, or take them out. - Close with a reason —
/ticket closeasks for a confirmation, then renders the transcript, sends it to the member, posts it to your transcript log, and reclaims the channel. - Auto-close — a ticket nobody has answered warns visibly that it's closing in a few hours, and does. A reply from the member clears the timer.
- The guards — a blacklist role, a cap on how many tickets one member can have open, a cooldown between opens, and a server-wide rate cap for a raid. All free, and a double-click can never open two.
- A Tickets page — panels, categories, forms, settings, and the live console, each with a full-screen builder and a preview of what lands in Discord.
- It's all in your logs — every open, claim, and close appears on the tickets lane of your server logs.
Known issues
- Closing is final in this version. There's no reopen — a member who needs more opens a fresh ticket, and their old transcript still exists.
- The console asks for Manage Server, so a moderator who doesn't have it can't use it yet. A per-server list of ticket agents is the fix, and it isn't built.
- There's no transcript archive in the dashboard yet — transcripts go to the member and to your log channel, and that's where they live.
- A transcript can't reach a member who has DMs closed. It's marked undelivered and isn't retried; the copy in your log channel is still there.
- Tickets are channels in this version, not threads.
- There's no transfer, escalation, priority, or tagging yet, and no service-level alerts, satisfaction ratings, routing rules, or business hours. They're named on the roadmap, not hidden.
- If our cache is having a bad day, the cooldown and rate guards let tickets through rather than locking your members out. Only the cap on open tickets per member still holds.
- The Ticket Desk is off until you turn it on.
- The desk has been built and shipped but not yet run through a full open-to-transcript loop on a live server by us. If a ticket misbehaves, tell us and it goes to the front.
What's next for the Ticket Desk
Reopening, transfers and escalation, priorities, a searchable transcript archive, and a ticket-agent role that doesn't need Manage Server are the reserved next steps. The roadmap has the wider picture, and what you tell us still sets the order.