Report a wrong chatbot answer, straight from the conversation

No AI system is right every time. The question that matters is what happens when it is wrong. Who finds out? How quickly? And what reaches the people who can fix it?

Until this release, the honest answer for most chatbot platforms, ours included, was "an email, a screenshot and a lot of back and forth". Gydr 3.2.8 replaces that: you can now report a wrong chatbot answer from the conversation itself.

Report an issue, from where it happened

In Visitors, open a conversation and choose Report an issue. Tick the replies that were wrong, add a note against any of them, pick what went wrong, and send.

You do not need to describe the setup, copy the transcript or explain which widget was involved. Everything we need to investigate is attached automatically, including the conversation and the context of each reply. You see the report's progress on the conversation, and we tell you when we have looked into it and how it was resolved.

Reports keep a copy of the conversation so we can investigate. If a visitor asks you to erase their data, you can remove a report and its stored copy from the conversation view. A visitor's right to be forgotten outranks our convenience in debugging.

A report belongs to the person who filed it

A week later, in 3.2.9, we gave reports a few more rights. You can see every report you have filed, from the conversation it was filed against. While a report is still waiting to be looked at, you can revise it: the category, your comment and your notes on individual replies. And while it is open, you can withdraw it.

A withdrawn report is closed for good. Nobody on our side can reopen it, work on it, or read it as though you were still asking. We made that rule deliberately. Feedback you have taken back is not ours to keep using.

Fixing the class, not the instance

A report is most useful when the fix reaches beyond the one conversation. When we investigate, we look for the shape of the failure, the kind of question, data or wording that produced it, and fix that, so the next variation of the same mistake is caught too.

Gydr 3.2.8 also shipped a fix of exactly that kind. A reply could state a price or a hotline number that appears nowhere in your knowledge base. Since 3.2.8, your chatbot checks every figure it is about to quote and will not state one it cannot support. The rule is not tied to one product or one number. It applies to every figure in every reply.

Why we built it

We believe the companies that win with AI will be the ones that close the loop fastest between "the assistant got this wrong" and "it will not happen again". That loop has to run through the people who see the mistakes first: you.

Frequently asked questions

How do I report a wrong chatbot answer in Gydr?

In Visitors, open the conversation and choose Report an issue. Tick the replies that were wrong, add a note to any of them, pick what went wrong and send.

Can I change or withdraw a report?

You can revise a report while it is waiting to be looked at, and withdraw it while it is open. A withdrawn report is closed for good.

What if a visitor asks me to erase their data?

Remove the report and its stored copy of the conversation from the conversation view.

The full list of changes is in the 3.2.8 release notes.