> For the complete documentation index, see [llms.txt](https://metacrm.gitbook.io/metacrm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metacrm.gitbook.io/metacrm/products/community/ticket/report.md).

# Report

The Service report offers a comprehensive overview of ticket statuses, channel distribution, and type distribution, enabling projects to effectively analyze performance. Users can filter data over various periods—1 day, 7 days, 30 days, or all-time—to evaluate the impact of protocol updates or the effectiveness of campaigns during specific intervals.

## Key features

* Visual indicators for **ticket volume**, **CSAT**, and **resolution time** to help you see performance trends at a glance.
* **Custom date filters** to view performance data over any time range you choose.
* Detailed data on **ticket resolution times** and **CSAT** per agent, helping you identify areas for improvement.
* Seamless integration with **Discord**, allowing you to track tickets created or replied to on Discord separately from those handled through your portal.

<figure><img src="/files/yDcQh87XmV55Z10AuwyF" alt=""><figcaption></figcaption></figure>


---

# 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://metacrm.gitbook.io/metacrm/products/community/ticket/report.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.