@Daniel Huthwaite I don't think it is ready for release at this time. I just met with them yesterday to discuss quite a few items. For me, I needed something I could get running with right now, so I have created my own solution in the meantime. I do like the premise they are trying to accomplish, so I want to continue giving them feedback. I do wonder if the amount of effort required to get it to a place to launch is significantly greater than what most people can (and are willing to) create on their own with a no/lo code solution, and if so, is that effort sustainable in the long run.

@Wiles Pena Sent DM

@Demba Dansoko You can try adjusting the Response Delay, but be careful not to create too much delay for normal conversation.

@Stuart Edwards I agree it is pointless if all orgs share the limit. So the solution is to create new accounts for each new client, and without any api calls to do this, it makes the process cumbersome, especially if you are trying to not have the client create their own accounts. My plan is to have clients see my company as the overall Voice provider. It would have been so nice to have the orgs have their own limit. Have you heard anything about what I put in my last reply about using your own Twilio numbers to remove the limit?

@Stuart Edwards Maybe I will use orgs for larger clients that want the ability to segregate and organize their assistants/tools by departments.

Having the same issue.