Like it'll sound a bit silly just to make that one tweak but right now the % of users (especially non-technical users on your platform) to be able to do that has like tiny % success rate... Like they'll probably in general just chalk it up to "Oh I thought that was just how things worked..." Without looking into workarounds/solutions. B/c what it takes is only via an update assistant api call - along with ALL of the rest of the configurations within the JSON payload to make sure that one tiny field is changed without breaking anything. Like someone has to literally: 1. Learn how API calls work 2. Learn how vapi API calls can work 3. Learn how update assistant API call work specifically 4. Learn how the transferCall function as part of the tools array as part of the model object work specifically 4. Learn how to translate their current configs (if they built it via UI) into JSON format for update assistant API call 5. Then execute on all of the learnings for that one update assistant api call to change the configuration of the callerId for that one assistant. Then they have to repeat that for X outbound assistants they have. Which mind you outbound generally is responsible for vast majority of call volumes. So vast majority of calls are negatively impacted by not having had this as a result. E.g. Any subsequent calls requires either the human OR the AI (if it's a booking agent process like ours) to re-capture the prospect's phone number to be able to do something with it like booking an appointment or moving them to next step. Like super silly imo. Not trying to throw shade, just pointing the significance/impact of this problem. And for the users who aren't able to get clear enough even on the problem, there may be slew of appointments booked with the AI outbound assistant's phone number... Which is not helpful. Show rate plummets because actual prospects don't get reminders or they forget etc. Super painful...

So my request/ask, and no of course you don't have to roll with it, is to just save people the pain of this lol Make the default config the same way you do for when someone/a user calls an assistant inbound, that's 1. Then 2. updating the UI such that it allows for a MUCH easier process of making changes away from the default if need be, for the transferCall function. This is super important because for anyone who's even trying to use vapi to attempt to bring value in a sales type of function, often will touch transferCall as the first conversion event they'll optimize for for proof of concept. But because it's 1. a default/pre-built tool vs. a custom tool, there's also not a lot of visibility/understanding for a typical non-technical builder. This is because 1. vast majority already will buckle before they get to even understanding how tool calls/function calling works, to be able to even build their own custom tool, let alone 2. understand what's possible to be customized/configured for that default/pre-built tool specifically. Like I've been trying to solve this problem by systematically overhauling our entire backend from static outbound assistants to transient outbound assistants as a whole (and I'll continue to do so) but in the process of doing that, as long as that is incomplete, we're suffering from this problem and it's super frustrating. Haven't thought to bubble it up to you guys up until now until I got a dose of inspiration/clarity from Grok 3. Plz help. Sos. lol Anyways that's all, but once again, thanks for even allowing me to do this work in the first place. Appreciate y'all

Last but not least, to really even drive the point home. Most non-technical people that will come onto your platform, probably will have an obvious insight/understanding of how valuable it can be for voice AI to be done for things like sales. And hell, whether it's for sales OR for customer service... Like ideally you want the prospect's number to be transferred to whoever communicates with them next. Those two, I wouldn't be surprised if they make up for a high volume of you guys' use cases. If this hasn't been bubbled up until this point, it's probably because 1. most people either don't move far along enough to even catch the problem, or 2. they may, even worse, just silently assume "this is just how Vapi works..." which would imo be a poor representation of the value you guys can bring to the table. But things like this is a significant deterrent from adoption, let alone retention. That's all