My assistant refuses to read its supplied files in the knowledge base even when i ask the same questions 1:1 as mentioned in the added FAQ file. How do i resolve this? The same exact prompt and files work in OpenAI perfectly okay. Is this caused by a difference in how vapi and openai handle the files or is there perhaps some kind of problem with loading the files into Vapi?

@skei I'm sorry to hear that you're experiencing issues with your assistant's ability to read from the knowledge base. It's possible that there might be a difference in how VAPI and OpenAI handle files, or there could be an issue with how the files are being loaded into VAPI. To resolve this, you might want to check the following: 1. Ensure that the files are correctly formatted and compatible with VAPI's requirements. 2. Verify that the files have been uploaded correctly to the knowledge base. 3. Check if there are any specific settings or configurations that need to be adjusted for VAPI to access and read the files properly. 4. Make sure that the assistant is correctly referencing the knowledge base when attempting to answer questions. If you've already checked these and the problem persists, it might be necessary to look into the logs or error messages, if any, that are being generated when the assistant fails to read from the knowledge base. This could provide further insight into what might be going wrong. If you need more detailed assistance or if the issue is not resolved, please reach out to support for more info on this. They will be able to provide you with specific guidance tailored to your situation.

I believe this is caused by how openai and vapi tokenize the inputted documents. I think vapi uses trieve as a provider for that and it bears inferior results

@skei This is the same issue I ran into, they don't seem willing to acknowledge their big mess up that caused our clients to be called liars and our assistants to hallucinate overnight. VAPI just didn't tell anyone outside of a Discord message and the dashboard interface still creates the KB files in a basically non-existent provider without any error warning at all. So you think the KB is working, but it's not. Only solution for now is to create the KB using their API and upload files using their API by using the new provider. Make sure to set the Threshold higher than the 0.1 in their documentation, which is an awful way to present a default and will keep making it lie if you have a lot of docs. Should be at least 0.7

Oh i appreciate it, thanks

@skei can you share the call id for which KB is not working.

uhm there was a workaround that made it work

@skei checking if I can close this ticket.

yeah sure