Howdy,
We’re receiving too many “Knowledge Gaps” notifications in the backend, although we’re happy with the answers given by the chatbot. How can we eliminate or suppress this condition?
Also, I would like to request your developers look into the benefits of connecting “Like” and “Dislike” clicks to the “Knowledge Gaps” logic to improve the frequency of notification triggers.
Thank you!
Hi there, @Petar_Dietrich 
Do I get it right that you’d like to receive knowledge gaps only if user disliked the response?
If you want to keep this feature enabled, but revise its logic only, could you please share the bot’s response for the knowledge gap from your screenshot? We’d be happy to review it 
Hi @Max,
No. Pardon the confusion. Just wanted to see if you guys can revisit the logic behind “Knowledge Gaps” notifications. Make it “smarter” so I don’t see a notification for nearly every chatbot answer provided.
The other (best) option would be to provide a toggle switch in the configurator that will allow us to disable “Knowledge Gaps” notifications. Since our team reviews every chatbot answer, we train our bot accordingly. We really don’t need to be “reminded” about potential knowledge gaps all the time.
I hope this helps. Thank you.
Got you, thanks!
Please let me consult with the devs. I’ll get back to you once I have any news
Hey @Max,
One other thing… can you share this with your developers as well? Correction needed. Using “Resolve” instead of “Resolved” suggests further action. Thank you.
In this case, Resolve is used intentionally as an action label. Since this option is something the user clicks to perform an action, the verb form is more natural here. Resolved on its own could sound more like a status, as if the knowledge gap has already been resolved.
In the detailed view, we use Mark as Resolved because there’s more space and the full action can be shown more clearly. In the compact menu, we shortened it to Resolve while keeping the same meaning.
Technically and to be consistent, “Resolved” is the term that should be used. It agrees with the checkmark next to it. In short, I think it’s just a typo. Oh well…
PS: Standing by for your developers input on my other request 
We keep getting a “Knowledge Gaps” notification for every single chat conversation.
Thank you!
I understand your reasoning, Petar. The current label follows our UI wording approach, where compact menu items are shown as actions, so Resolve is used here intentionally.
We’ve still shared your consistency note with the product team as feedback, but there’s no planned change to this label at the moment.
Regarding the Knowledge Gaps question, I’ll update you here as soon as I have any news
Unfortunately, it’s impossible to send disliked responses to the Knowledge Gaps section, but I’ve added this idea to the Wishlist. Feel free to upvote it: Send thread to Knowledge Gaps if users disliked the response
Regarding the knowledge gaps logic, our devs are currently analyzing existing prompts. I’ll update you as soon as I have more news
