Hey guys would love some support on this issue I have AI assistant that is not working inside of the voice lab neither when I call the phone number this is for million dollar Plumbing Company would love some help ASAP thank you 😅

Hey everyone! 👋 Wanted to pop in and make my first post here. I'm Halie — I've been working with the Assistable team as a beta cloud employee. I'll be hanging around the Skool group and DMs pretty regularly, so if you ever need anything just tag me or shoot me a message. Quick background on me: I have access across all departments, vendor Slack channels, and the Assistable platform itself (browser + API), so I can jump in and help triage things when needed. Since I'm here, figured I'd share a few updates: Webhook fix — Yesterday some of you may have noticed webhooks not firing. We tracked it down to a recently configured webhook that got stuck in a retry loop and was hogging server bandwidth. Found it, patched it, should be good now. New system prompt — This is a big one. We updated the core system prompt for the first time in a really long time, and the beta tester feedback has been super positive. It's one of the most comprehensive agent wrappers we've built — proper date/time context, user context, cached memory across channels, and stylistic tuning that keeps your agents sounding natural instead of robotic. Along with that, here's the updated variable set which covers a wide range of date and time variables for all use cases: https://docs.google.com/document/d/1pH_gk89wUf0dSjx0wLlJKgFVYt9yPNgwLrgtFbu4TXs/edit?usp=sharing STT update — We're rolling back from Deepgram Nova 3 to Nova 2 for now to cover a wider range of languages. But good news — with the V3 front end launch, you'll be able to pick your STT provider yourself (Nova 2, Nova 3, Flux from Deepgram). And for the multi-lingual folks, we're adding Krisp AI as an audio passthrough for noise reduction and cleaner transcription. V3 front end — Took a peek at the latest GitHub repo and we're getting really close to pushing this out. It's a big step up in stability — agent orchestration, load times, run times, the whole experience gets a lot smoother.

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, I'm still having the AI say the wrong days with the dates. It says the day prior to the date, as if it's still going off 2025 days and dates. I've had some unhappy customers since it seems like it's been happening since the new year. Any way we can get this back to being correct? Thanjs @Jorden Williams @Assistable Ai @Assistable Team