I hope you’re doing well. I am experiencing an issue with the knowledge base interface where the AI voice chat does not seem to capture or utilize the knowledge from uploaded documents. Issue Details: - After uploading a document to the knowledge base, the AI voice chat does not reference or retrieve information from it. - The document uploads successfully, but the AI does not seem to recognize its contents. - The AI voice chat gives answers not based on the uploaded document. I would appreciate any guidance on resolving this issue. Please let me know if you need any additional information. Looking forward to your support, below is a video of the issue we are facing;

https://vimeo.com/1062158508/7a41c00309?ts=0&share=copy

Hi there! 👋 I understand you're having trouble with your AI voice chat not utilizing knowledge from your uploaded documents. That can definitely be frustrating! Unfortunately, I'm unable to view the video you've shared, but based on the issue details you've provided, I can help troubleshoot this problem. ## Possible Causes & Solutions ### Recent Migration to Trieve One of the most likely causes is that Vapi has recently migrated from Canonical to Trieve for knowledge base services. According to [documentation I've found](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336887159948316733), this migration requires users to re-attach their knowledge base using the API. ### Steps to Fix the Issue: 1. **Verify File Format Compatibility**: Make sure your documents are in supported formats: [Markdown, PDF, plain text, or Microsoft Word (.doc and .docx)](https://docs.vapi.ai/knowledge-base). Also, ensure file size is less than 100MB. 2. **Attach Knowledge Base via API**: Since the UI for knowledge base has been temporarily removed, you'll need to use the API to attach your knowledge base: - Follow the documentation at [https://docs.vapi.ai/knowledgebase](https://docs.vapi.ai/knowledgebase) - You'll need to properly configure parameters like

searchType

and

scoreThreshold

3. **Check API Key and Permissions**: - Verify your API key has the correct scope and permissions - If you're receiving success responses but the assistant isn't connected, check for null key fields (file_ids, dataset_id, server) in Vapi logs 4. **Knowledge Base Configuration**: - Ensure the knowledge base is properly linked to your assistant - Verify that file IDs are correctly referenced in the configuration - Try refreshing or rebuilding the knowledge base index 5. **Prompt Engineering**: - Consider explicitly instructing the assistant to use the knowledge base as the primary source of information

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!