Support in Discord

A ticket system your support team will actually use.

A member presses a button, picks what the problem is about and fills in a short form. A private ticket opens, the team that owns that kind of problem gets pinged, and whoever takes it claims it. When it is done, the ticket closes with a reason and a transcript.

Start free View pricing

Panel

Where support in Discord usually breaks

Most servers start with a help channel. It works until the third person asks a question in the middle of somebody else's.

Everyone gets pinged for everything

The billing people get woken up for crash reports, so after a week nobody looks at the pings at all.

Nobody knows who has it

Two moderators answer the same member, or none does, because both thought the other one was on it.

The answer is gone a week later

The channel was deleted, the reason was never written down, and the next member with the same problem starts from zero.

What a Qreate ticket panel does

One panel per kind of help, each with its own categories, form and team.

Categories that ping the right team

Each category, and each sub-category, can ping its own staff roles. Billing pings billing, bugs ping the bug team. Only staff roles can be picked, because nobody else can see the ticket.

Claiming and priority

Only staff can claim. Whoever claims sets the priority, and the member sees who is on it and roughly how long the wait is.

Channel, thread or forum post

A ticket can be a private channel, a private thread under the panel, or a post in a forum channel. Closing archives or deletes it and keeps the transcript.

Example: a bug panel and a billing panel on one server

Ask Q: 'Make a support panel in #help with Bugs and Billing. Bugs ping the Bug team, Billing pings the Billing team.'

Q shows the panel, the categories and who each one pings, before anything is posted.

You approve. The panel appears in #help with one button per category.

A member opens a Billing ticket. Only the Billing team is pinged, someone claims it, and the transcript is saved when it closes.

What stays in your hands

Q drafts panels and changes, you review and approve them. Staff roles decide who sees a ticket. Every close asks for a reason, so the history says why, not only when.

Works together with

Tickets share roles, messages and automations with the rest of Qreate.

TicketsFormsRoles & PermissionsAutomationsAnnouncementsQ Chat

Frequently asked questions

Can different categories ping different teams?

Yes. Each category and sub-category has its own list of staff roles to ping. Leave it empty and the panel's list is used, and if that is empty too, every staff role is pinged.

Can a ticket be a forum post instead of a channel?

Yes. Each panel decides where its tickets live: a private channel, a private thread under the panel channel, or a post in a forum channel.

What is free?

One ticket panel with claiming and transcripts is free. More panels and the thread and forum options come with an upgrade. The pricing page lists what each plan includes.

Can I open a ticket from a button on any message?

Yes. A message button in an announcement or in one of Q's drafts can open a ticket panel's flow, the same as the button on the panel itself.

Verified sources

Tickets documentationPanels, categories, forms, close modes and transcripts, step by step.

Tell Q what your server needs.

Studio access is open free until 22 October 2026 with no credit card required. A permanent free plan remains available. Paid plans will be announced separately.

Start free Discord support

From the blog

All articles

October 7, 2026