We are testing a demo of a personalized conversational bot that should use the historia_personal.json file to respond based on real user data. However, the bot is not accessing the file, and is responding with generic or invented content not present in the data. @Sahil assistent id: df57a123-88bd-422e-a8fc-4ef0a33052c9 https://cdn.discordapp.com/attachments/1380582628771758111/1380583123770933299/image.png?ex=684467ba&is=6843163a&hm=1fc1f06cf5999fdb9f47b75c65452e05b4fadd07ffdca3bb79a12acf33d2e03a& https://cdn.discordapp.com/attachments/1380582628771758111/1380583124248821780/image.png?ex=684467ba&is=6843163a&hm=7313c70f33d506432f931c98c22a7fe80738708a7bce3049fb5ca7af19926adf&

To ensure your assistant uses

historia_personal.json

, make sure the file is uploaded and attached via a Query Tool. Here’s a quick API example to attach the file to your assistant:

bash
curl --location --request PATCH 'https://api.vapi.ai/assistant/df57a123-88bd-422e-a8fc-4ef0a33052c9' \
  --header 'Authorization: Bearer <YOUR_API_KEY>' \
  --data '{
    "model": {
      "provider": "openai",
      "model": "gpt-4o",
      "toolIds": ["<QUERY_TOOL_ID>"]
    }
  }'

Replace

<QUERY_TOOL_ID>

with the ID of your Query Tool that references

historia_personal.json

. After updating, test your assistant to confirm it responds with real data from the file. [See full guide](https://docs.vapi.ai/knowledge-base/using-query-tool#step-3-attach-the-query-tool-to-your-assistant) Source: - [Using the Query Tool for Knowledge Bases](https://docs.vapi.ai/knowledge-base/using-query-tool)

example @User @Sahil

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!