Tickets: Features
Everything it does
Panels and entry points
A panel is the message with the buttons. You can run several, each with its own rules.
{number}, {panel}, {username}, {button} and {category}. {panel_number} counts each panel's tickets on its own, and {number:4} pads a number to four digits, like 0142. Ticket titles can also use {subcategory}./ticket open lets managers and the panel's team open a ticket for a member, with an optional reason. It skips the blocklist, support hours, cooldown, limits and form.Intake forms
Ask the questions up front so the first staff reply is useful.
Working a ticket
Most of the bookkeeping happens without anyone touching a status.
/ticket escalate or the ticket page moves a ticket to another panel. Each panel can list up to 25 panels to escalate to. It can move and rename the channel, hand it to that panel's team and release the claim, and SLA targets not met yet restart under that panel's policy.Teams, hours and access
Who answers, when, and who is not allowed to ask.
/ticket dms off. A ticket by DM skips the opened and the staff replied notice: the bot's receipt and the answers themselves arrive by DM.Knowledge base and canned responses
Answer the common questions before a ticket is even needed.
/kb search returns the top five matches and /kb browse lists a category. Open to everyone./ticket respond posts one as the bot, and a reply can be set to go to the member by DM instead.Messages and look
Make the bot sound and look like your server.
{member}, {claimer}, {ticket.number}, {reason}, an intake answer with {form:field_key} and a fallback like {claimer|nobody yet}. A message never pings @everyone or @here.Transcripts, ratings and the web chat
The record of each ticket, and the ways staff can work it without opening Discord.
/ticket survey, and one switch turns the survey off.Backup and reuse
Build the setup once and carry it to the next server.
TKT-XXXXX-XXXXX, or start from one of the platform's ready-made templates.In the dashboard
/ticket respond or from a ticket's reply box, grouped by category, with placeholders, a use count, a copy button and the choice to send one by DM./kb search and /kb browse: articles with keywords, categories and drafts. Trigger words let an article answer matching messages in the channels you pick.Runs on its own
Limits
| What | Value | Notes |
|---|---|---|
| Buttons per panel | 25 | Discord's limit for one message. |
| Category menu depth | 10 levels | |
| Questions per form | 25 | Five to a page of the Discord pop-up. Questions filled in for the member do not count. |
| Open tickets per member | 1 to 20 | Default 1. Bypass roles skip the count. |
| Tickets per member per day | 0 to 100 | 0 turns the daily cap off. |
| Open tickets per panel | 0 to 500 | 0 means unlimited. |
| Cooldown between a member's tickets | up to 7 days | Per panel. |
| Attachments per ticket | 10 files, 8 MB | Kept with the transcript. |
| Transcript length | 1,000 messages | The newest ones are kept. |
| Messages held for a ticket by DM | 10 | For up to 30 minutes, until the member answers the bot's question or cancels. |
| Files in a ticket by DM | 8 MB each | Up to 10 files and 24 MB on one message. Anything over goes as a link. |
| Inactivity before a close request | 0 to 720 hours | 0 turns it off. |
| Close countdown | 1 to 168 hours | Default 24. |
| Closed channel retention | 0 to 365 days | A new server starts at 0, which keeps channels until someone deletes them. |
| Intake cleanup delay | 0 to 30 s | Default 5. |
| SLA warning | 30 minutes before breach | |
| Support hours windows | 6 a day | Per weekday, plus up to 100 closed dates. |
| Automation rules | 10 | Per server, each waiting 5 minutes to 30 days. |
| Escalation targets | 25 | Panels one panel can escalate to. |
| Delete after close | up to 7 days | Or right away. The transcript is saved first. |
| Roles per list | 25 | Access rules, observer roles and the roles given or taken on a ticket. The welcome message can ping up to 10 roles. |
| Channel renames | 2 per 10 minutes | Discord's limit. A rename past it is skipped with a note in the ticket. |
| Config export | 2 MB JSON | Up to 20 panels, 20 forms, 25 teams, 10 SLA policies, 200 canned responses, 500 articles and 10 automation rules. |
What it watches
GeneratedThe Discord events Tickets reacts to while it is enabled. It does not read history from before it was turned on.
Safety
/ticket dms off stops the opened, claimed and replied DMs and the rating survey for that member. The conversation of a ticket by DM is not a notification: its answers and one close message still arrive./ticket delete and automation rules all save a transcript before a channel goes. The one exception is a panel you set to keep no transcript.What it does not do
- The web chat mirror refreshes by polling, not a live socket.
- One breach ping per SLA policy. Escalating to another panel is a staff action, never automatic.
- Text channels and threads only. No voice or video tickets.
- The knowledge base is searched from Discord. There is no public web help centre.
- Automation rules react to replies, time and members leaving, not to what a message says.
- No email or SMS channel.
- One claimer per ticket. Adding a member grants access but is not a claim.
- Staff cannot start a ticket by DM. The member writes to the bot first.
- A member cannot start a second ticket by DM with your server while their first is open.
- In a ticket by DM, reactions and typing are not carried across. The member's own edits and deletes follow the choice on the Tickets by DM card, and by default the staff copy is updated.
Thank you. Your answer helps us improve the docs.
That did not go through. Try again in a moment.
Your sign-in changed since this page opened. Reload the page and try again.