Assistant started over in the middle of the conversation, it didn't catch the address correctly and it still continued after call transfer 😭😭 @Jorden Williams @Bernie White @Assistable Team

Call transcripts are not working

Please update here when the transfer call is fixed

Quick context: Last week I ran a free workshop inside the LeadIndicator group. During that session, I walked through the exact Assistable workflows and automations we use internally — the real ones that run our business, support, fulfillment, and scaling. There was a lot of interest in getting those workflows, and since the workshop was positioned as pure value with nothing to sell, I decided to give the entire snapshot away for free to that group. Rather than keep that value isolated, I want to make it available here as well. ✅ What I’m giving you - The full Assistable snapshot - The exact workflows we use internally - No stripped-down templates - No pitch, upsell, or funnel This is not something we normally give out publicly. The only thing I’m asking in return If you’ve found value in Assistable, I’m asking for one small favor: 👉 Go to Google, search for Assistable's TrustPilot page. Leave an honest review on our Truspilot page. That’s it. Reviews matter a lot — especially as we continue to grow and as we deal with the occasional bad-faith review that comes with scale. Your feedback genuinely helps. 📬 How to get the snapshot - leave a review on our TrustPilot page - Comment that you've left the review and I'll DM you.

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.