> 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/reference/right-click-actions.md).

# Right-click actions

Discord right-click context-menu actions.

Ticket King adds one right-click (context-menu) action in Discord.

## Create Ticket

Right-click any message, open the **Apps** menu, and choose **Create Ticket**. This opens a ticket on behalf of the message's author, and the message content becomes the ticket's opening note. It is useful when a member posts a problem in a normal channel and staff want to move it into a ticket.

This action needs ticket permission, which means Manage Channels or Manage Server, or being the server owner, or holding a configured support role. Discord Administrators also pass.

## Where to find it

* **Desktop:** right-click the message, then open the **Apps** menu.
* **Mobile:** long-press the message, then open the **Apps** section.

If you do not see Ticket King under Apps, the bot may need to be re-invited. The recommended invite link already includes the access it needs.

## Related

{% content-ref url="/pages/2e7K9arpuGVAz8xz6xjF" %}
[Slash commands in Discord](https://ticketking.xyz/docs/reference/slash-commands.md)
{% endcontent-ref %}


---

# 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/reference/right-click-actions.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.
