Inbound on new numbers arent able to get back from creating it time because its taking - 200 seconds.... By the way, just so we clear the air here - inbound (new / existing contacts), outbound, messages, context injection, oauth, tool calls - all use GHL endpoints, mostly GET or CREATE contact. Which right now, are taking - not seconds - but minutes. We have 2-4 second window on calling to get that information back - in which 200 seconds slightly goes over. I'm pushing a patch to bypass ghl right now.. Loom attached - Also, oauth set up is not allowing bulk install meaning oauth wont install if you reset it -

Most are aware of multiple provider outages coinciding with the Phase 2.1 update push. The timing is frustrating, but Assistable is working closely with affected providers to monitor the situation and assist wherever possible. What’s is/was Affected: • Inbound/Outbound Calls • Messaging Services • Any system interactions requiring GET requests from GHL (e.g., retrieving contact IDs/info). Advice: I strongly recommend avoiding troubleshooting or resetting systems on your end to prevent complicating the ongoing migrations. These interruptions stem from upstream provider issues and are not directly caused by the update. One of the outages from GHL is directly tied to marketplace app connections. If you're antsy and don't already have this in place... I recommend agency owners set up client communication workflows for service outages. Brand em up (or don't). --- Now... Tough love/perspective from Breyden. I understand how disruptive this is, but I feel inclined to remind you: AI itself is disruptive. You are selling disruption. Welcome to the frontier. The frontier is unpredictable at times, even with the best trailblazers and wagons (pardon my Oregon Trail reference). For example, today, a primary TTS service went down. Fallback systems across the board kicked in but were overwhelmed. GHL’s load balancers—yes, they also rely on voice AI—adjusted to handle their retry load. But compute resources are finite, and drastic adjustments can ripple across services, causing further degradation. Volatility is a guarantee when AI systems play with other AI systems. It's a cost we all pay for the benefits. It will decrease over time, but is going to be present. At the end of the day, "dynamic" and "controlled" are still oxymoronic - they're inherently inversely connected (at least until scalable AGI is available). P.S.) hopefully the perfect storm of all these at once never coincides with an update rollout again. Fantastic timing, right?

High Level is really pushing their AI Employe. I would like to make an informed decision and not sure sure which way to go. Assistable.Ai or HL Ai Employee? Some insight would be appreciated.

Need 1 or 2 testers to verify value extraction And 1 or 2 to test stripe oauth and access Let me know if you have some time to test

The last day and a half every time I call my inbound number she is reading the instructions how can I stop this from happening?. It was not doing this before I have not changed anything. Now when I say do I have any appointments it reads user wants to know if we have appointments? Has anybody else noticed this happening out of nowhere.