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

# /closerequest

## Close Request Command

### Overview

The `/closerequest` command asks the ticket author for permission to close, instead of closing the ticket yourself. It posts a message that pings the author with **Accept Request** and **Deny Request** buttons. Run it inside the ticket.

This is free on every plan. Several other ticket bots charge for it.

### Usage

```
/closerequest [reason]
```

* **reason** *(optional text)*: Why you want to close the ticket. It is shown in the request so the author knows what they are agreeing to.

### Description

* **Ask, don't assume.** The author decides. Nothing is closed until they click **Accept Request**.
* **The message is public.** It is posted in the ticket channel and pings the author, so they get a notification.
* **On Accept**, the ticket closes exactly as if `/close` had been used, and the normal close behavior, transcript, and log entry all apply.
* **On Deny**, the ticket stays open and staff can carry on.

### When to Use It

* The issue looks resolved but you want the member to confirm before you close.
* A member has gone quiet and you want to give them a clear way to say "yes, I'm done" or "no, still need help".
* Your server prefers members to close their own tickets rather than having staff do it.

### 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.
* Anyone can click the buttons only in the sense that the request is addressed to the ticket author — the decision is theirs.

### Notes

* You cannot send a close request for a ticket that is already closed. The bot tells you if you try.

### Example

```
/closerequest reason: Looks like the payment went through — can we close this?
```

Pings the ticket author with the reason and the two buttons.

### Related

{% content-ref url="/pages/qfsrgyXHffniP3UkUGWU" %}
[/close](https://ticketking.xyz/docs/bot-commands/close.md)
{% endcontent-ref %}

{% content-ref url="/pages/9dB72vzFglsTzKnh6Q2Z" %}
[Closing a ticket](https://ticketking.xyz/docs/tickets/closing-a-ticket.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/bot-commands/closerequest.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.
