> 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/help.md).

# /help

## Help Command

### Overview

The `/help` command opens a menu inside Discord with links to Ticket King's documentation and support resources.

### Usage

```
/help [command]
```

* **command** *(optional)*: Pick a command to get a direct link to that command's documentation page.

### Description

* **Help menu**: Opens a menu with pages you can move through, including setup guides, an FAQ, and bot information.
* **Quick links**: Gives direct links to the support server, the documentation, and the invite link.
* **Command help**: When you pick a command in the `command` option, the bot replies with a link to that command's documentation page.

### When to Use It

* When you want an overview of how Ticket King works.
* When you want quick access to support resources or the docs for a specific command.

### Permissions

* Anyone can use this command.
* The bot does not need any special channel permission to show the menu.

### Example

```
/help
```

Opens the Ticket King help menu so you can pick a help section.

```
/help command:close
```

Replies with a link to the `/close` documentation page.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ticketking.xyz/docs/bot-commands/help.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
