I think that Vapi does a great job at the core feature that its built for. Which is Voice Ai Agents, and bringing together the needed APIs and services to pull off natural conversations. I think that the specifics around auxiliary features like how exactly the user is speaking to that agent (web sdk, twilio, other phone providers) are secondary to their team's priorities. ALSO, its important to note that a lot of these perceived issues showing up in this general chat can likely turn out to be solvable or due to some misconfiguration on the individual person's end (we cant rule that out). AND, its worth noting that Vapi is very much *developer first * in their current set up and roadmap. I have been able to find easier and more reliable work arounds to solve these issues, and am probably better off having a bit more control over them by just whipping up something such as conferencing to have better call transfer ability. with the voicemail detection issues, its not really Vapi's job to be detecting whether or not the call has resulted in voicemail. Atleast not enough for them to spend time on improving that. Twilio's API has a pretty good voicemail detection and set of ways to dial that in, with certain threashold values and things like this. Its twilios job to detect a voicemail, but it was nice and convenient of Vapi to include that (sort of). Keep in mind they also just got a boat load of cash and will probably be up to a bunch of good stuff in the near future.