Loading

Custom STOP Keyword Does not Unsubscribe Subscribers from Business Units

Publiceringsdatum: Jan 23, 2025
Beskrivning
In MobileConnect, it is possible to create a custom STOP keyword. Unlike Global STOP keywords, the unsubscribe will only occur where the custom STOP keyword was created. 

Example: My Tenant 999888777 has short code 1234567890 provisioned across all business units. In my top level tenant 999888777, I create a STOP keyword "STOPSMS". In my business unit 888777666, I start sending to subscribers and inform them to unsubscribe by texting in STOPSMS to 1234567890. Because this keyword exists in 999888777, the unsubscribe will only happen in this account. The subscriber will still be opted-in to 1234567890 in 888777666.
Lösning

If you are on a shared code, meaning you do not own the short/long code, you can only have these Global STOP Keywords. Each business unit will need its own unique STOP keyword.

Note: shared codes are Salesforce owned codes that are provisioned to customers. Not all markets support shared sending. Salesforce stopped provisioning shared US/CA codes back in 2018 and fully removed support for them in 2020. 


If you have a short/long code that your company owns, it is possible to make Custom STOP keywords into Global STOP keywords. Please create a Support Case within the Help & Training Portal. Please specify which keyword(s) need to be made into a Global STOP keyword and on which code. 

Note: Once the keyword is updated to a Global Stop Keyword, any edits to the keyword itself from within the application will break the Global Stop functionality. Refrain from making any modifications to these keywords.

Knowledge-artikelnummer

000390233

 
Laddar
Salesforce Help | Article