I'm not sure what anyone else is seeing, but I've noticed that outbound calls are becoming more inconsistent. Does anyone know why or how to fix it? Inconsistent outbound call behavior: sometimes calls succeed, other times they fail with no workflow errors. Assistant match logs show: {"status":200,"data":{"assistant_id":null,"found":false}}, Kill switch:false. GHL workflows show no errors and settings, function names, and prompt length appear correct.

I'm testing the workflow "Start | Self-Selling Demo" and my personal number somehow landed on an internal DNC list. How did this happen? I checked the national DNC and my number is not listed there. The contact was created from filling out a form. If you're familiar with this workflow, you'll know that you'll see that the error comes from the branch that detects the assistant_error (see screenshot). NOTE: I am using a subaccount that is not A2P approved. I have not got that far yet and sending the sms out is not the issue. Please do not be thrown off by the unsuccessful error in the conversation tab.

**This post is for the technical builders** For those who dont use tooling -- its the actual key for enterprise use cases and its the biggest differentiator, even internally, as you chase big projects / clients. We have set up abilities using tools, middleware and external database that you wouldn't even believe and they are very high ticket (think north of $50k), I suggest its something to take a look at if you haven't before So, as we build alongside you for fulfillment we noticed some limitations that I think needed to be addressed. So, here is the basis of those additional functionalities: post / put / patch / get / delete, execution type (proxy, direct, workflow execution), headers, timeout MS, flattened tool menu to a page not a popup Proxied tool calls is your traditional tool call for middleware as you see it today. Output is wrapped in an args object with a meta_data object. These are best suited for middleware usage (make, n8n, buildship, etc) because not only do you have your agent's output but you have location id, contact id, etc. Direct tool calls are exactly that - we dont wrap it in anything - we just send the raw request exactly as you have configured it. This is for when you want to attach to something like an MLS, or niche API directly. Cofigure headers (variable friendly), configure body parameters (and soon query parameters), and the http type. We'll send the request on your behalf just as you would anywhere and return the direct output. Workflow execution is for the internal workflow engine we are adding so we can supply you with a middleware if you dont already have one, or looking for something more native to our functinoality. more to come, happy thursday