@RaSheem Barnett I asked support directly when looking at the enterprise plan. T1 enterprise is 20 concurrent inbound, outbound both Web and phone at an 'account' level which is the highest in the tree, i.e the main one you log in to. The other sub accounts or Orgs share this limit. This in my mind is pointless having orgs, you may aswell set up new accounts, hence why im looking at building a tool to automate this as its not in the api. However it's always worth testing the limits if you have the means? I could test web versions, but I don't have ten mobiles lying around, however I suppose I could get one accounts assistants to call the others off of multiple numbers simultaneously to test it... seem like madness... but...

@RaSheem Barnett i do use my own twilio account numbers but I've not tested it. But I'll try and see what happens. I suspect they will change the model, and it probably why the orgs are there as segmentation. I suspect they are trying to force people to monthy recurring per account to get their mrr up to a certain level to get more funding for growth. The pay as you go model is unsustainable from a growth perspective as its not guaranteed revenue and relies on the customer (us) making or receiving a volume of calls.

Ok I'll start, examples: - connect automatically to their email calendar and email for management of sending emails and bookings. - Visual Dashboard of data that's not vapi but branded, client urls. - Web based voice for their websites but with interactivity. Think you talk to the assistant and it shows you data. Think minority report 🤔 - Time based assistant schedule, eg. Divert to ai 9pm - 7am. Phone during the day. - Agent memory, user call memory... each phone number keeps history. - Caller based redirects (phone number triggers). - Auto email lead parse and call. You enter a unique email address in the form on a website (or where ever). As soon as the assistant gets it it triggers a call. Simple to integrate in any Web form - Call block list for phone assistants or fingerprint for Web based assistants - abuse mitigation, spam - Web form user login management for Web based assistant with payment option.This is for subscription based assistants where you'd want to limit access. Good for training systems. - Geo fencing. User go's in to or out of an area make a phone call... upsells galore. - Custom Web interfaces for Web based voice assistants. - Campaign level metrics could be assigned and managed by creating a a 'campaign' and then using an interface where you could use post call analysis prompts and rubric to set the success or failure plotted against campaign . The potentially change graphing visuals .

just use phantombuster - google it.