Server Assistant🎫 Tickets & support
Give your members a tidy way to ask for help in private. You post a panel with a button; a member clicks it, fills in a short intake form, and the bot spins up a private channel that only they and your staff can see. When the matter’s resolved, anyone with access closes it and the bot saves a full transcript to your log channel.
This page also covers the AI FAQ — answer common questions automatically from a list you control — and the right-click Message Report, which gives staff a fast, AI-summarised view of a flagged message with action buttons.
Who can run these: the server owner, or an admin with Manage Server, sets up and edits tickets. Any member can open one from the panel. Closing a ticket is open to the opener, your support role, or anyone with Manage Channels.
Commands are tagged so you know what you’re looking at:
FREE available on every plan · PREMIUM needs a premium plan · ADMIN admins or the owner only · AI uses AI tokens
The end-to-end ticket flow
Here’s the whole journey, one screen at a time — from the panel you post, to the member opening a ticket, to the private channel where you help them, to the close and its saved transcript.
The panel. Run /tickets setup once and the bot drops this into a channel of your choice. It's a single persistent 🎫 Create Ticket button — it keeps working after restarts and for as long as the panel sits there.
The intake form. Clicking the button opens this short pop-up. On the free tier it's a single question (“How can we help you?”); Premium servers can ask up to four. The first question is always required. One open ticket per member at a time — click again while one's open and the bot just points you to it.
A channel just for this. The bot creates a numbered, private channel (#ticket-0007-member) that only the opener, your support role and staff with Manage Channels can see. It pings the support role, posts the member's answers, and pins a 🔒 Close Ticket button. Talk to the member right there.
Closed, with a paper trail. Pressing 🔒 Close Ticket (or running /tickets close) saves the whole conversation as a .txt transcript to your log channel, then deletes the ticket channel. Nothing is lost — you keep the record, the clutter goes.
Setting up & managing tickets
Post the ticket panel. Use it in an existing channel, or have the bot create a fresh locked channel where everyone can see and click the panel but only staff can type. Set a support role so your mod team can see and answer tickets.
| Argument | Type | Notes |
|---|---|---|
channel optional | channel | Existing channel to post the panel in — defaults to where you run it. |
support_role optional | role | The role that can see and answer tickets. Strongly recommended — without it, only admins see tickets. |
create_channel optional | text | Create a brand-new locked channel with this name and post the panel there instead. |
Close the ticket channel you're in. Saves a full transcript to your log channel, then removes the channel. The opener, your support role, and anyone with Manage Channels can close.
| Argument | Type | Notes |
|---|---|---|
reason optional | text | Optional close reason — saved into the transcript and the close summary. |
Edit the panel's title and description from a quick form — and on Premium, set custom in-ticket welcome and close messages too. If the live panel message still exists, the bot updates it in place.
Set up to four custom intake questions that members answer when they open a ticket. The free tier always includes the single default question; this lets Premium servers gather exactly the detail they need up front.
Pull another member into the ticket you're in — handy when a question needs a specialist or a second moderator. Open to staff or the ticket opener. Run it from inside the ticket channel.
| Argument | Type | Notes |
|---|---|---|
user required | member | The user to add to this ticket. |
The AI FAQ
Answer your most-asked questions automatically. You build a short list of
question-and-answer entries; members run /faq with their question and the
AI replies — using only your entries, never made-up policy. Leave the
question blank as staff and you get a one-screen builder to add, edit and remove
entries.
Ask the FAQ — or leave the question blank to open the FAQ builder (staff only). Answers come strictly from the entries you've added; if your FAQ doesn't cover something, the bot says so and points the member to your staff team rather than guessing.
| Argument | Type | Notes |
|---|---|---|
question optional | text | The member's question. Leave it blank (as staff) to manage the FAQ. |
Managing the FAQ — the builder
Run /faq with no question and (if you can manage the server) you get a private
FAQ builder: a numbered list of entries, a dropdown to edit, a dropdown
to delete, and an ➕ Add entry button that opens a small form. Changes
save instantly and the list refreshes in place.
Right-click → Message Report
Tickets are for members coming to you. Message Report is the reverse — a fast, AI-assisted way for staff to deal with a single message. Right-click (or long-press) any message → Apps → Message Report. The bot reads the message plus the surrounding conversation, writes a short objective summary, and gives you action buttons — all privately, only you can see it.
How it works. The report is private and lasts about 15 minutes.
Each button respects your role — you'll only be able to take an action
your staff role allows, and the bot won't act on the owner or on other bots.
Whatever you choose is written to your log channel with the AI summary attached,
so the decision and its reasoning are on the record. Because it reads the
message with AI, Message Report uses AI tokens and can be switched off per server
from the /privacy panel (toggle Right-click Message
Report).
Need to reach the bot’s developer instead? That’s a different door:
/support(and its alias/feedback) opens a private DM-based ticket with the maintainer for bug reports, feature ideas, setup questions, or data requests — separate from your server’s own member tickets above.
See also
- Moderation & safety — warnings, timeouts, removals and the raid toolkit that pair with Message Report
- Back to the Wiki hub
- Contact & support — reach the team directly