How to Report a Wrong AI Answer, Wrong Data or a Disputed Score

WISEcode AI is in Beta, and the fastest way to make it better is to tell us when it misses. This article explains how to report a chat answer you think is wrong, a product record with wrong data, and a score you dispute — and what happens to each report.

A chat answer looks wrong

1. Use the thumbs down on the response. Every response in chat has thumbs up and thumbs down. A thumbs down reaches the WISEcode team with the conversation attached, so you do not need to copy anything. Add a line about what was wrong if you can.
2. Ask chat to check. Chat can answer from what it knows or by checking your data and the WISEcode canon. If an answer seems off, ask it to verify: “Check that against my portfolio” or “Confirm the processing level for that ingredient.”
3. If it matters for a decision, submit a request. Lead the subject with “WISEcode AI” and include what you asked, what chat answered, what you expected, and the product UPCs involved. A member of the WISEcode team will review it and get back to you.

Check anything you are going to publish or share externally. Chat tells you what it can and cannot see; when it has only part of a dashboard in view, it says so and offers to count across your full catalog.

A product’s data is wrong

If the wrong information is on one of your own products — ingredients, Nutrition Facts, name, image — fix it yourself: tell chat what to change, confirm, and publish the edits. See Adding and Editing Products Through Chat.

If the wrong information is on a product that is not yours (a competitor in a comparison, a product in a category view), or on WISEcode’s catalog data behind your product, submit a request with the UPC, what is wrong, and the correct value or a label photo. Data corrections go to the WISEcode data team; the fix appears in WISEcode AI and the consumer app once the catalog entry is updated.

You disagree with a score

1. Ask chat to audit the product — “Why does UPC … score the way it does?” — or open the Product Insights dashboard (“Audit a product”). It names the ingredients, sugar penalty, or Unique Ingredient of Concern driving the score.
2. Check the product’s own data first. Most disputed scores trace to an ingredient list or Nutrition Facts panel that is out of date, an estimated added-sugar value, or a compound ingredient that has not been broken down. See “But My Label Says No Added Sugar” - Troubleshooting an Unexpected Sugar Penalty.
3. If the data is right and you still disagree with how an ingredient is classified, submit a request with the UPC, the ingredient, its manufacturing route, and any documentation. Classification questions go to the WISEcode Science Team for review; borderline assignments are reviewable under the Standard.

Something is broken

A dashboard that will not load, a chat that times out, a file that will not upload, a product that will not publish even though nothing is missing: submit a request with what you were doing, what happened, a screenshot, and the time. Known issues at launch are listed in What’s not yet available in the WISEcode AI Beta.

What happens to your report

• Thumbs-down feedback is reviewed regularly with the product team and shapes prompt fixes and what gets built next.
• Requests are reviewed by a member of the WISEcode team, who will get back to you. You receive a confirmation with a ticket number as soon as you submit; reply to it any time to add detail.
• We do not send a follow-up for every individual data fix, but corrections appear in the product once made.