Increased fluidity thanks to new alphanumeric codes
Posted: Sun Dec 22, 2024 9:40 am
long code sms phone screen
- Long codes are intended for conversational use cases and may be filtered as spam.
short code sms phone
- Short codes are designed for sending large volumes of messages, but can be expensive and complex to manage.
alphanumeric sms phone
- Alphanumeric codes allow you to personalize the sender's name to clearly indicate the origin of the message.
Alphanumeric senders allow you to send SMS message s philippines mobile number example using a custom sender name in supported countries (see International support for alphanumeric senders ). They are useful because you can use characters to indicate where the message is coming from instead of an unknown number. The alphanumeric sender we integrate with the Authy and Verify APIs is “AUTHMSG.” This clearly indicates that the message is referring to a verification and authentication process. In countries that require pre-registration, we also register the sender with carriers so they are aware of the subject of the messages being sent.
Let's look at some scenarios where alphanumeric senders are a better option than long or short codes for sending an SMS:
1. Best end-to-end conversion globally
Most users prefer to receive SMS messages from a local number rather than an international number. In fact, some countries systematically block text messages from other specific countries. Also, carriers usually filter an international number when they notice that a large number of similar messages are coming from that number.
Let's take the following example:
Your healthcare platform is located in the United States and you have customers all over the world. A customer in France signs up for your service to consult their local doctor.
As part of the registration, you ask for the customer's phone number and send them a code to verify that the number is correct, but also that the customer is the owner of the device associated with it.
Since the message was sent via a local number with the +33 area code, your verification code is filtered as this number should be used for peer-to-peer traffic only.
The customer waits for the message and tries to sign up, while your app keeps trying to send the SMS. Your business usage costs increase for every message that is sent but not delivered. At the same time, the end user has a nightmare experience waiting to sign up for your service and abandons the process to go to a competitor.
- Long codes are intended for conversational use cases and may be filtered as spam.
short code sms phone
- Short codes are designed for sending large volumes of messages, but can be expensive and complex to manage.
alphanumeric sms phone
- Alphanumeric codes allow you to personalize the sender's name to clearly indicate the origin of the message.
Alphanumeric senders allow you to send SMS message s philippines mobile number example using a custom sender name in supported countries (see International support for alphanumeric senders ). They are useful because you can use characters to indicate where the message is coming from instead of an unknown number. The alphanumeric sender we integrate with the Authy and Verify APIs is “AUTHMSG.” This clearly indicates that the message is referring to a verification and authentication process. In countries that require pre-registration, we also register the sender with carriers so they are aware of the subject of the messages being sent.
Let's look at some scenarios where alphanumeric senders are a better option than long or short codes for sending an SMS:
1. Best end-to-end conversion globally
Most users prefer to receive SMS messages from a local number rather than an international number. In fact, some countries systematically block text messages from other specific countries. Also, carriers usually filter an international number when they notice that a large number of similar messages are coming from that number.
Let's take the following example:
Your healthcare platform is located in the United States and you have customers all over the world. A customer in France signs up for your service to consult their local doctor.
As part of the registration, you ask for the customer's phone number and send them a code to verify that the number is correct, but also that the customer is the owner of the device associated with it.
Since the message was sent via a local number with the +33 area code, your verification code is filtered as this number should be used for peer-to-peer traffic only.
The customer waits for the message and tries to sign up, while your app keeps trying to send the SMS. Your business usage costs increase for every message that is sent but not delivered. At the same time, the end user has a nightmare experience waiting to sign up for your service and abandons the process to go to a competitor.