Hey all, I have tried numerous ways to disable the ai for specific clients we tested with, but its still firing no matter what. I've archived the bot, turned off responses, and fully archived the accounts. Yet its still firing in GHL. Anyone know the specific process to turn it off without completely de-sync'ing every location?

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.

Can someone explain what the voice engine is to me like im 5? I think i get the jist but i've never seen anyone talk about it so I'm wondering what benefit it would offer to adjust or what would happen if we changed the voice engine? Thank you!!

Looking for the latest version of the docs as i have https://aisupportdocs.com/ and https://docs.assistable.ai/chat-ai#context-action @Assistable Ai @Assistable Team @Mike Copeland But they seem half baked just wondering what the most complete up to date version is. I have all the GHL docs stored in a knowledge graph/vector storage and want to merge my assistable set up with it. Happy to share the knowledge base set up once finished. Attached is my github repo represented in notebooklm infographics.

[Question] Context: Solar client using Assistable for lead qualification and appointments. Requirement: Agent needs comprehensive understanding of all 5 services and related products to be able to respond to client enquiries and provide product and service details to move the deal forward. Challenge/Ask: So far the client has sent me around 10 documents just to cover their services. The still need to send me way more. I estimate there will be 30+ pages of knowledge I need to make available to the AI agent. I considered creating 5 specialist agents, but I feel the complexity will be too much and would prefer 1 agent with a basic task based prompt making use of custom fields to determine the lead enquiry type (Boiler, Solar etc). Question: Does Assistable have a limit on the size of the Knowledge Base? Can I create a comprehensive KB using the Q&A vector method to manage 30+ pages of information? What would be best practice? Any guidance and assistance would be greatly appreciated. Colin