GetToken API not called by SMS STOP MO Messages
Trailblazer Community

GetToken API not called by SMS STOP MO Messages

Marketing Cloud Mobile

Last updated 2020-05-28 ·Reference W-7142651 ·Reported By 3 users

In Review

Summary
When a Marketing Cloud account has Tokenized Sending enabled at a Business Unit level, but a Mobile Code is configured in the Enterprise, the GetToken API is not called to get the Token for the MobileNumber to process the STOP (or custom stop) MO Message

Repro
Pre-requisties

- Tokenized Sending has been configured at the Business Unit level of an Enterprise
- Mobile Code has been provisioned to the Enterprise

Repro

- Subscriber sends a STOP MO Message to the Code targeting a Keyword at the Business Unit
- Message is processed by SFMC and a new Subscriber is created
- GetToken API is not called to get the Token for the MobileNumber, to then be processed correctly

Workaround
No current workaround

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.