Have any questions? Text me (iMessages & SMS): 770-296-7271 Need white-gloved help RN? (I am in there too): help.assistable.ai Have anymore questions? Text me and I will make a video over: 770-296-7271 ----- where have i been? - Actively trying to fire myself. I think a long term worry internally, myself, and from the community is key man risk. My only objective is trying to make sure this outlives me. Im mad. - Me too. Lets figure it out together, reach me or team and lets make sure clients are super duper happy Why is X happening? - I explained in the vid along with solution - if you are super busy, text me and ill get you an answer in less than 5 mins What can I expect? - A platform that does rely on me or any vendors - something that we own in entirety and can be maintained by people much smarter than me X ? - Y A (aka text me or run it up to support and they will send to me) we are on call 24/7, ask anyone thats talked to me in the past week - I have slept collectively 6 hrs (not even in my bed :/ ), yelled at some people upstream, and gave every ounce of my time to help anyone down stream I miss making videos and being involved here. I want to do it more. Thats what we are trying to do here

Any meaningful upgrade comes with a moment of discomfort. V3 is one of those moments. To support what’s coming next, we had to migrate some core components earlier than planned. While this was the right decision for the long term, we know the timing has caused real frustration. If you’ve experienced call issues, delays, or unexpected behavior, we want to be clear from the start: We see it. We understand the impact. And we’re actively fixing it. Right now, there are three main things we want to acknowledge. First, there is a delay in the AI agent greeting on outbound calls, and this is affecting all outbound traffic. We know how important that first moment of a call is, and we agree that this experience is not where it should be. A fix for this is part of the upcoming patch and is being treated as a top priority. Second, some users are experiencing latency or connection issues. The majority of the platform is operating normally, but we already have a patch in progress that directly addresses these issues and will be rolling out shortly. Third, there is a busy signal issue affecting a small subset of numbers. We currently host over 14,000 phone numbers. Out of those, a few hundred are affected. If you’re one of them, your frustration is valid, even if the issue is isolated. Most of the impacted numbers fall into one of these categories: - Custom Telnyx setups that don’t align with our updated requirements - SIP trunking requests that were never completed - Older numbers still in the final stages of porting from Twilio to Telnyx If you’re affected, there are two paths forward. Option one: wait it out. For many numbers, this will be resolved automatically over the next few days as the patch and cleanup complete. Option two: move faster. You can purchase a new number and let our support team know. If your old number qualifies, we’ll credit your wallet for the entire year for the phone number ($30) for the trade-in. This option is there for anyone who can’t afford downtime.

Hey @everyone I was working with @Jorden Williams this week and thanks to his work on the back end we were able to test some things out, and it appears that through testing a fix was achieved. Jorden is going to be pushing it out today, but you can get the outbound voices working properly by switching the assistant voice to one of the Rime voices or Marissa, which has been completely rebuilt. I have only tested this with the Twilio SIP Trunking configuration at this time, but Jorden assured me that it should also work with natively purchased numbers. Please test and confirm that this resolves the issue for you with your assistants as the update gets pushed out. Finally, I was told that the 5 second dead air issue at the beginning of the call is going to be patched out on Friday.

Been on with support for 5 days trying to figure out whats going on, running into all kids of issues with my numbers. I just wanted to see if it was just me or not. Anyone else having issues where outbound calls are not following the script or just sound different in general than they do for inbound?

When I make INBOUND CALLS or use the ORB sound perfect... but when a Lead came in and the "Make a Call" produces a Outbound call sound robotic... Anyone experience or have this problem? @Assistable Team @Mike Copeland