How it works

Setup

1. Sign in and add the bot

   Signing in reads who you are and which servers you hold Manage Server in. That is Discord's own permission, read live on every load, so the list is exactly what you can already administer — and someone demoted this morning loses access this afternoon rather than whenever a cache expires.

2. Create a panel

   A panel is a ticket type. It owns the message people see, the button they press, the form they fill in, the category tickets land in, and who can handle them. A server can have as many as it likes, and one posted message can carry up to 25 of them.

3. Post it

   Run /panel in the channel you want it in. Posting again updates the existing message in place rather than leaving a trail of dead panels.

4. Name your support team

   Under Roles and access. Almost every other screen refers back to this list, so it is worth doing before anything else is tuned.

Ticket lifecycle

created → opened → closed → re-opened → deleted, with claimed and unclaimed running alongside as a separate axis.

Variables

Usable in any message, embed, channel name or custom command. Chain modifiers with a pipe: {owner.username|upper|max:12}.

Panel editor

Every tab below is per panel, so a billing ticket and a bug report can look and behave nothing alike.

Messages

Thirteen points where the bot says something, each with an embed builder. Leave one alone and it uses the built-in wording.

All accept the variables above. A mention only pings from the message text, never from inside an embed, which is why each editor has a box for both.

Channel permissions

Nine targets, each a grid of allow, inherit and deny across twenty-two permissions. Inherit keeps whatever the role has server-wide. This is what makes a ticket private, and why the bot never asks for Administrator, which would bypass every row.

Untouched means the built-in private defaults. One rule cannot be switched off: unless you explicitly allow @everyone to view, it stays denied.

Automation and custom commands

Automation rules

A trigger and a list of actions, written as JSON. Seven of the ten triggers fire the moment they happen: created, closed, re-opened, claimed, unclaimed, close requested and claim requested.

{"window":3600,"source":"owner","fireOn":"absence","actions":[{"type":"close","delay":0}]}

Actions: close, delete, sendCommand, stopAutomations, startAutomations. The last two let a human take over a conversation a rule was about to close.

Custom commands

Run one with /custom. Three modes: strict matches the whole text, wildcard understands * and ?, regex puts named groups into the response. Strict beats wildcard beats regex.

{"trigger":"faq","match":"strict","response":"See {server.name} docs.","delivery":"channel"}

Delivery is channel, dm or ephemeral. Text after the trigger becomes {answer.1} onwards, up to five.

Permissions

Discord shows an invite's permissions as a list with no explanation, and never reviews what an app asks for. The only gate is an admin pressing Authorize. So here is the whole list with a reason for each.

Commands

Two more live on Discord's right-click menu rather than the slash list: Open a ticket about this on any message, and Open a ticket with this user on any member.

When it goes wrong