Alexander
08/20/2026, 12:25 PMAI Evy
08/20/2026, 12:25 PMAI Evy
08/20/2026, 12:26 PMAI Evy
08/20/2026, 12:26 PMAI Evy
08/20/2026, 12:26 PMAlexander
08/20/2026, 12:30 PMAI Evy
08/20/2026, 12:30 PMAI Evy
08/20/2026, 12:30 PMcall_id if you want Retell to handle the call — but since you don't want inbound calls going to the agent, you would skip this step for calls arriving on your retail number and instead route them directly to your call center using your telephony provider's own dialing/transfer capabilities .
3. If you did want to route certain calls to Retell, you would construct the SIP URI as sip:{call_id}@sip.retellai.com and dial the call to that URI within 5 minutes of calling Register Phone Call .
4. The docs state that "all traffic looks like inbound to Retell" with this method, so "it's up to you to specify the call direction" — meaning the logic to decide "this call should NOT go to the AI agent" has to live in your own telephony/webhook code, not in Retell.
For the Elastic SIP Trunking method (used with Twilio, Telnyx, Vonage, or contact center platforms like Avaya) , the docs describe importing a number and binding it to an agent , but don't document a way to conditionally send only some inbound calls to a different destination outside Retell.
I don't have exact steps in the sources for splitting inbound vs. outbound handling on the same number to bypass the agent entirely. This would likely need to be configured on your telephony provider's side (e.g., inbound routing rules that never touch Retell for calls toAI Evy
08/20/2026, 12:30 PMAI Evy
08/20/2026, 12:30 PM