Ensure that the sender ID is not a shared remapped ID
Posted: Sun Dec 22, 2024 9:40 am
When delivering SMS internationally, one of the downstream workarounds used to improve conversion is to replace the sender ID corresponding to an international long code with a short code. But while downstream operators can remap the original sender ID at their convenience, what happens when two completely unrelated entities are remapped to the same sender ID?
In reality, this situation is quite common, as illustrated by the following scenario:
An end user located in a European country requests philippines mobile number example authentication to access a Twilio customer's website based in the United States.
The website sends the authentication code to the end user using a US long code.
To avoid operator filtering, the sender ID is translated into a short code, which in this case had already been used by a casino to communicate with its customers.
Unfortunately, the recipient had disabled the casino's SMS sending (and blocked the short code corresponding to their messages).
The end user was therefore unable to see the authentication SMS sent by the website and kept retrying the SMS verification request until he was blocked.
In the examples above, using the alphanumeric sender AUTHMSG would improve conversion for all end users (in destinations where it is supported), ensuring that your messages are never filtered or displayed as coming from an unsavory or unrecognized number.
New feature, same consistent SMS delivery
With the new AUTHMSG alphanumeric sender, the Verify and Authy APIs continue to provide Twilio customers with the highest level of availability in a seamless manner, while building end-user trust, at no cost to the sender.
This feature will be automatically made available through Twilio APIs . One is for the Authy API for two-factor authentication (2FA) and the other is for the Verify API for Twilio phone verification . SMS messages that previously came as long codes will now be delivered with an alphanumeric AUTHMSG code in the following countries . Contact your Twilio sales representative (or Twilio Support ) to find out when and how this rollout will impact you and your users.
With over 5 billion mobile phone users worldwide, hackers are constantly looking for ways to abuse unsuspecting individuals through their connected devices. Smishing is a very common social engineering attack that uses SMS and that telecom operators are working to solve. Posing as a trustworthy entity, a malicious actor sends text messages asking for personal information such as passwords or credit card numbers. It only takes a few people to fall for the attack for it to be successful, especially if the hacker uses stolen Twilio account credentials to send the messages.
In reality, this situation is quite common, as illustrated by the following scenario:
An end user located in a European country requests philippines mobile number example authentication to access a Twilio customer's website based in the United States.
The website sends the authentication code to the end user using a US long code.
To avoid operator filtering, the sender ID is translated into a short code, which in this case had already been used by a casino to communicate with its customers.
Unfortunately, the recipient had disabled the casino's SMS sending (and blocked the short code corresponding to their messages).
The end user was therefore unable to see the authentication SMS sent by the website and kept retrying the SMS verification request until he was blocked.
In the examples above, using the alphanumeric sender AUTHMSG would improve conversion for all end users (in destinations where it is supported), ensuring that your messages are never filtered or displayed as coming from an unsavory or unrecognized number.
New feature, same consistent SMS delivery
With the new AUTHMSG alphanumeric sender, the Verify and Authy APIs continue to provide Twilio customers with the highest level of availability in a seamless manner, while building end-user trust, at no cost to the sender.
This feature will be automatically made available through Twilio APIs . One is for the Authy API for two-factor authentication (2FA) and the other is for the Verify API for Twilio phone verification . SMS messages that previously came as long codes will now be delivered with an alphanumeric AUTHMSG code in the following countries . Contact your Twilio sales representative (or Twilio Support ) to find out when and how this rollout will impact you and your users.
With over 5 billion mobile phone users worldwide, hackers are constantly looking for ways to abuse unsuspecting individuals through their connected devices. Smishing is a very common social engineering attack that uses SMS and that telecom operators are working to solve. Posing as a trustworthy entity, a malicious actor sends text messages asking for personal information such as passwords or credit card numbers. It only takes a few people to fall for the attack for it to be successful, especially if the hacker uses stolen Twilio account credentials to send the messages.