Mine is loading but nothing happens ? Anyone experiencing the same ?

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?

Outbound campaign. I have it set in Assistable - Contact Initiates: AI will remain silent until the contact speaks first. (See Image). But the AI is not speaking until the contact speaks TWICE. Anyone have a solution? We have added some wording to the prompt but still not working. Thanks.

The call is answered, I hear background noise, but assistant is not speaking

Has anyone built an AI voice assistant to fully replace a traditional inbound phone tree for a multi-location clinic? I’m working on a project where the current setup is the standard: “Press 1 for billing”“Press 2 for directions”“Press 3 for Houston clinic” etc. The goal is to replace that with an AI voice assistant that can: -Answer calls conversationally instead of keypad prompts -Identify caller intent (billing, rescheduling, directions, front desk, etc.) -Figure out which clinic/location they’re referring to -Handle simple FAQ questions like address, hours, and directions -Cold transfer the caller to the correct department or clinic There are around 20 different transfer destinations involved. Main question: Has anyone successfully done dynamic call routing like this inside Assistable since Flow Builder is gone? Or did you end up handling routing through Twilio / another phone system instead? Also curious if multiple cold transfers across that many destinations worked reliably for you. Would love to hear how you structured it and what limitations you ran into.