Apologies for the delay - we've been migrating some assets to AWS which is a perfect segway to answer The simple answer is we are building for depth not breadth - we are building for ownership and sustainability rather than shiny object. Perfect example is now. Right now is a time where it may seem where we are a bit absent or no "new feature" weekly like usual but we are doing a lot of boring things tbh. DB migrations, server migrations, rebuilding 3+ yr of infra and data to own it. After this is done, we have almost 0 vendors in our entire stack which means we own EVERYTHING end-to-end 1. depth not breadth - we will double down on, and get deeper into, things that are already there rather than adding new stuff as much. Take transfers as an example. How do we create a better experience which more customization like wait music on transfer? confirmation and rejection from the business owner so the agent can either transfer or handle on it at the convience of your client. Flow builder is another - how do we scaffold agents so that our users can run AI cheaply and inteiilgently? how do we increase latency without decreasing intelligence? things like this is our focus now 2. Same thing as one - but aside from depth our focus is on expanding native abilities. along the way we've basically been a plugin for GHL but how do we keep more functionality in-house for a better / deeper exerpeince in building set-it-and-forget-it solutions. In house workflows, not to contpete with GHL, but to save you money and time on middleware for tools just do that stuff here without maintiaing this and n8n or something. so we will double down on the depth on building agents and deploying them 3. yeah, we reverted due to some minor schema stuff - we have fixed it since and now focusing on cleaning up everything for a full prod release soon. focus here is seamless experience The vision has never changed - but the way we are working towards it has. A lot of these things you will see from GHL seem to be shiny object - nothing wrong with that BTW, I myself love shiny things, but we'd rather be the master at two things: building complex agent archectiure as easy as possible to people like you (so you can build things for clients that you never thought you could before) and how do we make deploying / maintincing that easy (set-it-forget-it, fallbacks, integrations, visibility etc etc.)

I can make a loom in a bit

Let me check

@Michael Kittinger yiu out today brotha?

Send me assistant id, contact id, location id and I’ll send you what’s being pulled

@Jamie Latinsky check oauth - all of those sound like oauth connection Hullcinations = doesn’t know contact info from GHL Booking = can’t book to calendar bc GHL won’t let it Etc

Can you send a Quick Loom here and I can see if ther are any discrepancies?