> 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/rating-modes.md).

# Rating modes

Three rating modes. Rating only, with optional comment, or with required comment.

<i class="fa-crown">:crown:</i> **Premium.** The **Ticket Rating Mode** dropdown has three options. They control whether the member can leave a text comment with the star rating, and whether that comment is required.

## The three modes

| UI label                      | Behavior                                                                                                                            |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Rating Only**               | The member clicks a star and the rating is saved. No comment is requested.                                                          |
| **Rating + Optional Comment** | The member clicks a star, then a comment box opens with a single paragraph field. The member can submit it blank or with a comment. |
| **Rating + Required Comment** | The same comment box opens, but the field is required. Submit stays disabled until the member writes something.                     |

The default mode after you enable Ticket Rating is **Rating + Optional Comment**.

<figure><img src="https://1268186137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrnuG1qjzbOoh0efVpoK8%2Fuploads%2Fgit-blob-0ea9c9c1b23dbb3d7567d5c0bb9618bcd3e5048c%2Frating-modes-dropdown.png?alt=media" alt="Settings, Ticket Rating Mode dropdown open showing the three options"><figcaption></figcaption></figure>

## Which mode to pick

**Rating Only** asks for the fewest clicks, so more members finish the rating. It gives you the star score without any written comment.

**Rating + Optional Comment** gives you the star score from everyone, plus a written comment from members who choose to add one. This is the default.

**Rating + Required Comment** attaches a written comment to every rating. Some members who would give a quick star and leave may not finish, so you may get fewer ratings.

## Where the comment ends up

When a comment is submitted (the optional or required modes):

* It is saved to the dashboard with the ticket.
* It is shown in the Rating Log embed in the **User Feedback** field.
* It is shown on the closed ticket in Ticket History.

## Changing modes later

You can change the rating mode at any time. The new mode applies to tickets that close after the change. A rating prompt that was already sent keeps the mode that was active when it was sent.

## Related

{% content-ref url="/pages/ZJP01LC6EVKd946UMthw" %}
[What ticket ratings are](https://ticketking.xyz/docs/ticket-rating/what-ticket-ratings-are.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/ticket-rating/rating-modes.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.
