# Feedback and problem reports

You can rate a specific answer, report an app problem, suggest a feature, or ask a billing question. Each path lets you review what you send.

## Rate one answer

Choose the thumbs up or down beneath a finished answer. For thumbs down, select any applicable reasons—**Wrong**, **Slow**, **Didn't do it**, or **Other**—and optionally add a note.

The sheet explains that it sends your request and that answer to the Nock team as cleaned text, together with your rating, reasons, optional note, tool identifiers and success/error codes, selected model, app version, and operating system. Tool arguments and outputs are not part of that feedback metadata. Choose **Send** to submit or **Cancel** to leave without sending. Pictures, screenshots, and files are not included in that answer-feedback payload.

This shares one exchange. **Help improve Nock** is a separate opt-in setting for sharing future exchanges; [Privacy controls](/nock/privacy-controls) explains it.

## Report a problem

Ask “report a bug” or open **Settings → About → Report a problem**. Choose a report type, summarize the issue, and add the steps that reproduce it. Read and edit the card or form before selecting **Send report**.

**Include diagnostics** adds details such as version, operating system, selected models, recent error codes, and cleaned log lines. Review **See what's included** and untick diagnostics if you do not want them attached. Reports require your final Send action, including when agent access is Autopilot.

## Make the report useful

Include the action you tried, what happened, what you expected, and whether it repeats. For example:

> After switching microphones, dictation starts but the input meter stays flat. The same microphone records normally in the system sound settings.

Do not paste provider keys or sign-in codes. If you supply your own screenshot or text, inspect it for unrelated private content before sending. Automated cleanup cannot inspect material you share through another service for you.

## After sending

Keep the short reference shown after submission. If the service is unreachable, a queued report can send when Nock reconnects. Optional usage sharing does not control problem reports or individual answer feedback; those are separate choices.

For a quick fix before reporting, use [Troubleshooting](/nock/troubleshooting). For billing and access, see [Billing](/nock/billing) and [Usage and limits](/nock/usage-limits).