Why it matters
Feedback loops turn bad answers into doc updates, new tests, and governance fixes. Without closure, thumbs-down is a mood ring.
How it works
Route feedback to owners, triage by intent, require linked tickets for doc or policy changes, verify with tests before closing.
Example
Nintendo thumbs-down on refund answers opens support ops tickets, assigns doc owners, and adds regression tests when fixes publish.
Common mistakes
- 1Feedback stored without triage SLA
- 2Product teams never see AI failure themes
- 3Fixing single sessions without systemic tests
Test the answer before your customer does.
Run answer tests and evaluations against your governed knowledge before you ship.
See answer evaluations