A verification step that reads the Messaging Service as the builder's own account and checks the inbound request URL exists, is public https, is not local, and points at the platform's SMS receiver. Anything it cannot confirm blocks the promotion.
Also called: can customers text back · inbound webhook check · one-way texting
- 1The status cron calls the check before promoting a registration.
- 2The Messaging Service is read using the builder's credentials, since the parent cannot see it.
- 3The inbound URL is validated for presence, scheme, host and path.
- 4A failure to read the service also blocks promotion — failing closed.
Documented on the function: 'Carrier verification tells us the tenant may SEND; it says nothing about whether anyone can hear the answer. Promoting without a reply path silently severs every inbound conversation, so this is checked at the source of truth — Twilio's own record of the service — rather than trusting that our purchase flow set it.' The failure posture is explicit: 'Failing closed here costs a delay; failing open costs a customer's message.'
- An account could be promoted to a provider that could send but not receive.
- Trusting our own purchase flow instead of the carrier's record hid misconfiguration.
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 →