I've been having this issue where the Dutch agent doesn't transfer the call when it is supposed to. 67d8fea8-4c5f-428e-a7c5-8ef44879e9e6

Hey @Saien | Exousia AI To help track down this issue, could you share: - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help me figure out what went wrong!

The timestamp is 01:14 The response I expected was for the call to be forwarded to the forwarding phone number that is set up for the assistant Instead, the assistant gave the following response: "Bedankt. Ik ga je nu door verbinden met een klantenservice medewerker die je verder kan helpen Een ogenblik geduld alstublieft. Verbind door naar Pluz dertig, twintig, vierhonderd, vier en vier rennen naar vier voor." And this translates to "Thank you. I will now connect you to a customer service representative who can help you further. Please wait a moment. Connect to Pluz thirty, twenty, four hundred, four and four run to four for." Looking forward to your response, thank you!

@Saien | Exousia AI the transfer didn't worked because of KB files. We are working on complete revamp of the KB providers and files which will be completed by end of this week. So, I suggest either to wait till this week to use KB or try the call again by removing these KB files. Let me know your decision.

Thank you for the update. So wait till Sunday?

@Saien | Exousia AI as your issue is resolved, can i close this ticket?

Hi, my issue is not resolved yet. 460d1777-e10f-43d2-8270-6a6bc07a761d at 0:33

@Saien | Exousia AI we have pushed new changes related to KB, which you can find here https://docs.vapi.ai/knowledgebase . Try it out and let me know how it goes.

The thing is, I don’t see anything different as it relates to this document. I’ve already been following these best practices

Surprise, can you share the recent call ID with the new KB development? Now it shouldn't interfere with the in-context processes such as transfer.

This is the most recent call from last night

The changes are released in the afternoon. As mentioned

canonical

is no longer KB provider with Vapi. So, please try out new changes.

json
      "knowledgeBase": {
        "topK": 2,
        "fileIds": [
          "64e1e7c7-dc40-4fae-bfbe-43364d69c4f2",
          "0ec966d8-e8d7-4039-ae8d-0de6c7d6e393"
        ],
        "provider": "canonical"
}

So literally just change the provider name from canonical to trieve?

The new vapi voice library layout is shit, the Dutch agent options are also gone, we use it for our operations and what now??

No the underlying tech is also changed, and few more things are about to announced.

Hi I haven’t had a chance today but I will check tomorrow and get back to you. Thanks for checking