A single derivation: an account is on the other CRM when its live SMS binding is that CRM and it has no active in-house SMS or voice binding of its own. Those accounts get no phone dock, no launcher, no voice token and no call-driven automations. Everyone else does.
Also called: phone doesn't show up · no dialer for my account · GHL texting
- 1A pure function over the account's provider bindings, shared by the browser and the server
- 2The client hides the launcher, the dock and the incoming banner entirely
- 3The softphone mints no token and creates no device
- 4The server-side lookup fails OPEN on a query error, because a transient read failure should not take a working builder's phone away
- 5Callers gating a WRITE use the explicit-false check instead
A builder whose texting runs through a connected CRM has no carrier sub-account, no line and no calling identity, so the in-app phone cannot work for them — but the dock, the launcher and the pipeline automations each decided that for themselves. Two definitions of "does this account have a phone" means two answers, and the one that drifts is the one that silently advances a lead's stage for a builder who never placed the call. One rule now decides, and every surface obeys it.
- Dead phone UI for accounts with no telephony
- Two definitions of the same capability drifting apart
- Automations firing for accounts they do not apply to
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →