@Jorden Williams There is a major bug with voices leading to it not following prompts. All agents sound different, like robots and not the usual. They are speaking in custom values, hanging up calls, and not leaving VM. We opened a ticket and no response. I see other threads like this.. Can we please get an update.

If a number is on a DNC list but they fill out a form on GHL. Will it still block for DNC or will it make the call? I noticed it still doesnt call even if just opted in.

Something is seriously wrong this morning, was something changed? I have multiple assistants voices changed, and messing up scheduling incorrectly on the calendar, and ignoring tools and/or not scheduling them at all. Here is an example call. This assistant was working properly before and was set to use CIMO for voice, and gpt4o for the model. Elevenlabs setting is set to Turbo2.5 and multilingual engine. Others are reporting the same. Anyone know what's going on and how to fix it? @Jorden Williams @Assistable Team

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.

This is me (clone), calling me