QREATEQREATE
🎟️

Tickets

A support panel that opens a private channel members can talk to staff in.

Post a ticket panel; when a member clicks it, QREATE opens a private channel between them and your staff. Staff can claim and close it, with an optional transcript.

Set it up

  1. 1Open Tickets and flip it on.
  2. 2Edit the panel — title, button label, and categories.
  3. 3Choose a close mode: delete, archive (keep the channel, locked), or require confirmation.
  4. 4Publish the panel to your support channel.

Panel examples

text
Support desk:
Title: Need help?
Button: Open ticket
Categories: Support, Report a user, Billing, Other

Applications:
Title: Apply for staff
Button: Start application
Categories: Moderator, Event host, Partner

Close modes

  • Delete - cleanest channel list; use when transcripts are enough.
  • Archive - keeps the channel locked for later review.
  • Request/confirm - best when members should confirm before closure.

How many tickets one member can have open

Set it once on this page and it applies to every panel. A panel can override it with its own number when one type of ticket needs a different rule; leave that field empty and the panel follows the server setting.

Note. Panels created before 29 July 2026 each carried their own limit of three from the moment they were made, which quietly overrode the server setting. They now follow the server setting. If yours is still capped at three, check that the limit field on the panel itself is empty.

Permissions to check

  • QREATE needs Manage Channels to create private ticket channels.
  • Staff roles must be selected or tickets may open without the right team seeing them.
  • If using an archive category, QREATE needs permission to move channels there.
Note. Archive mode keeps a record without cluttering the channel list — closed tickets are renamed and locked, and can be moved to an archive category.

Channels or private threads

By default each ticket opens as its own private channel. Turn on Open tickets as private threads (per panel, at the bottom of the panel editor) to instead open each ticket as a private thread under the panel's channel — the same claiming, closing, and transcript, just without a new channel per ticket cluttering your sidebar. The member who opened it and your staff are added automatically, and staff need no extra per-channel permission. It's off by default, so existing panels are unchanged. In thread mode, Delete deletes the thread and Archive locks + archives it; the destination category and anchor position don't apply (threads live under the panel channel).

Note. For thread mode the bot needs Create Private Threads, Send Messages in Threads, and Manage Threads. Very large staff teams should also have Manage Threads so everyone can see every thread; whoever clicks Claim is always added.

Design the form members fill in

By default a member opening a ticket gets two boxes: a subject line and a description. Turn on Use a custom form in the panel editor to build your own instead: a title, an instruction block shown above the fields, and up to five fields, each either a single line, a paragraph, or a list to choose from. Every field has its own label, placeholder and required flag.

The form can also carry a file upload box, so someone reports a bug with the screenshot already attached instead of being asked for it afterwards. Whatever they fill in appears in the ticket's opening summary, and uploaded files are re-posted into the ticket channel so they stay readable later.

Note. Discord allows five components in a form, and the instruction block and the upload box each use one. The editor counts down the room you have left and stops you at the limit.

Priority

When a staff member claims a ticket, they get a private menu to set its priority: Low, Medium, High or Critical. The choice is announced in the ticket and written into the opening summary, so the embed at the top always shows where the ticket stands.

Extra buttons on a panel

Each panel can carry up to 4 extra buttons, configured in the dashboard's Ticket Panels editor. Pick a button type for each: staff-only canned replies (a ready template, optionally with variables like the ticket opener's name) for fast, consistent answers; user-facing prompt buttons that post a suggested message into the ticket; or an event-mappable action button that runs a real action on click.

An action button does something, not just say something: give or remove a role, post a message, DM a member, or call a webhook — the same actions the Automations module offers. Role and DM actions can target either whoever clicks the button or the ticket opener, and a "post a message" action with no channel chosen posts inside the ticket itself. Set the button's visibility to *staff* to keep powerful actions to your team. Discord role hierarchy still applies — QREATE's role must sit above any role it grants or removes.

Duplicate panels

Creating a second panel in a channel that already has one is blocked — you'll get a clear message instead of a silent duplicate. If you already have a duplicate from before this fix, open the Ticket Panels editor and use the delete button on the extra panel's card (with a confirmation step); deleting a panel also removes its message from Discord.

Next✅ Verification