GHL Direct Connect (not connecting) 😞

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?

6 comments