> 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/ticket-rating/where-to-read-ratings.md).

# Where to read ratings

<i class="fa-crown">:crown:</i> **Premium.** Once Ticket Rating is enabled, rating data shows up in three places.

## 1. The rating log channel

Every rating posts a new embed to your configured **Ticket Rating Log Channel**.

[The rating log channel](/docs/ticket-rating/rating-log-channel.md)

Use this for live visibility. As ratings come in, you see them in order, one embed per rating.

## 2. The single ticket detail view

On the dashboard, open **Ticket History**, then click any closed ticket to open its detail page.

If the ticket was rated, the detail page shows a **Ticket Rating Information** card with:

* **Rating**, the star count.
* **Rated Date**, when the rating was submitted.
* **Feedback**, the text comment, or *""* if no comment was collected.

[Single ticket detail](/docs/tickets-history/opening-a-ticket-detail.md)

Use this to look into one specific ticket.

## 3. The Statistics page

On the dashboard, open **Statistics**. It has an **Average Ticket Rating** chart that plots the average rating over the time range you pick. The average is weighted by how many ratings each period had.

Next to the chart you see:

* The average rating for the range, for example "4.32 <i class="fa-star">:star:</i> avg".
* The total number of ratings in the range.

When there are no ratings, it shows *"No ratings yet."*.

[The Statistics page](/docs/statistics/the-statistics-page.md)

Use this to follow the trend over time, for example across the last 30 days.

## What Statistics does not break out

* The Staff Leaderboard ranks staff by tickets closed, not by average rating. There is no top-rated-staff ranking.
* Statistics does not split ratings out by panel.

## Related

{% content-ref url="/pages/ZJP01LC6EVKd946UMthw" %}
[What ticket ratings are](/docs/ticket-rating/what-ticket-ratings-are.md)
{% endcontent-ref %}

{% content-ref url="/pages/FbKCvUVzdQTcW1xoif1r" %}
[The Statistics page](/docs/statistics/the-statistics-page.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 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://ticketking.xyz/docs/ticket-rating/where-to-read-ratings.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.