What's upcoming for assistable? @Jorden Williams @Mike Copeland

The core reason was finally sent and the user has been identified. Evidence will be submitted shortly. Going forward, we are going to have workspaces in their own sub-accounts in the telephony provider so that these issues are isolated and wont happen going forward. There was a honeypot number called which caused a compliance strike that we were NOT notified for UNTIL LITERALLY RIGHT NOW... I'm hoping to have this done before EOD - I wouldnt put my chips on black there in case there needs to be further review into this user. until then, WE WILL SWITCH YOU TO OUR NEW NUMBERS COMPLETELY DFY OR HELP YOU TRUCK A PROVIDER OF YOUR CHOICE ON A 1-ON-1 CALL. I'm not resting until this is fixed. Standby

We had someone violate a rule in Twilio so we have a temp outage with numbers older than 6 months (Twilio based numbers) - we have submitted proper evidence and been acknowledged so we are just awaiting the switch on. In the meantime, we will help you trunk or get a native telnyx number to keep you going on a 1-on-1 call; just drop a comment and the team will get you on a call immediately Hoping this resolves today and we are porting those numbers over to telnyx afterwards to prepare for voice version 3 and native CRM launch in november

Quick question, my client has Verizon and we set up forwarding to the AI, but it takes 30 seconds maybe a little less before it forwards and by then most people have already hung up. (She wants the opportunity to pick up but it rings too many times) I don’t want to change their business phone number because it’s on their Google business profile website and everything else. Has anybody else ran into this issue and what was your solution?

I’ve read and tried every suggestion in the community, but today the agents are just refusing to hang up. Does anyone have a truly ironclad method to make the agents end the call? It's been too long to have this issue!