### Answer Based on the documentation, there isn't a separate "transfer agent" type—**Agent Transfer** refers to the feature/action of switching from one AI agent to another during a call, not a distinct agent category. [(1) ]() [(2) ]() How Agent Transfer works: - It enables you to modularize tasks and re-use specialized agents (e.g., a front-desk agent transferring to an appointment-booking agent) . - The destination agent has access to the full conversation history, so there's no need for re-introductions or repeated questions. - The transition is near-instant with lower latency than phone-based call transfers. For your setup: You would create a normal agent for the destination, then use the Agent Transfer tool/node to transfer to it by specifying that agent's ID and version. Key settings behavior: - Settings like

optInSignedUrl

,

optOutSensitiveDataStorage

, and

webHookUrl

from the first agent persist throughout the call. - Other settings (language, voice, voiceModel, max call duration, responsiveness, end call on silence) follow the currently active agent after transfer. [(1) ]() [(2) ]() [(3) ]() So in short: build your second agent as a regular agent, then configure Agent Transfer to route to it when needed.

​ To learn more, see the sources I considered: [[1] Agent Transfer](https://docs.retellai.com/build/single-multi-prompt/transfer-agent) [[2] Agent Transfer Node](https://docs.retellai.com/build/conversation-flow/transfer-agent-node) [[3] Discord message from @tomjennings25 on 2025-12-08](https://discord.com/channels/1186424376300679209/1294891368505937952/1447644511969738956) ​

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