I am creating an app that could scale to hundreds or more phone numbers, each providing information to the caller which is unique. The question I have is how best to set up the relationship between these phone numbers and the assistants. Ideally the bulk of that unique information is stored in a knowledge base. Do I.... (A) set up an assistant for each phone number (B) set up a single assistant and load the knowledge base dynamically If (A) then doesn't scaling becomes an issue? If (B) then how the heck do I dynamically load the knowledge base associated with the phone number? And what about concurrent calls? And what kind of performance hit might there be as the knowledge base get's loaded (if this is even possible)? Any and all input on this gratefully accepted!

I mean, that's what I'm about to do, so if it's a bad idea, I'd like to know about it, lol. I'd say just make sure you're taking concurrency limits into consideration.

Are you referring to concurrency limits on a given number or on the total account? I’m pretty sure we can throw money at vapi and they will take care of account concurrency.

Yeah we can pay more for it, just saying to factor it in to overhead.

@Stickler101 I got word back from vapi that (A) should scale to very large numbers. This approach is vastly simpler.