Docs / Tickets / Commands / /tickets panel
Admin Server only

/tickets panel

Create, edit and post ticket panels

Usage

Generated
/tickets panel [panel_id] [channel]
OptionTypeRequiredDescription
panel_id whole number
suggests
No A panel to open in the builder (pick from the list). Leave empty to see them all
channel channel No With a panel: post it in this channel straight away (text, announcement channels)

Who can run it

Generated
Discord defaultEvery member
Command Access presetServer managers
Always allowedThe server owner and, by default, Administrators
Change itDashboard, Services, Tickets, Commands

The presets keep it for server managers. Server owners and Administrators can always run it. How Command Access works.

What the bot needs

Generated

Tickets is granted these permissions by the invite link. A command that finds one missing replies privately with what it could not do and changes nothing.

Manage ChannelsView ChannelSend MessagesEmbed LinksRead Message HistoryManage RolesManage ThreadsCreate Private ThreadsSend Messages in Threads

Behaviour

Checked against the code 2026-10-08

Builds, changes and posts your ticket panels without opening the dashboard. Run it with no options and a private builder opens: one message only you see, which changes as you go. Give it a panel and the builder opens on that panel. Give it a panel and a channel and the bot posts that panel there straight away.

The bot first applies the server's Command Access rules for /tickets panel and checks that Tickets is enabled ("❌ Tickets is not enabled for this server."). You need the Manage Server permission or the manager role on the dashboard's Access page. Everyone else is told: "Only people who manage this server can build ticket panels. You need the Manage Server permission or the manager role on the dashboard's Access page."

The builder

The first screen, "Ticket panels", lists every panel with its state: "Live in #channel", "Not posted" or "Off". A panel you changed after posting it also says "Changes not in Discord yet". "Pick a panel to edit" opens one, "New panel" makes one and "Open the dashboard" takes you to 1 Opening.

"New panel" asks for a "Name" and what to "Start from": "Blank", "Support" or "Applications". The builder then asks where members will see it ("Now pick the channel where members will see it."), so a working panel takes two steps. An application panel first asks for the channel where staff review applications.

A panel's screen shows whether members see the saved version ("In Discord"), its "Status", "Where tickets open", "Who answers by default", what "Members pick from" and the message itself, exactly as members see it. The "Change..." menu holds the rest:

  • "Name", "Title and text" and "Colour and images" each open a pop-up with the current values filled in. An image or a thumbnail is a link that starts with https://.
  • "Buttons" lists the panel's buttons, up to 25. "Add a button" asks for a "Label", an "Emoji" and the "Line under it in the menu". Pick a button to change its "Colour", choose "Who answers tickets from this button", move it up or down or remove it. A server emoji can be typed by its name, like :ticket:.
  • "Where tickets open" picks the category for new ticket channels ("Pick a category" or "No category"). On an application panel it picks the review channel.
  • "Who answers by default" picks one of your teams ("Team that answers") or makes one: "New team from a role" turns a role into a team and puts it on the panel.
  • "Members pick from" switches between "Use buttons" and "Use a menu", and "Change the menu's text" sets the text in the menu before a pick.
  • "Turn off" and "Turn on" close the panel to members and open it again.

The main button of a panel's screen puts it in Discord:

  • "Post in Discord" asks for a text or announcement channel ("Pick a channel"). The bot needs View Channel, Send Messages, Embed Links and Read Message History there. When something is missing nothing is posted: "The panel cannot be posted in #channel yet.", followed by what the bot lacks and the steps in Discord that fix it.
  • After a change the button reads "Update in Discord", and pressing it edits the posted message in place: "Updated in Discord. Members now see the panel as it is saved." While nothing is waiting it reads "Members see this version".
  • "Move to another channel", in the "Change..." menu of a posted panel, posts the panel in the channel you pick and then deletes the old message, so members see one panel.
  • "Delete this panel" asks first ("Yes, delete it" or "Keep it"). The bot deletes the panel's message too. Tickets already opened from it are kept.

"More settings on the dashboard" opens the panel on 1 Opening for everything the builder leaves out: questions, response targets, limits, opening hours, who can open tickets, the options members pick from after a click and private threads.

Posting a panel directly

With both options the command posts the panel and answers "✅ Panel <name> posted in #channel!" The panel must belong to this server ("Panel not found."). The bot checks its own permissions in the channel first and stops with a private message when any of View Channel, Send Messages or Embed Links is missing: "❌ I'm missing the <permissions> permission in #channel." If Discord still refuses the post: "❌ I couldn't post in #channel - check my permissions."

The panel_id option has a picker: start typing and choose from your panels, shown as "<name> · #<number>", with "· posted" when the panel is already posted somewhere and "· off" when it is disabled. The channel option accepts text and announcement channels.

Good to know

  • A button change updates the posted panel right away, as on 1 Opening: "The panel in #channel is up to date." A change to the name, the title, the text, the look or "Members pick from" waits for "Update in Discord".
  • The builder posts the same message as "Post in Discord" on 1 Opening, so the builder and the dashboard always agree on whether members see the saved panel.
  • The dashboard lists what was changed in the builder in the last 30 days, with who made each change: History, "Panel changes made in Discord".
  • If someone deletes the panel's message in Discord, the builder says so the next time it tries to update it ("The panel's message was deleted in Discord. Post the panel again.") and the panel reads "Not posted" again.
  • Posting directly a second time leaves the earlier message where it is. "Move to another channel" in the builder keeps one copy.
  • The channel's member count at posting time is recorded and shows as "Reach" in the Buttons table on the Insights tab of the dashboard's History page.
  • A panel that is off can still be posted, but its buttons answer "This panel is not available." until you turn it on.
  • Tickets by DM opens its tickets under one panel (1 Opening, "Tickets by DM"). Turning that panel off or deleting it stops members from opening a ticket by writing to the bot. The builder tells you so right away, and so does the dashboard. Turn the panel on again or pick another panel on the card.
  • /tickets setup creates a channel for a panel and posts it there in one step.
YourBot docs Reference tables are generated from the code that is running. Ask in Discord Suggest a correction