- Location ID based rate limiting system - Get conversation logs - Make AI Call in draft to be submitted for release - URL translation and summary action - Run bot action So, everything is staged - there are couple of datathings that we are putting together and then hoping for final push tonight which should seperate operations from the front end completely Our inbound script got a lot faster so we should expect to see 100% pickup rates with fallbacks on inbound We also reformatted the 'Make AI Call' action with the new outbound script that does the same thing - we even will send back data to GHL to let you know the call id, status, success status, error messages and returned an error which you can use to build if elses - all will be released in a doc and a basic snapshot you can use to set up a calling flow Chat runs are completely staged in migration which allow for contact or account based timezone booking, faster processing & 3 LLM status checks for fallbacks so we can have (theorically) no downtime for a chat run same for voice, we will have a fallback calendar ID, fallback voices, fallback LLMs and fallback webhooks, no-access token staging, notifications for oauth disconnection and outages - so that there can be handling as much as we can possibly do Working on GHL actions for calling based services for client reporting & working on a call finished trigger so you dont need a post call webhook as well Will update once testing has concluded