Hoping someone has run into this. Our agency has the Assistable agency-level connection set up on our own GHL. In the past, I've been able to install Assistable on a subaccount inside an outside agency as a direct connection without issue. The last several attempts, the install flow defaults to the agency-level selection. Subaccount/location isn't presented as an option — agency is the only choice available to proceed. When I follow through, it wipes out my existing agency connection on my own GHL. Then I'm stuck in a loop trying to restore my agency connection, and I still can't get a direct connection on the outside subaccount. This isn't isolated to one outside agency — it's happening on every outside subaccount I try. Support docs don't reflect the current install flow, so I'm not sure if something changed on the Assistable side, the GHL side, or if there's a step I'm missing. Anyone else seeing this? What's the current correct path to direct-connect a single subaccount that lives under an outside agency without nuking my own agency connection?

So… turns out we’re late to our own announcement. Classic. It’s actually already built. I was telling the devs this morning it’d be cool if we could roll out an MCP for everyone soon… only to find out one of them had already taken initiative and built it. Next up, we’re adding subaccount-level API keys, and once that’s in place, we’ll release the MCP for everyone to use. And yes, before anyone asks, updated API docs are coming too.

Hey @everyone I was working with @Jorden Williams this week and thanks to his work on the back end we were able to test some things out, and it appears that through testing a fix was achieved. Jorden is going to be pushing it out today, but you can get the outbound voices working properly by switching the assistant voice to one of the Rime voices or Marissa, which has been completely rebuilt. I have only tested this with the Twilio SIP Trunking configuration at this time, but Jorden assured me that it should also work with natively purchased numbers. Please test and confirm that this resolves the issue for you with your assistants as the update gets pushed out. Finally, I was told that the 5 second dead air issue at the beginning of the call is going to be patched out on Friday.

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.

I am looking to run a Google ads call campaign to an assitable voice agent. However Google requires the destination number to be verified. Is it possible to make the number purchased verified to Googles standards? Is there possibly a work around?