high impactPRODUCTIONMobileConnect

A STOP Can Exist Without a SubscriberID

You see an opt-out/subscription event for a mobile number but no corresponding contact/subscriber ID.

Context Pack →Open Workspace →
Trust & provenancePRODUCTION
Evidence tierPRODUCTIONOfficial sources2Other sources0Last verifiedNot recorded

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.

Why it bites

Salesforce documents that a net-new mobile number can text STOP without a contact being created; the event is still logged.

What to check
  1. Search _SMSSubscriptionLog by MobileNumber, not only SubscriberKey.
  2. Do not inner-join away rows with missing subscriber identity.
Make it cheaper next time
  1. Design SMS compliance queries to tolerate null SubscriberKey/SubscriberID.
  2. Treat mobile number as a necessary diagnostic dimension.
smsstopsubscriberidconsent
Sources / verification