https://retellai.com/?utm_source=discord&utm_medium=seo logo
- If I require both EXT navigation and IVR navigat...
# ❓・ai-evy-support
r
@AI Evy - If I require both EXT navigation and IVR navigation, how to configure that in warm transfer? Can dynamic routing prompt handle EXT as well? Or will that come in IVR navigation as well?
a
Thanks for tagging me @Rakshit Kalra. I'll look through relevant sources and get back to you shortly.
### Answer For warm transfers that require both extension (EXT) navigation and IVR navigation, you can configure both capabilities within the transfer call settings [(1) ]() . Extension Configuration: You can set the transfer number extension directly in the transfer call tool settings. Extensions must be 0-9, '*', '#' (e.g., 123#) . IVR Navigation Configuration: For warm transfers specifically, you can configure IVR navigation through the "Navigate IVR" setting. You provide a prompt to help the agent navigate if the transfer target is an IVR system . How They Work Together: The extension field handles direct extension dialing, while the Navigate IVR prompt guides the AI agent through interactive voice response menus using the press digit functionality [(1) ]() [(2) ]() . The Navigate IVR prompt should include clear instructions on when and what digits to press, similar to the guidance in the Press Digit documentation [(2) ]() . You can specify preferred navigation keywords, keywords to avoid, and guidance for uncertain situations . Both settings can be configured simultaneously in your warm transfer configuration, allowing the agent to handle extension dialing first, then navigate any subsequent IVR menus it encounters [(1) ]() .
​ To learn more, see the sources I considered: [[1] Transfer call](https://docs.retellai.com/build/single-multi-prompt/transfer-call) [[2] Press digit (IVR navigation)](https://docs.retellai.com/build/single-multi-prompt/press-digit) ​
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
r
@AI Evy I want EXT to be dynamically selected based on context of the call and then I want the IVR to be handled - again on the context of the call. How would I configure that?
a
Thanks for the follow-up, @Rakshit Kalra. I'll get back to you soon.
### Answer For dynamic extension selection based on call context, you can use dynamic variables in the extension field [(1) ]() [(2) ]() . Dynamic variables allow you to inject personalized data that gets substituted at runtime [(3) ]() . Extension Configuration: Set the transfer number extension to a dynamic variable like
{{selected_extension}}
instead of a static value [(1) ]() [(2) ]() . The extension must be 0-9, '*', '#' (e.g., 123#) . Dynamic Variable Setup: You can set dynamic variables through: - Agent-level default dynamic variables as fallback values [(3) ]() - Runtime substitution when initiating calls via API in the
retell_llm_dynamic_variables
object - Inbound Call Webhook for incoming calls IVR Navigation Configuration: For context-based IVR navigation during warm transfers, configure the "Navigate IVR" setting with a prompt that instructs the agent how to navigate the IVR system [(1) ]() [(2) ]() . The prompt should guide the AI on when and what digits to press based on the call context . Combined Setup: In your warm transfer configuration: 1. Set extension field to
{{selected_extension}}
or similar dynamic variable 2. Provide a Navigate IVR prompt that includes conditional logic based on your call context (e.g., "If the caller needs billing support, press 2. If they need technical support, press 3.") The agent will first dial the
dynamically determined extension, then use the Navigate IVR instructions to handle any subsequent menu navigation based on the call context .
​ To learn more, see the sources I considered: [[1] Transfer call](https://docs.retellai.com/build/single-multi-prompt/transfer-call) [[2] Call Transfer Node](https://docs.retellai.com/build/conversation-flow/call-transfer-node) [[3] Dynamic Variables](https://docs.retellai.com/build/dynamic-variables) ​
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
Thanks for the follow-up, @Rakshit Kalra. I'll get back to you soon.
r
@AI Evy - Isnt extension also DTMF? can't IVR navigation press multiple digits and pound key as needed to do EXT dialing on behalf of the user?
a
### Answer You're correct that extension dialing is also DTMF-based. However, Retell AI provides two separate mechanisms for handling these scenarios: Extension Field vs. IVR Navigation: The extension field in the transfer call configuration is specifically designed for direct extension dialing [(1) ]() [(2) ]() . Extensions must be 0-9, '*', '#' (e.g., 123#) . This field handles the extension input as part of the initial call setup. IVR Navigation for Post-Connection Menus: The "Navigate IVR" setting with the Press Digit function is designed to handle interactive voice response menus that occur after the call connects [(3) ]() [(1) ]() [(4) ]() [(2) ]() . The Press Digit function allows the agent to press digits based on what the IVR system says [(3) ]() [(4) ]() . Why Use Both: While technically both use DTMF tones, they serve different purposes in the call flow: - The extension field handles immediate extension dialing during call setup - IVR navigation handles menu navigation after the call is answered by an automated system Practical Consideration: Based on a community discussion, IVR navigation after a warm transfer may have limitations [(5) ]() . One user asked about using IVR functions after a warm transfer, and it was indicated this might not be ful
ly supported at that time . For your use case of dynamic extension selection followed by IVR navigation, you may need to test whether the Navigate IVR prompt can handle the complete sequence, or if you need to use the extension field for the initial extension and Navigate IVR for subsequent menu navigation [(1) ]() [(2) ]() .
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.