Just dropped an updated comparison video for 7 AI Voice Agent Platforms! I compare these platforms in 4 different categories, Sound, Speed, Cost & Integrations. I've also uploaded all of the test calls with recordings in a CSV file, you can check it out in my Skool community linked in the video.

Client: “Why should we pay monthly support if the voice AI is already built?” Fair question. But here’s the reality. Voice AI is not plug-and-play. It’s a system stitched together with at least 5 moving parts: 1. An orchestrator like Retell AI or Vapi, 2. An automation engine like n8n or Make, 3. Telephony providers like Twilio or Telnyx, 4. VoIP systems forwarding calls, 5. And finally CRMs or databases storing the results. And guess what? Even if 4 work perfectly, if 1 fails, your customer call fails. Just yesterday, we noticed during monitoring that call transfer failed for one call. Client had no idea. Turned out, Telephony glitched for a few minutes. Not our code. Not the AI. But the end result? Business may have lost an opportunity. We investigated, added fallback prompts to avoid this in the future, tested again, and shielded the client from chaos. That’s why monthly support is not a “nice-to-have.” 𝗜𝘁’𝘀 𝗶𝗻𝘀𝘂𝗿𝗮𝗻𝗰𝗲. 𝗜𝘁’𝘀 𝗿𝗲𝗹𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆. 𝗜𝘁’𝘀 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗰𝗼𝗻𝘁𝗶𝗻𝘂𝗶𝘁𝘆. If you’re a business owner deploying voice AI, think of support as fuel, not cost and if you’re building for clients, your job is to help them see the invisible value. Truth about monthly support in Voice AI (Linkedin Post with screenshot of production issue) https://www.linkedin.com/posts/connectwithamitgupta_vihuai-voiceai-businesscontinuity-activity-7369151551766024193-PRg7?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAR9sUsBQFtFnNDvcM7vnvjh1Cj0gkqUWs8

Hey Guys, Question for exp folks. I have built many agents with Retell, Twilio/Telnyx and N8N/Make but one issue is across the clients. Everyday 2-10 calls being dropped under ten seconds, or just after greeting, or even before greeting sometimes etc. I am observing more such call drops over Telnyx than Twilio but can't conclude if the telephony has an issue. Inspected the SIP logs in telephony and everything looks good. Not sure, what else to investigate. I would like to ask two questions. 1. Are you seeing this in your builds too? 2. How do you conclude if this was the user who dropped or an issue in Twilio or retell ai itself ? Q: how to troubleshoot dropped calls in Retell/Twilio? @Brendan Jowett are you able to help ?

If the service I’m selling cost around 1000 bucks for each customer, how I’m gonna charge him a $800 retainer ?

Hey Everyone, I have been using Twilio for long time and recently started exploring Telnyx. It is much better to show the SIP call flow, logs and debugging. Just sharing the two days worth of troubleshooting with Telnyx to save you time and effort if you encounter these two issues in Retell AI with a Telnyx phone number 1. Inbound calls going busy -- Change the phone number format to E.164 or +E.164 under SIP trunk inbound routing settings. 2. Outbound calls not connecting - just use "sip.telnyx.com" instead of FQDN which include the SIP trunk name in the URL on the retell side under SIP URL field (when you import a phone number) Solved: Retell AI - Telnyx Calling