Hey Kasey! Currently, Knowledge Agents will always return 10 sources to be used to answer a question, that said, just because it’s returning those sources does not mean all those sources are being used to generate the answer.
We recently improved the answers editing experience in the AI Agent Center, so if you specifically add a source to an answer, it will tie that source to that question in the future. So in other words, adding the correct source to the answer is a more effective way of “training” the Knowledge Agent than removing superfluous sources.
Hey Kasey! Currently, Knowledge Agents will always return 10 sources to be used to answer a question, that said, just because it’s returning those sources does not mean all those sources are being used to generate the answer.
We recently improved the answers editing experience in the AI Agent Center, so if you specifically add a source to an answer, it will tie that source to that question in the future. So in other words, adding the correct source to the answer is a more effective way of “training” the Knowledge Agent than removing superfluous sources.
Hi @Noah Carpenter ! Do you have screenshots or a link to a help center article explaining this? The scenario that I am encountering is:
- A question is asked and the Agent says no direct answer was found.
- I go to edit the answer, and I see that the Guru card which contains the answer to this question is listed as one of the sources.
- I remove all of the irrelevant sources.
- The Agent is now providing a correct answer once the only source listed is the relevant card.
So while I do see the field for adding a source, I can’t necessarily use that when the card in question is already listed as a source.
@Kasey Ah I see, in the case where the source is already showing up in the list you’re correct that you can’t add the source and thus can’t boost it to be added. This is a known gap for us and is something we plan to improve.
In the meantime however, the fact that the correct source is showing up but is not generating the correct answer feels like a bug - if you open up a support case we can take a look at what’s happening and try to get this sorted!