Feedback

The round feedback button sits at the bottom right of the workspace, and opens Send Feedback.

On the Feedback tab:

• A sentiment choice: Happy, Okay, or Sad.
• A Feature request switch, which routes it as a request rather than a report.
• The message box, which invites you to share thoughts, suggestions, or report issues. There is a microphone control if you would rather speak it.
• The page you are on is included automatically.
• A checkbox to include client console output, which may contain technical details from this browser session. Turn it on for anything that looks like a bug; it usually contains the reason.
• Capture screenshot, which attaches an image of your current screen, with Remove if you change your mind.
• Submit Feedback.

Keyboard shortcuts are listed in the dialog, including one to open it and one to capture a screenshot directly.

If the submission saved but the notification failed, a banner says so with Retry notification. Your feedback is not lost in that case.

What makes a report useful: what you did, what you expected, what happened, and the screenshot. What was not working is a message that costs someone a round trip to answer.

Feedback inbox is the conversation, not just an archive. It lists your submissions with the team's status, and it is where replies arrive.

Statuses you will see: new, read, replied, closed, under review, on the roadmap, in development, and live. Feature requests are badged as such.

Opening an item shows Your message, any Message from team, and a box to reply and continue the conversation, with Send. New replies are highlighted, and the sidebar entry carries a dot when something is unread.

New feedback starts another submission and Refresh reloads the list. Items can be deleted, which asks for confirmation.

Some team replies are drafted with AI assistance and reviewed by a person before sending. Where disclosure is required, it is disclosed.