This is really sad that developers would allow thsi to happen!!! Now when adding a phone number the system will not allow you to scroll down to the bottom to assign the agent, so I have to reduce my Browser down to 50% so I can see remaining fields. Then when I finally am able to assign the number to an agent, it will not save. I can no longer setup clients on the platform and in fact am actively searching for alternatives as My clients were promised something running soon. VAPI is now completely useless as I can no longer assign agents to phone numbers which is a huge important part of using this tool!!!

Yeah, that’s a pretty critical failure for a platform like VAPI especially when the UI itself is blocking core setup flow and changes won’t persist after assignment. I’ve dealt with a few cases lately where browser rendering/state issues and broken save actions on VAPI caused onboarding bottlenecks like this, so I get why you’re already looking at alternatives. Happy to take a closer look with you if you want another set of experienced eyes on it. @Larry

I am able to save the agent , I had to reduce the browser to 50% then re-enlarge it to 75% and it allowed me to save!! Thats what I really needed to get done, so I am in better shape now. But seriously, come on developers!!!!! In todays day and age you CANNOT make a web interface that glitches like this! where is quality control? Where are the managers overseeing development? This is such a amutuar bug that I cant beleive VAPI missed this!!!

Glad you managed to get it saved that definitely sounds like a broken responsive/container overflow issue in their phone number modal rather than user error. Honestly, bugs like “can’t scroll to required fields” slipping into production usually point to rushed UI updates or poor regression testing, especially on core onboarding flows. If you captured the behavior on video, that’s actually useful evidence because it makes the issue impossible for their dev team to dismiss. @Larry

They fixed ! It is now working and scrolling fine, I see they did a main website update just recently, I wonder if that had anything to do with it.