I need to cancel Wed Workshop call today. I’m traveling and my internet is too spotty. We’ll resume normal schedule next week. Thanks!

So, its been a long process and a lot of work - literally re-writing our voice orchestration to be native - and we still have a small sprint before we will start flowing traffic that way. Here is just a general guide of somethings that will change, be added and be deprecated. So, rollout. first - the users using our numbers will start seeing the traffic flow first. Then older numbers. Then trunked numbers. Nothing tangible changes from your perspective besides lower latency. Tooling - So, we are adding POST / GET / PUT / PATCH / DELETE to api request types. We also have it where you can configure headers, query parameters, path parameters and body parameters. So, fully customized API calls. We will suppose variables in these as well so you can pass API keys or your access token for GHL. Here's the thing, tools is now running through a proxy of ours that will open up the doors for a couple things: - Tools to run as they do today - Direct API calls (will be a toggle), so instead of being wrapped in a args object with metadata, etc - we will just send the API call. This gets rid of the need for middleware because you can make direct API calls. - Workflow execution; not today or the next week but we are adding native workflows to the platform. You can configure a custom tool to trigger a workflow locally to run multi-agent frameworks and basic automation so we will support a middleware internally. Abilities - all stays the same, but we are adding agent teams in voice (chat following right after). So, add different assistants into call to create a team env on the call either through a "prompt change" so we just change the prompt dynamically, or through a team so mutliple voices, etc. AI Models - We will be running a custom fine-tuned model thats been fine-tuned for voice orchestration. aka, this llm outputs text-to-speech friendly output to keep weird translations to a minimum. You will be able to select an OpenAI model if you would like and run it with your key if you prefer OpenAI output.

Telnyx Integration... 5 1/2 years on the GHL ideas board and still nothin... NOT ANYMORE! I'm not a coder and relied 100% on AI. Took a few hours and built seamless integration myself with a simple dashboard. Submitting for approval today. Free for everyone. No upfront fee. No hidden fee. No usage fee. 100% free. It's literally just a clean, seamless bridge that allows you to send and receive SMS via Telnyx with or without a GHL phone number. And Telnyx is 1/2 the price for SMS and 1/4 the price for MMS than Twilio. Happy early Thanksgiving!

I understood MCPs from a "here's what they are and what they can do" standpoint, but until I actually started using them, I had no idea how powerful they are. I haven't used MCs yet with Assitable AI, but I use them extensively with my AI elsewhere. Cannot wait until Assistable can connect into them. They really are a complete game changer.

What do you do if your prompt needs to be longer due to pathing through complex scenarios? I have a tax client with like 6 calendars and services that the agent is having to sort and path through and book on the appropriate calendar. I've used a calendar matrix and I think I've reduced every last character I reasonably can. I'm still at 13,351 characters. My concern is that I have an upcoming client with like 20 services with a good 5-6 products each per service and will have a similar scenario. The biggest challenge with length is that I'm having straightforward tools fail on me on both SMS and voice (e.g. add a tag, calendar booking), and help.assistable is telling me it's a matter of prompt length and to reduce it to 8K characters. Any advice, direction, tips, or help would be truly, truly appreciated! ...TRULY APPRECIATED. Thanks in advance!