> For the complete documentation index, see [llms.txt](https://docs.keeping.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeping.com/help/setup/auto-close-stale-tickets.md).

# Auto close stale tickets

#### What is Auto Close?

Auto Close automatically closes tickets that have had no activity for a set period of time. This helps keep your inbox clean by resolving stale conversations that no longer need attention.

#### Setting Up Auto Close

1. Go to **Mailbox Settings** and select a mailbox
2. Find the **Auto Close** setting
3. Choose a time period: **5, 10, 15, 30, or 90 days** of inactivity
4. Click **Save**

Any ticket in that mailbox with no new messages for the chosen period will automatically be set to Closed.

{% hint style="info" %}
Auto Close is configured per-mailbox, so you can set different thresholds for different shared inboxes. For example, you might auto-close after 5 days for a sales mailbox but 30 days for a support mailbox.
{% endhint %}

#### What Happens When a Customer Replies?

If a customer replies to a ticket that was auto-closed, the ticket will automatically reopen. Your team will see it back in the inbox as an open ticket, and any SLA rules will apply as normal.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeping.com/help/setup/auto-close-stale-tickets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.