​ To learn more, see the sources I considered: [[1] Retell transfer_call delay (never transfers immediately without a response)](https://discord.com/channels/1186424376300679209/1416864938487447644) [[2] Transfer call](https://docs.retellai.com/build/single-multi-prompt/transfer-call) [[3] Issue with the Transfer agent not completing the transfer](https://discord.com/channels/1186424376300679209/1444633634744045703) [[4] Call Transfer Node](https://docs.retellai.com/build/conversation-flow/call-transfer-node) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer --- This is a known behavior where the LLM waits for user confirmation before executing the transfer. Here are some approaches to improve reliability: 1. Use a custom, specific function name [(1) ]() Give the transfer function a descriptive custom name like

transfer_to_luke

instead of a generic name—this helps the LLM properly identify and call it. 2. Update your prompt with explicit instructions [(2) ]() Incorporate the transfer call conditions clearly into the prompt. For example: "If the user requests to speak with a human, use the transfer_call tool immediately." [(3) ]() You can also try adding language like "after answer always call function 'transfer_call'" to ensure the function fires without waiting. 3. Ask a confirmation question before transferring [(1) ]() Instead of having the agent say "Please hold while I transfer you" and then wait, prompt the agent to ask something like "Are you ready to be connected?" and then trigger the transfer immediately after the user responds. 4. Try a different model If you're using GPT-4o mini, try switching to 4.1 mini—the transfer behavior relies on the model's tool calling capabilities, so model choice can affect reliability. 5. If using Conversation Flow, use the Call Transfer Node [(4) ]() If you want the agent to say something like "Let me transfer you right away" before transferring, put a conversation node (with

skip response

turned on) before the Call Transfer Node. The Call Transfer Node itself does not speak—it just executes the transfe

r.