Is there a way to export all data for a specific assistant into a single or multiple Markdown files? This could include selective or complete export of global prompts, toolkit settings, knowledge base, phone numbers, voice settings, tags, and other configuration data. This feature would be helpful for debugging and optimization purposes. If not available, just sharing this as a potential enhancement idea. thoughts?????

thumbs up or thumbs down your assistants reply to use for further training Sub-account locking password moved to the dashboard Message limit and sub-account limit with associated metrics now in the dashboard

just an idea!

Apologies if this has been covered, but I couldn't find a recent thread on it. I'm looking for success stories or recommendations for setting up a dynamic knowledge base—one that continuously updates or that the AI can query in real-time (unlike the standard static URL scrape). are there any Supabase / RAG database setups that work well for this? I'm aiming for a low-cost solution (ideally comparable to the standard ~$15/mo range). Any tips would be huge. 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.