At this time, GHL is having massive issues (think we all know this). Not confirmed but word is they know the issue and it will take up to 72 hours to implement the fix. IN THE MEANTIME, we will be pushing 2.1 early and working on an internal Assistable fix to bring everything in house. ‼️ IMPORTANT ‼️ Please do not be tagging Jorden in posts, calling him or texting. We are all in the same boat, dead in the water. We need him to be able to focus on pushing 2.1 and then this new unexpected patch he has to figure out. As new information is available, we will update the group here.

How to use the context injection as a fallback - we will build in fallbacks for senarios like today, this is the first time where we've had timeouts from GHL so this is new, we will add handling for it and parameters for you to use in case both failsafes fail Here is something you can use to restart those conversations

how is everyone getting there bots re engaged in conversation after a tag error or GHL glitching ??

Who else is facing inconsistency with performance? I love what’s being created here, but it feels too unstable to be called reliable. Often, things suddenly stop working properly. Fetching data from the knowledge base is particularly unreliable — sometimes the assistant accurately follows the KB, but other times it’s completely off. It might even say the opposite of what’s in the KB or claim it doesn’t have access to information that is clearly part of the KB.

Want to hide the Ai Employee/Season of AI from your GHL account? CSS to Hide AI Employee Promo/Season of AI /* Hide Employee Promo */ #sb_ai-employee-promo { display: none !important; }