> 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/tickets/inactivity-rules.md).

# Inactivity rules

Auto-closing tickets that go quiet, with close on leave (free) and timed inactivity (premium).

Ticket King has two automatic closes.

## Close on leave (Free)

When the ticket author leaves the server, their open tickets are closed automatically.

| Setting             | Default | Is Premium? |
| ------------------- | ------- | ----------- |
| **Autoclose Leave** | off     | No (free)   |

Configure in **Settings, Ticket Autoclose Settings, Autoclose Leave**.

When **on**, each open ticket the member owns is closed with a "user left the server" reason.

When **off**, which is the default, no ticket is closed. Instead, a "user left" notice is posted in each of their open tickets so staff know.

## Timed inactivity close (Premium)

Tickets with no recent message activity are closed after a period you choose. This is a <i class="fa-crown">:crown:</i> Premium feature.

| Setting                          | Default | Is Premium?                             |
| -------------------------------- | ------- | --------------------------------------- |
| **Auto-Close Inactivity**        | off     | <i class="fa-crown">:crown:</i> Premium |
| **Auto-Close Inactivity Period** | 7 days  | <i class="fa-crown">:crown:</i> Premium |

Configure in **Settings, Ticket Autoclose Settings**.

### How the period is set

Set the Auto-Close Inactivity Period with a slider. You can pick 6 hours, 12 hours, 1 day, 2 days, 3 days, 7 days, 14 days, or 30 days. The default is 7 days.

### How it works

A ticket is closed when it has had no messages for the full period you set. Brand-new tickets are not closed before that period has passed, even if they are quiet.

An inactivity close uses the standard close flow, so it produces the same transcript, logs, and DMs as a manual close. The close reason states that the ticket was closed due to inactivity.

### Turning it on, confirmation prompt

When you turn Auto-Close Inactivity from off to on, the dashboard shows a confirmation pop-up:

> **Enable Auto-Close Inactivity**
>
> Enabling this will instantly close all tickets that have been inactive for longer than your selected period. Please double check your Auto-Close Inactivity Period selection before proceeding.

This matters, because turning the feature on does not give currently-open tickets a grace period. If your period is 7 days and you have a ticket that has been quiet for 8 days, it closes soon after you enable the feature. Set your period first, then enable.

### What it applies to

The inactivity period is server-wide. There is no per-category, per-panel, or per-option override. Every ticket on the server uses the same period.

## Disabling auto-close for a specific ticket

There is no per-ticket disable. To keep a ticket open, have staff post a message in it, which resets the inactivity timer.

## Common questions

{% hint style="info" %}
**Does a staff response count as activity?** Yes. Any message in the channel resets the timer.
{% endhint %}

{% hint style="warning" %}
**A ticket was auto-closed but the member was just away.** Your period is too short for your team. Set a longer period. The default is 7 days.
{% endhint %}

{% hint style="warning" %}
**Tickets keep closing even with Auto-Close Inactivity off.** Check the close reason. An inactivity close always says the ticket was closed due to inactivity. If it says *"Ticket channel was manually deleted by an administrator."*, someone deleted the ticket channel in Discord, and Ticket King only recorded the close. Open **Server Settings, Audit Log** and filter by **Delete Channel** to see who. Entries made by Ticket King are its own closes. Entries made by another bot or a staff member are the cause, so remove that bot's access to your ticket category or turn off its auto-delete.
{% endhint %}

## Related

{% content-ref url="/pages/9dB72vzFglsTzKnh6Q2Z" %}
[Closing a ticket](https://ticketking.xyz/docs/tickets/closing-a-ticket.md)
{% endcontent-ref %}

{% content-ref url="/pages/exzL4IxFJ6d9jWNjp6BF" %}
[The premium-only feature list](https://ticketking.xyz/docs/premium/feature-list.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/tickets/inactivity-rules.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.
