Discord tickets worthy of a real support desk

A ticket panel that fits your server

It all starts with a panel posted in a channel. Pick its shape to suit your needs: a single button, several buttons (up to 25) to separate support, partnerships and reports, a dropdown menu with 25 options, or a parent panel that routes to other panels.

The panel message can be an embed, plain text or a modern container. For each panel, you choose the staff roles who will see the tickets, the roles to mention, the welcome message and the allowed or excluded roles.

Forms to get straight to the point

Instead of "hi, I have a problem", have members fill in an interactive form as soon as the ticket opens: short or long answer, single or multiple choice, yes / no, and even follow-up questions that show up depending on the answer.

Once the form is filled in, HurixBot posts a clear summary in the ticket and pins it. If the member doesn't finish in time, the ticket can close on its own.

Your staff stays organised

• Claiming: a staff member takes the ticket, with a custom emoji and messages;
• automatic expiry of the claim if nobody answers, with reassignment from a queue;
• /transfer to hand a ticket over to a teammate, /ticket transfer to send it to another panel;
• /ticket priority shows the urgency (emergency, high, medium, low);
• /ticket add, remove and rename to manage participants and the channel name;
• /ticket ping nudges the member, /ticket autoclose closes the ticket if they stop answering.

A clean close, transcripts kept

When closing, pick a preset reason (up to 25). With two-step closing, the ticket first becomes read-only with buttons to reopen it or delete it for good.

Every closed ticket leaves a transcript: a text file in your log channel and a copy you can read from the dashboard, per panel, with dedicated reader roles. You choose how long to keep them, from 7 days to 10 years, or with no limit.

Find any ticket in seconds

In the dashboard, filter your tickets by participant, author, assigned staff or the staff member who closed it (automatic closes included), by dates and times, by panel, by priority or by length. Filters stay in the page address: you can share a filtered view with your team. Ticket and staff statistics export to PDF or CSV.

Measure your members' satisfaction

With /ticket review or /avis, the member rates the staff who helped them from 1 to 5 stars and leaves a comment. Reviews can be posted in a channel, and the dashboard's Reviews tab shows the average with filters by rating.

Built-in anti-abuse rules

• maximum number of tickets per member and of claims per staff member;
• cooldown between two openings to prevent spam;
• /ticket ban blocks someone from opening tickets, for a chosen time or permanently, with automatic lifting when it ends.