Assistable is breaking left and right on my side. Anyone else experiencing outages on site widgets please? Thanks.

@Halie Bot, @Mike Copeland Just tried to create a new Ai Assistant, and one was created quickly, but it is empty. Is this normal? what's the new procedure to create a new AI Assistant?

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.

My client is waiting for me to deliver their bot, that they paid a month ago. They want to call up fresh leads with voice AI. They have a medical knowledge base of 300 rows of data. Since KB for voice doesn't work, I deliberately tested Buildship GSheets & GDocs and even make.com connections. On all my tests the chat bot read all of the data and voice bot only read first 20-30 rows, and said it didn't have access to rest. What else can I do to get this fixed?

Tons of new features, hyper-customization of the voices, and HIPAA compliant calling. Latency is now instant - we will enable inbound, outbound, iframe-initiated + web calling (to have the AI talk in the browser). Switching to 11labs for voices to for broader options and lower latency. Buy twilio numbers through us to link to your assistants for inbound calls to your business. Actions - voice assistants will share the same functionality as the chat assistants. BONUS: I will be putting buttons throughout the platform to walk you/your clients through deployments by talking to them in the browser about how to do everything.