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

# /claim

## Claim Command

### Overview

The `/claim` command marks the current ticket as claimed by you. This tells other staff that you are handling the ticket. Run it inside the ticket.

### Usage

```
/claim
```

### Description

* **Take the ticket**: You become the assigned staff member for the ticket.
* **What changes**: The effect depends on the server's Ticket Claiming Mode. Depending on the mode, claiming can leave the ticket unchanged, make it read-only for other staff, or restrict it to the opener, you, and the bot. The server can also ping the ticket author and add roles when a ticket is claimed.

### When to Use It

* When you start working on a ticket, so other staff know it is taken.

### Permissions

* You can use this command if you have Manage Channels or Manage Server, or you are the server owner, or you hold an authorized support role. Administrator also works because it includes those permissions.
* The bot needs `Manage Channels` to update the ticket.

{% hint style="info" %}
Using `/claim` in Discord is free. Claiming a ticket from the dashboard is a Premium feature.
{% endhint %}

### Example

```
/claim
```

Marks the ticket as claimed by you.


---

# 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/claim.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.
