Appearance
Feedback
Every AI response in Stoa has a thumbs-up and a thumbs-down button under it. Use them. Your votes are how Stoa gets better at your specific work, in your specific organization, with your specific documents.
This page is about why feedback matters, how to leave it, and what happens after you click.
Why feedback matters
Stoa isn't a finished product the day it's installed. It's a tool your administrators tune over time: the knowledge bases get cleaner, the agent instructions get sharper. The thing they tune against is your feedback.
When you upvote a great answer, you're telling them: keep doing this. When you downvote a bad one, you're telling them: this needs work. Without that signal, your admins are guessing. With it, they have a real, ranked list of things to fix: which agent's answers get downvoted most, which document keeps producing wrong claims.
How to leave feedback
Look under any AI response. You'll see two small buttons:
- Thumbs up if the answer was good, useful, accurate, well-cited, or just well written.
- Thumbs down if it was wrong, incomplete, off-topic, badly cited, or unhelpful.
Click one and it's recorded immediately, there's nothing else to fill in. You can change your mind and click the other button later if you reconsider.
What to vote on
Vote on the content of the answer, not the tone. Don't downvote because you didn't like the phrasing, downvote because the content is incorrect, missing, misleading, or unsupported.
A vote only means something if you actually checked. A thumbs-up on an answer you didn't read, or a thumbs-down on a hunch, adds noise rather than signal. If you spot something specific and wrong, such as a stale citation or a fact that doesn't hold up, that's exactly the kind of answer worth downvoting: see citations for how to check one.
What happens after you vote
Your rating goes into a log your administrators review. They look for patterns: a single downvote is interesting, a cluster of downvotes on the same agent or the same document is a clear signal that something needs attention.
From a pattern of downvotes, an admin might:
- Replace a stale document in a knowledge base.
- Tighten an agent's instructions.
- Restrict or extend a tool's permissions.
- Fix a misconfigured retrieval setting.
- Bring the issue to whoever owns the source document.
You may not always see the change show up directly, but the next time you ask a similar question, the answer should be better. If you keep seeing the same problem after voting on it, tell your admin in person, a rating on its own doesn't carry the detail of what went wrong.
Privacy
The feedback log lives inside your organization's Stoa deployment. It does not leave your network. Your votes and the responses you voted on are visible to your administrators and, depending on your organization's settings, to a small number of people responsible for tuning the system. They are not sent to any outside service.
If your role requires that your usage be anonymous within your team, talk to your administrator about how feedback is attributed in your deployment.
A small ask
Vote on a few responses every day. It takes one click. Across a team of fifty, that's hundreds of small signals a week and that's enough to make Stoa noticeably better month over month.