Tickets & support
Give 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 only they and your staff can see. When it’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 and the right-click Message Report.
Who can run these: the owner, or an admin with Manage Server, sets up tickets. Any member can open one. Closing is open to the opener, your support role, or anyone with Manage Channels.
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
The whole journey, one screen at a time: the panel you post, a member opening a ticket, the private channel where you help them, and the close with 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. The free tier asks one question ("How can we help you?"); Premium servers can ask up to four. The first is always required. A member can hold more than one open ticket (two unrelated problems get two tickets); if you'd rather cap that, set Max open tickets per member in /tickets → Edit panel.
A channel just for this. The bot creates a numbered private channel (#ticket-0007-member) 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.
Closed, with a paper trail. Pressing Close Ticket (or running /tickets close) saves the conversation as a .txt transcript to your log channel, then deletes the ticket channel. 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 to open a one-screen builder.
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 (with Manage Server) to get a private FAQ builder: a
numbered list of entries, dropdowns to edit and delete, and an Add entry
button. Changes save instantly and the list refreshes in place.
Right-click → Message Report
Message Report is the reverse of a ticket: a fast, AI-assisted way for staff to deal with a single message. Right-click (or long-press) any message and choose Apps → Message Report. The bot reads the message plus the surrounding conversation, writes a short objective summary, and gives you action buttons, all privately.
How it works. The report is private and lasts about 15 minutes. Each
button respects your role, so you can only take actions 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. Because it reads the message with AI, it
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