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 post is just to help the community. For those who'd like to use AI to answer missed calls instead of them going to voicemail. I spent a ton of time trying to figure this out, GHL support says it doesn't work, but I just found a work around. Instead of wasting tons of time trying to figure it out, check out this video. It works for me. https://www.loom.com/share/78b455f713ff4990be290f0b86f19675?sid=9354edb3-6438-4039-849c-db37d8ea4f06

quick question.. i am new to the platform.. Using outbound calling... is the agent able to read GHL calendars and book appointments or is that only through chat?

Here's a quick one on how to set up your AI voice to check for tags in GHL in V2. This is not something everyone will need, but can be handy to have in your toolbelt. Use cases given in beginning of vid. Name: check_tag_customer Description: Use this tool to check the status of the tag customer Endpoint: https://assistable.ai/api/1.1/wf/assisable-check-tag Parameters: locationId {{sublocationId}} contactId {{contactId}} tag the field value is customer @Platon Belmont @Harry Stokes

Is the chat widget still in beta?