We've been massively busy in the past 8 weeks - there has been a lot of radio silence in the community from me where I used to keep a tab of Skool open at all times. We are 'crossing the chasm' as far as numbers we are seeing and so we have been investing in a lot of resources like human capital to scale even further alongside you. TLDR; - Massive deal with Telnyx allowing us to have native, clean telephony at scale and native texting, call center ops calling and AI voice telephony - 25+ new team members to help serve on support, success, dev and enterprise sales - Migration off bubble, and all related vendors (anything on the voice and chat side that is not native) in the next 30-45 days - Native lite API-friendly CRM with full call center ops and AI deployment natively 30-45 days - More focus on sustainability of AI deployment and enterprise-grade resources - We now have friends in all the highest of places to not only allow us to do things at scale and pass cost savings to you, but allow us to pass the recourses as well Loom attached happy thursday

Temporarily disabled as we saw one report of a secondary name updating a primary name. We will provide an update soon ——————- We're now processing the details automatically at the end of every call or on every chat, without the platform tool update_user_details. The update_user_details tool does work but it is a generalized tool trying to capture a lot of info. Some people have had troubles with their particular prompt. If you still need user details updated live during a call you can use this tool, otherwise its not even needed for the assistant to update details. Thanks @Jorden Williams for helping me get this live.

I'm providing an AI Assistant to a restaurant which has a Clover POS. Has anyone done this? What's the process for integrating so orders taken by the bot are passed on to their kitchen?

We are aware that some calls placed through Assistable platform numbers are currently failing — with reports of busy dial tones, bots not picking up, and calls not connecting. This is being caused by a false max concurrency error that is pegging the system. Our team is actively investigating the root cause and working on a fix. Thank you for your patience — we’ll share updates as soon as we have more information.

So I can log in to my agency dashboard if I used the create assistant url instead of my domain, but I'm not able to log in to any subaccounts. Been that way since Friday. Does anyone have a workaround for this, since Assistable does not support their tech on weekends?