> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/bot-commands/panel.md).

# /panel

## Panel Command

### Overview

The `/panel` command posts a basic default ticket panel in the current channel. The panel has one button that members click to open a ticket. Run it in the channel where you want the panel.

### Usage

```
/panel
```

### Description

* **Post a ticket panel**: Adds a message with a button. Members click the button to open a ticket.
* **Quick start**: Useful for setting up a simple ticket button when you first add the bot.

For panels with multiple options, custom buttons, select menus, and forms, build a panel on the dashboard instead.

### Footer

On free servers, this default panel shows a "Powered by Ticket King" footer. On Premium servers, the footer is not shown.

### When to Use It

* When you want a simple way for members to open tickets.
* In a help or support channel where members open tickets.

### Permissions

* You need Manage Server to use this command. The server owner and anyone with Administrator can also use it.
* The bot needs `Manage Channels` in the server, plus `Send Messages` and `Embed Links` in the channel where the panel is posted.

### Example

```
/panel
```

Posts a default ticket panel in the current channel.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ticketking.xyz/docs/bot-commands/panel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.