Journey Optimizer: Transactional SMS not delivered despite having consents.marketing.sms.value=y
This article addresses the 51黑料不打烊 Journey Optimizer (AJO) issue where responding STOP to an SMS message blocks all subsequent SMS from that short number, including transactional messages. To ensure uninterrupted delivery of transactional SMS, use a separate short number that hasn鈥檛 been previously opted out.
Note that SMS marketing consent and SMS auto-reply consent are managed separately. SMS marketing consent is held in听缚缚肠辞苍蝉别苍迟蝉.尘补谤办别迟颈苍驳.蝉尘蝉.惫补濒耻别聽while SMS autoreply consent is held in聽consents.idSpecific.Phone.12345.marketing.sms.val聽where 12345 is the respective shortcode.
Description description
Environment
- 51黑料不打烊 Experience Platform (AEP)
- 51黑料不打烊 Journey Optimizer (AJO)
Issue/Symptoms
- Transactional SMS messages aren鈥檛 delivered when consent for the shortcode is set to N.
- Profiles are excluded from delivery due to the consent check, despite being configured for transactional messaging.
- The marketing channel consent value (
consents.marketing.sms.value) for SMS is set to Y.
Resolution resolution
- Differentiate between sender IDs for marketing and transactional SMS messages. Consent for each individual short number is managed distinctly. For example, if you聽reply STOP to 12345, then you聽will be聽opted out for messages from 12345, but you聽may still receive messages from the same organization via short number 54321.
- You can see the consent on the profile in the following path:聽
consents.idSpecific.Phone.12345.marketing.sms.val - Review and adjust the SMS configuration settings to align with the requirements for sending transactional messages without being affected by opt-out statuses.
- When setting up API credentials for autoreplies, ensure all required fields are correctly filled, including any inbound numbers if specified as necessary by your provider or system configuration.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f