SMS Delivery & Opt-Out Diagnostic
Trace MobileConnect send state, delivery semantics, held numbers and subscription events without treating one status field as the whole truth.
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
A channel diagnosis that separates send attempt, aggregator delivery, handset uncertainty, held state and consent history.
Know the mobile number normalization used by the program.
Know whether the code is private or shared.
Inspect message tracking
Start with recent message/status records and Journey identifiers.
Interpret shared-code delivery correctly
Aggregator acceptance is not automatically proof of final handset delivery.
Inspect subscription history
Use subscription events for opt-in/opt-out context.
Check held / undeliverable state
A held number can explain repeated delivery failure even when upstream logic looks healthy.
Account for STOP without identity
A new number can generate STOP-related state before a SubscriberID exists.
Turn the Recipe into checkable work.
Progress, notes and history stay in this browser.