interesting, in terms of call forwarding costs, from what I understand these are minimal? I guess you would only have an issue burning you main Org Twilio account with unsolicited or what would be deemed robo/spam calls if who was being called flagged them on mass. Thanks guys

after this you can get your SID and secret needed to add in to Vapi, this can be a bit of a pain getting it verified in vapi if a few settings are not correct.

and costs are outlined here as a per min: https://www.twilio.com/en-us/voice/pricing/au

@Dan McCoy love to know more about storytelling consulting. Not a term ill admit to hearing alot about. I'll assume is about building a narrative around a problem and guiding the prospect to a solution you (client) is selling (product, service, solution)

@Dan McCoy sounds interesting, thanks for the explanation. Was in marketing, growth hacking, seo etc for a while there before I started building software 😀. Sounds like you've told a few stories!

@Abhishek Gupta any particular solution that's best suited for? 🤔

@Paige Goodlett pretty extensive. 3 years. I love it. Work in it everyday. Bubble.io are working on full native mobile as well. That's gonna be fun.

@Alejo and Paige Pijuan oh for sure, the issue I have as it stands its not setup for developers building products. Just Indie hackers and companies integrating for their own needs, unless you go beyond the enterprise t1 which I've found no details on as yet.

A better way Vapi could work with concurrency and accounts/sub accounts and help them to scale their business. Having a shared concurrency limit across sub-accounts can restrict growth, particularly for larger businesses with multiple sub-accounts, each of which may have varying needs. It can make scaling difficult because users may feel like they’re competing for resources within their organization. Here’s how I would approach this situation, along with some alternative options: 1. Account-Level Concurrency Limits Based on Plan - Assign Concurrency per Sub-account: When a client subscribes, give them the option to assign concurrency limits per sub-account based on their plan. For example, if a business has the T1 plan with 20 concurrent calls, they could distribute those among sub-accounts. A small sub-account might get 5 concurrent calls, while a larger sub-account could get 10 or 15. - Why?: This gives the client more control and flexibility over their resources, ensuring they can optimize usage without internal bottlenecks. It encourages larger businesses to subscribe and segment their usage across departments. 2. Separate Concurrency for Sub-Accounts - Provide Concurrency per Sub-Account Plan: Each sub-account could have its own separate concurrency limit depending on the plan chosen by that sub-account. For instance, a small sub-account could opt for a plan with 5 concurrent calls, while another sub-account might need 10 concurrent calls and could subscribe to a higher-tier plan. - Why?: This incentivizes businesses to subscribe to higher-tier plans for individual sub-accounts, creating more predictable revenue per sub-account. It avoids the problem of shared concurrency and allows sub-accounts to scale independently. 3. Introduce Scalable "Per-Sub-Account" Pricing - Account with Base Plan + Pay Per Sub-Account: Create a structure where the master account subscribes to a base plan with its own concurrency and minutes, and then each sub-account pays for additional concurrency as needed. Each sub-account could be billed separately but under the same umbrella of the master account. - Why?: This makes the service more scalable and adaptable for large organizations, while allowing individual teams or departments to manage their own usage and budget independently. It also increases the opportunity for upselling.