Ask for the minimum useful report
Capture the task the employee was trying to complete, the answer they found unhelpful and what seemed wrong. Where available, attach the conversation reference and application version without asking the employee to copy a long transcript. Let them distinguish an incorrect fact from missing context or an unusable format. Explain where reports go and discourage adding passwords, personal details or unrelated confidential documents merely to make the example more convincing.
Give the queue an owner and status
Assign a person or staffed role to triage new reports and provide cover for absence. Use visible states such as received, needs clarification, under review, change planned and resolved. Agree review expectations internally rather than promising an unsupported response time. Acknowledgement should mean the report was received, not that the answer was wrong or a correction is complete. Keep reports that await another team visible with a next action.
Separate the cause from the complaint
Check whether the relevant source is incorrect, missing, outdated or unavailable to that user. Then consider whether retrieval, instructions or presentation need investigation. An employee requesting information outside their permission does not by itself justify granting access. Where two approved documents disagree, ask the source owner to resolve the conflict. Record the current uncertainty rather than changing the assistant to favour whichever statement arrived in the latest feedback.
Review evidence within the right audience
Let reviewers see only the information needed for their role. A general improvement board can hold a sanitised issue summary while restricted evidence stays in the approved workspace. Decide who may inspect conversation records and how long review material should remain available under the organisation own rules. If a report suggests information was disclosed unexpectedly, use the established incident process instead of leaving it in the ordinary wording-improvement queue.
Follow one fictional report to a decision
In a fictional example, an employee reports that a stock-return answer names a retired internal form. The reviewer checks the cited procedure and finds that its source still names that form. The procedure owner supplies an approved correction, and the team verifies that the assistant now uses the current source. They also check a related return question. The report closes with the source correction and verified result, rather than an unexplained claim that the model learned.
Verify closure and look for repeated causes
Repeat the reported task after a change and check relevant existing cases before marking it resolved. Tell the reporter whether the source changed, the application changed, clarification was needed or no change was accepted, with a reason. Group repeated reports by cause to find issues that deserve a planned fix. Keep useful examples for the release review using approved test data. Report volume alone does not establish answer quality; it also reflects usage and willingness to report.