# Rate a Verdent Response (/docs/verdent-manager/core-features/response-feedback)

> Use the inline satisfaction controls to rate the latest result and share optional feedback



After Verdent finishes a response, you can rate the result directly in the message actions. The rating helps Verdent measure result quality without interrupting your task.

## Submit a rating [#submit-a-rating]

<Steps>
  <Step title="Choose a star rating">
    On the latest unrated Verdent response, select from one to five stars. The score is saved as soon as you select it.
  </Step>

  <Step title="Add details (optional)">
    The feedback panel opens inline. For one- to three-star ratings, you can select an issue type. You can also add a comment of up to 200 characters for any score.
  </Step>

  <Step title="Finish the feedback">
    Select **Submit** to save the optional details, or **Skip comment** to close the panel and keep only the star rating.
  </Step>
</Steps>

For lower ratings, the issue list includes problems such as incorrect results, incomplete work, ignored instructions, broken output, lost context, workflow issues, visual quality, speed, or cost. Four- and five-star ratings do not ask for an issue type.

<Note>
  The rating control appears only on the latest response that has not already been rated. A saved rating is product feedback; it is not added to the task as a follow-up instruction. Send a new message if you want Verdent to change the result.
</Note>

## If feedback cannot be saved [#if-feedback-cannot-be-saved]

If the local rating cannot be saved, Verdent keeps the panel open so you can retry. A problem sending product analytics does not remove the saved rating or block your work.

## Related guides [#related-guides]

<CardGroup cols="2">
  <Card title="Manager" icon="diagram-project" href="/docs/verdent-manager/core-features/manager">
    Assign work and review results
  </Card>

  <Card title="Code Review" icon="code-compare" href="/docs/verdent-manager/advanced-features/code-review">
    Review code changes separately from response feedback
  </Card>
</CardGroup>