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.

Would yall want to pass your own 11labs key for your own voices / acct for voice? would obviously drop price for input keys but curious would anyone use this before I built it / move on

Your numbers are only showing up as SPAM because you haven't done the proper registrations. Most numbers you buy from Twillio will more than likely be marked spam. It's the nature of the beast. But, if you go register with Hiya your spam problems will go away almost instantly (at least that's been the case for me on every number I had that was going to spam) Go register your business and every number you call or text from here: https://business.hiya.com/registration/account Hiya is the entity that controls whether your number shows up as SPAM or not on Android. 70% of the global smartphone market consists of Android users. I can almost guarantee this will fix 99% of calls that are being marked spam. (considering you're not actually spamming of course) The one catch is you have to have a business. There's no sole prop registration that I know of.

@Jorden Williams I registered the number with freecallerregistry. It’s still showing as spam. How long does it take usually? Any other ideas

@Jorden Williams i have this widget that you shared with us on my website and it works perfect. but when i wanted to add the iframe to a newsletter email within GHL email templates and i test it. the toggle button for "Ai Calls you", wont toggle over as a selection. but the user can still call dial the number for "Call Ai" functionality. any ideas to help me out here. thanks