- Documentation
- Support
- Tickets
Tickets
Support requests as private channels: categories, panels, form questions, team roles, transcripts and ratings.
Quick look
This is how it looks in Discord – with sample data.
Support with the context your team needs.
A ticket panel, custom questions and a private channel: Your support team receives each request with the details that matter.
yurnaBOT
How can we help?
Open a support ticket and tell us a little about your request.
Interactive demo with sample data. Nothing is changed on a real server.
Open a ticket from the panel. Step 1 of 3
With the ticket system, members open a private channel with a button, where only they and your support team can write. Questions stay out of the public chat, and your team keeps track of everything.
In the dashboard#
You find everything under Support → Tickets (/dashboard/<server>/tickets). The page has three tabs: Tickets (inbox and handling), Statistics and Settings with Categories & form and Support hours & SLA. Statistics and support hours are covered in Ticket Pro.
How to set it up#
- Create a category in Discord (e.g. “Tickets”). yurna will create a separate channel for every ticket inside it.
- In the dashboard, open Tickets → Settings → Categories & form and click Add category.
- General tab: name, description, emoji and the label of the button that opens the ticket.
- Channels tab: pick the Ticket channel category from step 1 and the Panel channel where the button should appear. Without a ticket channel category, nobody can open a ticket.
- Roles & pings tab: choose your support team's roles. yurna mentions them as soon as a ticket opens.
- Save, then click Publish panel on the category. yurna posts the panel with its button to the panel channel.
The live preview in the editor shows how the panel and the ticket opening look in Discord.
How a ticket works#
- A member clicks the button in the panel. If the category has form questions, they answer them in a form first.
- yurna creates a channel in the ticket channel category and sends the opening message: an optional banner, an embed with the Claim and Close buttons, and a line with the pings.
- A team member clicks Claim and takes care of it.
- To close, the team clicks Close and can add a reason. If the creator clicks Close themselves, a team member has to confirm.
- yurna attaches the transcript as a file to the closing message and deletes the channel after 5 minutes. The creator receives a DM asking for an optional rating from 1 to 5 stars with an optional comment.
Settings in the editor#
- Team roles: The support team consists of the roles under Roles & pings, plus everyone with Administrator or Manage Server and the server owner. Only they can claim and close. Up to 10 roles per category; Mention ticket opener is a separate switch.
- Opening: banner (image URL), title, text and colour of the embed. The text supports
{user},{username},{ticket}and{category}. - Form: Create questions under Custom fields (short text, long text, number, select, multi select, optionally required) and assign them to categories. Discord allows at most 5 questions per form.
- Panel: title, text, colour, footer, thumbnail and image of the panel embed.
- Advanced: Ticket name template with
{emoji},{username},{ticketnumber},{priority},{categoryname}and{date}, plus Max tickets per user (empty = no limit).
Handling tickets#
The Tickets tab lists every ticket with search and filters for status, priority and category. Clicking a ticket opens it: follow the conversation live, reply straight into the Discord channel, claim or close it (including Close with note), write internal Notes and see form answers, the rating and Transcripts. Handling single tickets only works in the dashboard or with the buttons in the ticket channel.
Premium#
| New Moon | Half Moon | Full Moon | |
|---|---|---|---|
| Ticket categories | 3 | 10 | 25 |
More ticket features such as support hours and SLA are covered in Ticket Pro.
By command#
Everything in the editor also works in Discord. You need "Manage Server". Set up panels and categories with /tickets, form questions and general texts with /ticket-setup. If you leave an option out, it stays unchanged; for texts, - clears the field.
| Command | What it does | Important options |
|---|---|---|
/tickets panel create <name> | creates a panel | channel: channel for the panel, style: buttons or select menu, title, description (\n = new line), color (hex), footer, thumbnail, image, placeholder (select menu text), categories: categories in order, comma-separated |
/tickets panel edit <panel> | changes a panel | the same options as create, plus name |
/tickets panel delete <panel> | deletes a panel | delete-message: also delete the panel message in Discord |
/tickets panel list | lists all panels | – |
/tickets panel publish <panel> | posts the panel or refreshes the message | panel: which panel |
/tickets category create <name> <discord-category> | creates a ticket category | discord-category: Discord category for the ticket channels, panel, description, emoji, button-text, support-roles (mentions, up to 10), auto-roles (roles for the opener), transcript-channel, name-template, max-tickets (0 = no limit), priority, close-approval (closing needs team approval), enabled, color, open-title, open-text, ping-creator, banner |
/tickets category edit <category> | changes a category | the same options as create |
/tickets category delete <category> | deletes a category | category: which category |
/tickets category list | lists all categories | – |
/ticket-setup question add <category> <label> | adds a form question to a category | type: short text, long text, number, select, multi select; required, placeholder, description, options (choices separated by ;), max-length |
/ticket-setup question edit <question> | changes a question | like add, plus enabled (on/off) and category (for “required” per category) |
/ticket-setup question remove <category> <question> | removes a question from a category | – |
/ticket-setup question list | lists the questions | category: only this category |
/ticket-setup settings show | shows the general ticket settings | – |
/ticket-setup settings set | changes the general settings | welcome-title, welcome-message, claim-label, close-label, info-label (button labels), priority (default priority), auto-claim, auto-close (hours, 0 = off), reminder (hours, 0 = off) |
/ticket-setup settings reset | resets the general settings to default | – |
Support hours and SLA are set with /ticket-setup hours and /ticket-setup sla – see Ticket Pro. Long texts such as the opening message are easier to write in the dashboard. More under Set up everything with slash commands.
Common questions#
Why can't I publish the panel?#
The category has no ticket channel category. Pick one on the Channels tab or with discord-category in /tickets category edit.
Why aren't my support roles notified?#
The editor tells you why – usually yurna lacks “Manage Roles” or the role sits above yurna's role. Fix makes the role mentionable. More under Role pings don't arrive.
What does “This category has too many questions” mean?#
Discord allows at most 5 questions in one form. Remove questions from the category until there are 5 or fewer.
Who can claim and close tickets?#
The category's support roles, everyone with Administrator or Manage Server and the server owner. The creator can only request closing.
Where do I find old tickets?#
On the Tickets tab with the status filter “Closed”. The transcripts are there too. With Full Moon you can search every message with the transcript search.
See also#
Last updated on 30 October 2026