Everything looks configured but we can't confirm it
Sometimes we genuinely can't check. That's not the same as working, and it's not the same as broken — this explains which of your settings we can verify live, which we take your word for, and what to do about the difference.
Who this is for
Anyone who's seen a status that says we couldn't confirm something.
Why we say this instead of showing green
A failed check is not a pass. If we can't reach your provider, or there's no API to ask, the honest answer is that we don't know — and showing a green light we haven't earned is how people end up trusting a setup that isn't working.
So an unverifiable status renders neutral, never green, and always says why.
What we can and can't read
For Twilio and Telnyx we read live from your own account, so A2P and number status here reflect what the carrier actually thinks.
For SignalHouse there's no per-account status we can query. What you see is based on webhooks we've received plus your own confirmation that registration completed. That's a permanent limitation of that integration, not a temporary outage — the authoritative source is their dashboard.
For anything running on platform credentials rather than your own — which is the normal case for a captive agency — the setup isn't on your account at all, so there's nothing for you to check.
What to do about it
Verify by behaviour rather than by status. Send a real text to a real handset. Make a real call. Book a real appointment. Those tests are authoritative regardless of what any status panel says, which is why the go-live article is built entirely out of them.
Related
Where this lives in the app
This is documentation for Virtual Closer. Book a walkthrough or sign in.