How Discord Tickets works

1. Sign in with Discord. The site asks for two OAuth scopes only — identify (who you are) and guilds (which servers you are in). No e-mail, no messages, nothing posted on your behalf.

2. Pick a server. The dashboard lists servers where Discord gives you “Manage Server” or Administrator. Others are hidden — you cannot configure what you do not manage.

3. Add the bot. The “Add bot to server” button opens Discord’s invite screen for the server you picked. Panels, tickets and settings appear the moment it joins — with the real channel and role pickers.

Every panel lives in one channel and has a trigger: a single button for one queue, or a select menu where each option is a topic with its own staff and rules.

The message type decides how it is delivered. Components V2 (default) is Discord’s modern container layout posted by the app. Webhook sends a classic embed through a webhook with its own sender name and colour — handy when the panel should look like it comes from your server’s brand rather than from the bot.

The preview on the right of the editor is the same component the dashboard uses. Change the title, the text or the trigger and watch it update.

A topic has a label and an emoji (what the member sees), the mode it opens in — a private channel under a category or a private thread — and the staff roles that get access and a ping.

The intake form asks up to five questions before the ticket exists. Answers land in the first message, so staff start with context instead of “hi”. Mark questions as required when you need them answered.

Close rules keep queues tidy: who may close (opener or staff, staff only, opener only), whether closing asks for confirmation and a reason, how many hours of silence trigger auto-close, and how many open tickets one member may have at once.

The Tickets tab lists every ticket with the topic, who opened it, who claimed it, the status and when it started. Filter by open or closed, open a row to see the full transcript, the close reason, first-response time and duration.

Messages inside a ticket channel or thread are archived while it is open, so nothing has to be exported later. When a ticket closes, the channel can be deleted or kept — the transcript stays either way.

Each transcript has a public link switch. Off by default; switch it on to share the conversation with someone outside the server, switch it off and the link stops working immediately.

In Settings you choose the log channel (open, claim and close events are mirrored there), the default language for new panels, the staff roles pre-filled for new topics and whether transcripts start with sharing on or off.

Panels, forms and bot messages ship in English and Russian. The language is chosen per panel, so one server can run both.

The bot asks only for what the features need: view and manage channels and threads, send and manage messages in them, read their history, and edit channel permission overwrites so tickets stay private. Remove the bot from the server at any time from Discord’s server settings.

The FAQ on the home page covers pricing, privacy and languages. For anything else, join the Discord Tickets server — include the server ID and, for ticket questions, the ticket number.

Discord Tickets is an independent project by RootCore, not affiliated with Discord Inc. We also make discord-webhook.com, a free webhook and embed builder.