Example of the callId: 9dcedb24-112c-4adc-95a9-dedb06c6df2c In logs, we can see that the Model called tool: transferCall() a few times, but the transfer never happened. The same flow was working yesterday, e.g. call ID 7c1f95d5-4b44-4b4d-a6d8-2a472ec7a418

message has been deleted

@Vapi no errors in the logs, and we don't see any transfers on the twilio side The transfer phone number is 14153197882

@Anastasiia Kryhina It's quite unusual that there are no errors in the logs and yet the transfer didn't occur on Twilio's side. Since the same flow was working previously, it's possible that there might be an intermittent issue or a change in the environment that's affecting the transferCall function. To proceed, I would recommend the following steps: 1. Double-check the transfer destination number (14153197882) to ensure it's correct and capable of receiving calls. 2. Verify that there have been no changes to the Twilio account settings or permissions that might prevent transfers. 3. Review any recent changes to the call flow or application code that might affect the transferCall function. 4. If possible, attempt to replicate the issue with a test call to see if the problem persists. If after these checks the issue remains unresolved, please reach out to support with the specific call IDs and any relevant information so they can investigate further. If you need assistance with any of these steps or have additional questions, feel free to ask.

@Vapi we double checked and here's more information Yesterday we implemented a change to support the passing of CallerID https://docs.vapi.ai/api-reference/assistants/create#request.body.model.custom-llm.tools.transferCall.destinations.number.callerId Yesterday the transfer call with CallerID worked successfully. No code changes were made, but today call transfers no longer work for us. We just tried to remove the caller ID in one environment, and transferCall worked as expected. What can be the reason for such inconsistency on the same use case? We initiate the calls using dynamic assistant and we may use different numbers for the transfer, but it's possible we configured the tool poorly. Could you please advise how we should configure transferCall tool and what parameters we should use for calling it? Successfull call ID: 7c1f95d5-4b44-4b4d-a6d8-2a472ec7a418 Unsuccessfull Call ID: 9dcedb24-112c-4adc-95a9-dedb06c6df2c

@Anastasiia Kryhina Thank you for providing additional details. It seems that the issue might be related to the CallerID feature that was recently implemented. If removing the CallerID resolves the issue, it's possible that there might be restrictions or configurations within Twilio or your telephony provider that are affecting the use of certain CallerIDs. Here's how you should configure the

transferCall

tool with the CallerID parameter: 1. Ensure that the CallerID number you are using is verified with Twilio and is allowed to be used as a CallerID. 2. Make sure that the CallerID number is in E.164 format, which typically means a

+

followed by the country code and the phone number. 3. When configuring the

transferCall

tool, you should pass the destination number and the CallerID in the correct format. Here's an example of how to structure the parameters:

json
{
  "destinations": [
    {
      "type": "PhoneNumberTransferDestination",
      "number": "14153197882",
      "callerId": "+1YourVerifiedCallerIDNumber"
    }
  ]
}

Please replace

+1YourVerifiedCallerIDNumber

with the actual CallerID number you wish to use, ensuring it's in the correct format and verified. If you continue to experience inconsistencies, it's important to check with Twilio's support to see if there are any issues on their end that could be causing this behavior. Additionally, ensure that your dynamic assistant is configured to handle different numbers correctly and that there are no conditional flows that might be affecting the transfer based on the CallerID or other variables. If you need further assistance with configuring the

transferCall

tool or if the problem persists, please reach out to support for more detailed investigation.

@Vapi I need further assistance - we cannot configure transferCall in a suggested way because we configure it before we learn callerId. We know callerId only when we call the previously configured transferCall

@Anastasiia Kryhina Understood. If you're configuring the

transferCall

tool before you know the CallerID, you'll need a way to dynamically set the CallerID at the time of the call. Here's a general approach you could take: 1. Configure the

transferCall

tool with a placeholder for the CallerID. 2. Once the call is initiated and you have the CallerID, update the

transferCall

configuration with the actual CallerID. 3. Execute the

transferCall

with the updated configuration. Since you're using a dynamic assistant, you should be able to update the call configuration on the fly. However, if your system doesn't support updating the CallerID dynamically after the assistant configuration, you may need to look into a different approach or modify your system to allow for this functionality. If you're still facing difficulties, it might be best to reach out to the support team with the specifics of your setup. They can provide more detailed guidance based on how your dynamic assistant and the

transferCall

tool are configured. Please ask support for more info on this.

@User could you please assist us?

@Anastasiia Kryhina the call was transfered can you check with twilio what's stopping them from forwarding the call. Twilio Call Sid: CA59cf0258e7d80f2f8201eeab28eb7da1 https://cdn.discordapp.com/attachments/1317142221723533332/1317390247671107664/Screenshot_2024-12-14_at_12.40.47_PM.png?ex=675e82c6&is=675d3146&hm=7bdfe475809014feaf4e2ab1a5b2db3b6a7ed729d838218f33778db17292d472&