Hey guys and girls, I wrote some code tonight that some of you may find useful. This is another way to demo your AI. You can get very creative with the code if you like, but here is the base code. https://www.loom.com/share/2638be9312ce482592c558b62a21aa63?sid=1cfee38e-6625-432b-bffc-d28e981a2c00 Here is the code to install the HTML: https://docs.google.com/document/d/15oCIEfsoVfFLU_MRBK9KdcRnhAcl8i2fZnlftYRBn5s/edit?usp=sharing

Here's my brief overview of Jorden's V2.1 notes with a couple things you'll want to be READY and AWARE of when it drops.

Will there ever be a send SMS custom tool? I think GHL has this native in their AI Employee.

One of my clients sent me a screenshot today of the Ai sending all the task in one shot . Thats the first time it happened 😂. What do i do ( i serve the french market) @Jason Dueck @Jorden Williams @Esteban Lopez

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?