The Discord ticket bot for staff teams that need cases.
Arkanis turns tickets into cases. Members open them through button panels or DMs. Staff handle them with identity context, audit trails, and capability-gated permissions. Free for one panel. Pro for the rest.
What is a Discord ticket bot?
A Discord ticket bot lets members open a private channel with staff via a button or command. Common uses are support requests, ban appeals, member reports, and onboarding questions. Each open ticket becomes a private channel that staff handle, then close and transcript when done.
Arkanis calls these cases. A member clicks a button on a case panel, gets a private channel under a Support Inbox category, and staff handle the case from Discord or the dashboard. Identity context, strike history, prior cases, audit trail, and capability-based permissions sit alongside the case so staff are not handling it blind.
What Arkanis does as a Discord ticket bot.
The standard ticket surface, plus the parts that turn tickets into a real staff workflow.
Case panels with buttons
Members click a labelled button on a case panel and get a private channel under a Support Inbox category. Each button can route to its own subcategory, ping its own staff role, and use its own template. Free plan supports one panel with three buttons; Pro removes the limit.
Support Inbox dashboard
The dashboard mirror of the case workspace. Every open case is listed with member identity, claim state, age, and last activity. Search and filter by category, claim, or status. Staff who prefer the dashboard never need to leave it.
Modmail cases from member DMs
Pro feature. A member DMs the bot, picks a server, and the bot opens a real case channel in the Support Inbox category with the member added. Staff and the member share the channel. Same lifecycle and audit as button-driven cases.
Claim, close, transcript
A staff member claims a case to signal ownership. Other staff see the claim in the case header and in the audit log. Close generates a transcript and archives the channel. Add and remove participants as the case shifts. Free capability, gated by tickets_manage.
Identity context per case
If the member has linked their Steam, Xbox, or game-server identity, the case channel surfaces it. Prior strikes and prior cases for the same identity are reachable in one click, so staff are never handling a case blind.
Audit trail for every case action
Every open, claim, close, transcript, and message-action is audited with actor identity, reason text, and timestamp. Three months later, when someone disputes a closed case, the audit trail answers exactly what happened and why.
Capability-gated access
tickets_manage gates claim, close, transcript, and add/remove participants. tickets_configure (dangerous) gates panel and button setup. The same capability set gates Discord commands and dashboard actions, and view-as-role previews the boundary before you apply it.
Per-panel and per-button welcome templates
Each panel and each button can carry its own welcome message that posts automatically when a case opens. Useful for routing members to the right form, restating ban-appeal rules, or naming the staff who handle a category.
What separates Arkanis from a typical ticket bot.
Four things that matter for serious staff teams.
Cases live alongside enforcement, not in their own silo
A ban-appeal case in Arkanis surfaces the strike history, the linked identity, prior cases for the same person, and the audit trail behind the original ban. Staff are never piecing this together from five tools.
Capability gating is real
Junior staff can handle support cases without ever touching the destructive surface. The capability registry separates case-claim from case-close from panel-configuration. View-as-role previews exactly what a role sees before you assign it.
Audit covers the case lifecycle
Open, claim, close, transcript, add and remove participants. Every state change is audited with reason text and actor identity. The audit log is the dispute-resolution surface, not a debugging tool.
Modmail is a real case channel, not a proxied DM thread
Pro modmail picks up member DMs and opens a case channel in the Support Inbox. The member is added to that channel with read and write access; staff and member continue the conversation there directly. Staff get a `?note` prefix for internal-only entries that the member cannot see. Same lifecycle, same audit, same case data model as button-driven cases.
Free for one panel. £7.99 per month for the rest.
Free covers one case panel with three buttons, plus claim, close, transcripts, the full audit trail, and identity context. Pro removes the panel limit and adds modmail-from-DMs as another way for members to open cases.
Common questions
What is a Discord ticket bot?+
A Discord ticket bot lets members open a private channel with staff via a button or command. Common uses are support requests, ban appeals, reports of other members, and onboarding questions. Arkanis calls these cases. A member clicks a button on a case panel, gets a private channel under a Support Inbox category, and staff handle the case from there.
How is Arkanis different from a typical ticket bot?+
Cases sit alongside the rest of the staff control plane. The same audit log, the same capability checks, the same identity links. A staff member handling a ban-appeal case sees the linked Steam or Xbox identity, strike history, and prior cases in one view. Case actions are audited with reason text and actor identity. Junior moderators can claim cases without unlocking the destructive surface.
Can I run multiple case panels?+
Yes. The free plan supports one panel with three buttons. Pro removes the limit so you can ship one panel per case category: appeals, reports, support, onboarding, partner-requests, anything. Each panel routes to its own subcategory and can target a specific staff role.
Are cases a free feature?+
Yes. Cases are free, including claim, close, transcripts, add and remove participants, audit logging, and identity context. One panel with three buttons is free. Pro adds unlimited panels, unlimited buttons, and modmail cases from member DMs as another entry point.
Can staff claim cases?+
Yes, on Free and Pro. A staff member claims a case to signal ownership; other staff see the claim in the case channel header and in the audit log. Claim is gated by the tickets_manage capability, which Arkanis ships free for moderator-tier roles by default.
Will Arkanis import my old ticket bot configuration?+
No. Different bots store ticket configurations differently and we do not have an importer. The Arkanis Support Inbox Panel walks you through creating panels and buttons from scratch; most teams find it faster to rebuild than to migrate a stale configuration.
Try it on your own server.
Sign in with Discord, pick a server, and ship your first case panel in under five minutes. The free plan covers one panel forever.
See also: Moderation bot · Modmail bot · Pterodactyl bot · RCON bot