> 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/reporting-and-analytics/advanced-reports/ticket-statistics.md).

# Ticket statistics

![Ticket Statistics](/files/vpYV7WZObn2EA7njpECg)

### New Tickets

The number of new tickets created during the selected time period for selected mailbox (or all mailboxes). A single ticket may have many messages and generally aligns with a "conversation" (or thread) in Gmail.

{% hint style="info" %}
Filtering your data by tags will not have an effect on New Tickets, as a tag is always added after a ticket is created.
{% endhint %}

### Closed Tickets

The number of tickets that moved into the *closed* state during this time period, and that stayed closed.  If a ticket is closed and re-opened during the selected time period, and is in the open state at the end of the time period, is not counted as a closed ticket.

### Open Tickets

The number of tickets in the *open* state at the end of the selected time period.  

### Pending Tickets

The number of tickets in the *pending* state at the end of the selected time period.  

### Active Previous Period

For tickets that were created **prior to** the start date in the selected time period, the sum of tickets that have an *open* or *pending* state in the currently selected time period.

{% hint style="success" %}
Active Previous Period is great for understanding how many customer issues are not getting closed or resolved in a timely manner.
{% endhint %}


---

# 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/reporting-and-analytics/advanced-reports/ticket-statistics.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.