Description
Customers can use short codes on Digital Campaigns for sending SMS messages. However, restrictions exist that require the short code’s country of origin to match the destination country (e.g. a US short code can only send to phone numbers with +1 country code). Our downstream provider currently prevents customers from sending in this scenario, but we have made a change to instead block sending upfront in our outbound-messaging service.
Change Category
Informational
Change Context
This change gives the customer better insight into why the message was not sent. In the scenario outlined above, the message from a US short code to a Great Britain cell phone (for example) would have received a wrapup value of OUTBOUND-MESSAGE-SENT, but would have been blocked from sending by our SMS provider. Customers could see that the message was not sent through delivery receipt information in reports.
With our change, we will no longer send the message in this scenario to our SMS provider, but will instead wrap up the contact as OUTBOUND-INVALID-PHONE-NUMBER. This is because the phone number is not a valid destination address for the specified short code on the campaign.
Change Impact
Customers will see a more accurate wrapup value in their contact list exports in the scenario where a customer's phone number does not match the country of the sending short code on the campaign. Customers will not experience any change in whether the message is sent.
Also worth noting, we already do this for every other supported phone number type on digital campaigns. This was simply an oversight when Digital Campaigns were originally created, as short codes were the first supported phone type.
Date of Change
Apr 26, 2023
Impacted APIs
No APIs were changed.
References
[OD-1000]
[OD-963]