![]() In other words, unless we do it manually on every contact on Contact Builder > AllContacts > YourContact > Membership, I could not unsubscribe contacts from WithConsent keyword. The problem with the Use case #1 is, there is no way of unsubscribing contacts from a keyword in bulk. Use case 2: If the contact has not been attached to this keyword on AllContacts, he will receive the SMS and will be Opted-in to the keyword.In case he is Opted out from this keyword, he will not receive the SMS and will not be re-opted in. The contact will only receive the SMS if he has opted in. Use case 1: If the contact has been attached to this keyword in AllContacts, then Journey Builder will respect the consent.There is actually two use cases when choosing the second option: But after conducting several tests, I found out that this is not the real behavior. At least, this is the description given in the UI by SFMC. The second option (cf image below) allows you to associate your SMS activity to a keyword and subscribe the contact to this keyword if he is not. The problem was with the promotional sends. In addition, since Journey Builder gives the possibility to send SMS to contacts that are subscribed to at least one keyword, it was perfect for transactional sends. Moreover, contacts who gave their consent and have a valid MobileNumber will be uploaded to AllContacts and associated to WithConsent keyword. ![]() Query 2: populate contacts that gave their consent to receive SMS messages and have a valid MobileNumber.Įvery contact that have a valid MobileNumber will be uploaded to AllContacts through ContactBuilder and associated to NoConsent keyword.Query 1: populate contacts that have a valid MobileNumber. ![]() I created two keywords, WithConsent & NoConsent to separate transactional and promotional SMS sends. However, it did not last very long before I learned that there are many limitations. I was happy to find out that I can use keywords. After digging in the documentation, I did not find a "standard" way to achieve this. I had to figure out a way to do the same within MobileConnect. In fact, not checking the "Honor source and publication list level opt outs" checkbox will ignore the contact's status on AllSubscribers, opening the doors for your transactional emails. This functionality is available when sending Emails leveraging Send Classifications in Email Studio. Long story short, there is no such thing as Transactional SMS sends in Marketing Cloud. In this short article, I will describe how I have addressed this use case. The ability to send transactional SMS to customers is an indispensable feature, especially for companies selling to individuals.
0 Comments
Leave a Reply. |