squad transfer not working with gpt realtime
# support
k
i tried having a french agent transfering to another agent speaking arabic and that is gpt real time, when using other assistants it works but with gpt real time no.
k
GPT real-time assistants currently struggle with call transfers between multilingual agents due to model limitations, unlike standard assistants, so ensure both are compatible or use standard models for reliable transfers.
k
now tried another method of transfering and my assitant couldnt be found for inbound call it says " couldn't find assistant"
here is the assistant id: 1812ec4b-a6cc-4244-99c7-e64359355885
a
Hey, Can you send me the latest call_id?
k
hello Sahil, here it is: cd5d5bae-0111-4567-b275-693f6e5e434c. the transfer is not working.
a
Hey KONI, I looked into the Shared Call ID, and the call was transferred successfully to the assistant. If this was unexpected, could you share the following information? - 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!
k
hello, so i was expecting to talk to the arabic speaking assistant but it was blank it is at the end
v
For reliable squad transfers between multilingual agents, use standard (non-GPT real-time) assistants for both the source and destination agents. GPT real-time models currently have limitations with call transfers, especially in multilingual scenarios, so switching to standard models is the recommended solution for consistent transfer functionality. After updating your assistant configurations, test the transfer flow to confirm it works as expected. Sources: - [Configuring Inbound and Outbound Calls for Squads](https://docs.vapi.ai/squads-example) - [Call Forwarding and Transfer Documentation](https://docs.vapi.ai/call-forwarding)
a
Can you please point me to the exact duration in the recording. Also, what's the expected response that you were hoping? We don't understand Arabic.