A pair of capability checks with different rules. Texting can be live through either provider: through the platform's own carrier it needs a number AND an approved carrier campaign; through a connected CRM the number and registration live there, and an active binding IS live texting. Calling is different: a number that can be dialled inside another product still cannot be dialled from here.
Also called: can I text yet · is texting live · why can't I call · status light
- 1Each light returns ok plus a plain-language reason when it is off
- 2Texting via the platform's carrier requires a number and an approved campaign, because without registration US carriers silently filter
- 3Texting via a connected CRM counts as live because that CRM does its own carrier compliance
- 4Calling requires a voice binding and a dialler in THIS product
A status label said texting was live when all it really meant was that a configuration row existed — one account displayed "no number", "registration not started" and "texting live" on the same line, and the builder reading it had no texting at all. Ambiguity here is expensive, because the failure it hides is messages being accepted and never delivered. Two honest lights per account now answer the only two questions that matter: would a text sent right now actually arrive, and can a call be placed from this product — each with the reason when the answer is no.
- Status labels reporting configuration rather than capability
- Accounts with thousands of real messages reported as unconfigured
- One flag used to answer two different questions
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 →