Skip to main content

Sender ID

  • FAQs on Sender ID

    1. What is a Sender ID?

    Sender ID is the name that appears as the message sender of an SMS message on the recipient’s device. Sender IDs are a useful way to identify yourself to the recipients of your messages.

    Support for sender IDs varies by country. For example, carriers in the United States and Canada don't support sender IDs. Carriers in India require the use of sender IDs.
    Sender IDs are classified as one of two types.

    1. Dynamic Sender ID: Customers can start sending messages with custom sender IDs immediately in countries that support Dynamic Sender ID. Simply enable the geo-permission for that country through your Plivo Console.
    2. Pre-registered Sender ID: Please follow these steps to request a sender ID in countries that require pre-registration. 
    • Sign in to the Plivo Console
    • Navigate to the Messaging tab and select the Sender ID option
    • Click ‘Register Sender ID’ button
    • Click on the ‘Pre-registration’ option. You will see a list of countries along with the cost and review times involved for registration
    • Select the countries from the list to which you wish to be registered. 
    • Fill out other details: like SMS use case, sender ID, sample message, business website etc.
    • Attach the documents required for the registration and click ‘request sender ID’. Please note that this may vary from country to  country
    • Following a review, you will be assigned with a sender ID that you can use to send messages to customers in pre-registration countries.

    2. What is the difference between Dynamic SenderID and Pre-registered SenderID?

    Customers can start sending messages with custom sender IDs immediately in countries that support Dynamic Sender ID. Simply enable the geo-permission for that country through your Plivo Console. For countries that require pre-registration, you must go through some additional steps to get set up. Recurring charges vary depending on the country of registration.

    3. Which countries support Dynamic sender ID?

     Here is the list of countries that support Dynamic Sender ID.

    4. Which countries require a Pre-registered sender ID?

    Here is the list of countries that support Pre-registered Sender ID. Along with basic information about the company, pre-registration requires the submission of documents and recurring charges for each sender ID. This may vary from country to country. Click here for the list of countries with cost and time details required for pre-registration.

    5. Why is there a need to Pre-register the sender ID?

    Register your Sender ID to represent your brand/company name, as well as help monitor and prevent SMS fraud. The telecommunication laws of certain countries mandate sender ID registration for the protection of consumers and companies.

    6. What is the process for sender ID registration?

    To set up a sender ID, please submit your request by completing this registration form in your console. You can select one or multiple countries at once depending on your business needs. Once the request is approved, the Sender ID will be set up for your account.

    7. What are the requirements for registration of the sender ID?

    The common requirements when submitting a sender ID registration request are:

    1. SMS Use case - promotional or transactional
    2. Preferred alphanumeric sender ID
    3. Sample message
    4. Your company name
    5. Company website
      For pre-registration, you may be required to submit additional documents according to the country. For example, in Indonesia, you are required to submit a Letter of Appointment (LOA) that authorizes Plivo to register and send branded messages on your behalf

    8. What is the pricing for sender ID registration?

    For countries that do not require pre-registration, sender ID registration is free and instant. Countries that require pre-registration have varying charges to get set up. Click to review the pricing for countries requiring pre-registration.

    9. How does sender ID help in highlighting the brand name?

    The sender ID represents your brand/company name distinguishing it from a million others. It plays a massive role in defining your brand to your customers. Branding your SMS messages allows you to make an instant connection with your customer or client. Your message is more likely to be opened and read, driving higher engagement with customers and improving brand recognition.

    10. Are there any restrictions on selecting a sender ID?

    The preferred alphanumeric sender ID must abide by the following criteria:

    1. Enter between 2 - 11 characters that represent the brand identity of the Sender. You can include upper- and lower-case letters, the numbers 0 - 9, and spaces.
    2. Include at least one letter.
    3. Do not use ASCII special characters (e.g. #, @).
    4. For India, the sender ID must be exactly six characters.

     

  • Pre-registration country - Charges & ETA for Sender ID

    Below is the list of pre-registration countries along with the overall setup fee, recurring fee and ETA for Sender ID registration:

     

    Country

    Setup fee ($)

    Recurring fee (per month in $)

    ETA (in days)

    1

    Russia

    181

    290

    14

    2

    Kenya

    117

    0

    14

    3

    Kazakhstan

    58

    128

    15

    4

    Kuwait

    35

    0

    30

    5

    Czech Republic

    18

    30

    14

    6

    Vietnam

    14

    14

    60

    7

    Belarus

    0

    0

    10

    8

    Cuba

    0

    0

    120

    9

    Egypt

    0

    0

    30

    10

    Indonesia

    0

    0

    60

    11

    Japan

    0

    0

    2

    12

    Jordan

    0

    0

    10

    13

    Oman

    0

    0

    7

    14

    Palestinian Authority

    0

    0

    10

    15

    Philippines

    0

    0

    7

    16

    Qatar

    0

    0

    10

    17

    Sri Lanka

    0

    0

    7

    18

    Tanzania

    0

    0

    60

    19

    Thailand

    0

    0

    3

    20

    Turkey

    0

    0

    60

    21

    United Arab Emirates

    0

    0

    10

    22

    Saudi Arabia

    0

    0

    26

    *This is subject to change as per country/carrier/end operator regulations

     

     

  • List of countries based on Sender ID regulations
    Supports Sender ID with Instant Registration (109 countries) Supports Sender ID with Pre- Registration (22 countries)
    $ - Represents countries that have charges for Sender ID registration
    Sender ID not supported (42 countries)
    Albania Belarus Afghanistan
    Algeria Cuba Argentina Republic
    Andorra Czech Republic - $ Azerbaijan
    Angola Egypt Brazil
    Armenia Indonesia Burkina Faso
    Australia Japan Canada
    Austria Jordan Chile
    Bahrain Kazakhstan - $ China
    Bangladesh Kenya - $ Colombia
    Belgium Kuwait - $ Costa Rica
    Belize Oman Croatia
    Benin Palestine Dominican Republic
    Bolivia Philippines Ecuador
    Bonaire, Saba, Sint  Eustatius (Former NL Antilles)        Qatar Ghana
    Bosnia & Herzegov. Russian Federation - $ Guatemala
    Botswana Sri Lanka Honduras
    Brunei Darussalam Tanzania Iran
    Bulgaria Thailand Korea S Republic of
    Cambodia Turkey Lesotho
    Cameroon United Arab Emirates Madagascar
    Chad Vietnam - $ Malawi
    Congo Dem. Rep. Saudi Arabia  Mali
    Congo Republic   Mexico
    Cyprus Morocco
    Denmark Mozambique
    El Salvador Namibia
    Estonia New Zealand
    Ethiopia Pakistan
    Federated States of Micronesia Panama
    Finland Paraguay
    France Puerto Rico
    French Guiana Serbia
    Gabon South Africa
    Georgia South Sudan (Republic of)
    Germany Syrian Arab Republic
    Gibraltar Taiwan
    Greece Tunisia
    Guinea Turkmenistan
    Guyana United States
    Hong Kong (China) Uzbekistan
    Hungary Venezuela
    Iceland Yemen
    Iraq                                          
    Ireland
    Israel
    Italy
    Ivory Coast
    Jersey and Guernsey
    Kiribati
    Kyrgyzstan
    Laos P.D.R.
    Latvia
    Lebanon
    Libya
    Lithuania
    Luxembourg
    Macao (China)
    Macedonia
    Malaysia
    Maldives
    Malta
    Marshall Islands
    Mauritius
    Mayotte (FR Indian Ocean Territories)
    Moldova
    Monaco
    Mongolia
    Myanmar (Burma)
    Nepal
    Netherlands
    Nicaragua
    Niger
    Nigeria
    Northern Mariana Islands (US)
    Norway
    Papua New Guinea
    Peru
    Poland
    Portugal
    Reunion
    Romania
    Rwanda
    Sao Tome and Principe
    Senegal
    Seychelles
    Sierra Leone
    Singapore
    Sint Maarten (Former NL Antilles)
    Slovakia
    Slovenia
    Solomon Islands
    Somalia
    Spain
    Sudan
    Suriname
    Swaziland
    Sweden
    Switzerland
    Tajikistan
    Timor Leste (East)
    Togo
    Uganda
    Ukraine
    United Kingdom
    Uruguay
    Zambia
    Zimbabwe

    *India is not in the above list because there is a different process for registering in India, i.e., DLT registration

    Dynamic Sender ID - Customers are expected to have a sender ID registered against their brand name. They can send using any preferred Sender ID to these countries but if the messages are coming through a non-alphanumeric sender ID, Plivo will automatically replace it with the registered sender ID.

    Pre-Registration: Customers are requested to upload the required documents through the portal. Registration will happen in the background and customers will be updated post the registration process.

    Sender ID not supported: SMS will be delivered but the Sender ID used in the From number will be replaced with local numbers or shortcodes or a generic code based on the country regulation for delivery

     

     

  • DLT registration process for sending SMS to India

    The Telecom Regulatory Authority of India (TRAI) has mandated all entities that want to send SMS to register their organization, headers & templates along with the required consent information on the DLT platforms, to curb Unsolicited Commercial Communication (UCC).

    Please find the registration process below:

    Step 1 – Get Unique Entity ID

    Register on any of the DLT platforms below by filling in the required information and documents and get a temporary ID. After the verification of your documents by the Operator, you will receive your Unique Entity ID.

    Note:

    • According to customer feedback so far, JIO seems to have a  shorter and easier registration process.
    • Please share your reference number/temporary ID/Unique ID and registered entity name with us if you have registered on any of the DLT platforms.

    Step 2 – Add Telemarketer & Register Headers

    Once you get your Unique Entity ID, add Telemarketer ID and register your headers in the DLT platforms.

    To Add Headers –

    • After the registration is complete, you can start adding your headers (Sender ID) under the Headers tab in the dashboard. Please refer to the attached guide for the header registration process.
    • There are 2 types of Headers to choose from – Promotional & Others.
    • For sending campaigns promotional in nature like offers, discounts, promotions, etc., you need to choose a 6-digit numeric sender ID which will be prefixed with your industry
    • For sending campaigns transactional in nature like updates, notifications, etc., you can choose your preferred Header Name. Add your preferred Header Name in the text box and mention the reason for choosing the Header in the description box below

    Please note – the Header selected by you should match the entity name. If the header name is different, please justify the same and add your mobile number in the description box. The mobile number will help the DLT support team to contact you in case of any queries.

    To add Telemarketer –  

    Go to Telemarketer tab in the DLT platform > Search TeleMarketer Name and add 

    In the Select Telemarketer box > Search and add TM ID: “xxxxxxxxxxxxx” in the “Enter your Telemarketer ID” textbox > Click on Verify. 

    Please write to us(https://support.plivo.com/support/tickets/new ) with your registered Entity ID for Telemarketer Name and ID details

     Note –

    • Only entities with registered headers will be able to send SMS. Please reach out to us once your headers have been approved.
    • Headers (Sender names) are case-sensitive i.e. ABCDEF and abcdef are two different sender names and can be registered separately.

    Step 3 – Register Consent & Content Templates

    After you have registered your business and headers (sender IDs), the next step in the DLT registration process is to add your content templates and customer consent information. 

    Consent Templates and registering guidelines : 

    Consent Template is a Standard message that is sent to end-users of the enterprise for their consent to receive communications from the respective enterprises. 

    Note: While creating a consent template, the following details are to be provided

    • Template Name: Name as per the choice 
    • Brand Name: The product/trade name or if they have multiple brand names 

    Ex: Enterprise “Jococo Food Kitchen” owns 3 brand portfolios “ Doscos Pizza; Munch Donuts & Katey's Kitchen”. 

    Scope of consent: Content they want to send to end-users (We would like to send communication regarding all marketing offers and events to our registered customers. {opt-out procedure can also be given}). It should not contain any actual message contents. 

    Ex: 

    • Would Like to Send Communication Regarding All Marketing Offers and Events to Our Registered Customers 
    • “ABC Solutions” needs Your Consent in Order to Serve You Better. We May Send You Messages About Your Account Information, Activity, and Our Best Offers 
    • We will send you updates, transactions, recommendations of our services, or products being a registered customer with us.

    With the above details filled, the enterprise can submit the template for approval. There is no limitation for enterprise on the creation of no.of consent templates. Post-approval by the registrar, the enterprise can link these consent templates to their content templates in promotional or service category accordingly (As shown in below snapshot) 

    Do’s for Consent Template

    • Choose a relevant short name to the template.  This helps in choosing the right consent template while creating content templates in promotional or service explicit categories.
    • Brand name should be relevant to details mentioned in scope of content 
    • The scope and intent of content should be very clear and relevant to the mentioned brand. 
    • If an entity wants to provide opt-out information, that needs to be provided completely. Example: “To opt-out, send SMS as STOP to 5555555”

     Don’ts for Consent Template

    • Do not use generic names for templates like “template1; etc..
    • Do not mention invalid or irrelevant names or popular brand names. This will be treated as an invalid template.
    • Do not enter actual message sent to the customer
    • Do not enter shot messages like “consent; SMS to customers; etc…”
    • No variables can be used in the scope of consent, as variables are applicable only to content templates.

    How to register a consent template in the DLT portal?

    For Jio DLT Platform:

    • Select Template > Consent Registration
    • Add a template name and your brand name
    • Add ‘Template Consent’ which is the standard message that is added to your T&C or any other document informing them about their consent to receive communications from respective enterprise
    • After adding your consent template, add a list of consented customers.
    • For adding phone numbers – Select Customers’ Consent > Bulk Upload

    Content Templates and registering guidelines :

    How to Add Consent Templates –

    Transactional

    Any message which contains OTP and requires to complete a banking transaction initiated by a bank customer will only be considered as transactional. This is applicable to all banks (national/scheduled/private/govt and even MNC’s).

    • OTP message required for completing a net-banking transaction. 
    • OTP message required for completing credit/debit card transaction at a merchant location. 

    Example: 234567 is the OTP for txn of inr 57.75 at Izaak payment services PVT with your sbi card xx3931. OTP is valid for 10 mins. pls do not share with anyone

    Actual Message

    Template Format

    234567 is the OTP for txn of inr 57.75 at Izaak payment services PVT with your sbi card xx3931. OTP is valid for 10 mins. pls do not share with anyone

    {#var#} is the OTP for txn of inr {#var#} at {#var#} with your sbi card{#var#}. OTP is valid for {#var#}. pls do not share with anyone

    234567 is your OTP for fund transfer for the amount Rs.6,000 to Raja. OTP valid for 8 minutes. Do not share this OTP with anyone.

    {#var#} is your OTP for fund transfer for the amount {#var#} to {#var#}. OTP valid for 8 minutes. Do not share this OTP with anyone.

    234567 is OTP for your eComm Txn for the amount Rs.25,000 OTP valid for 8 minutes. Do not share this OTP with anyone.

    {#var#} is OTP for your eComm Txn for the amount {#var#} OTP valid for 8 minutes. Do not share this OTP with anyone

     

    Service Implicit

    Any message arising out of customers action or his existing relationship with the enterprise, that is not promotional will be considered as Service-Implicit message.

    • Confirmation messages of a Net-banking and credit/debit card transactions.
    • Product purchase confirmation, delivery status, etc. from the e-comm website.
    • Customer making payments through Payment Wallet over E-Commerce website / mobile app and an OTP is sent to complete the transaction.
    • OTP’s required for e-comm website, app login’s, social media apps, authentication/verification links, securities trading, Demat account operations, KYC, e-wallet registration, etc.
    • Messages from TSP/ISP.
    • Periodic balance info, bill generation, bill dispatch, due date reminders, recharge confirmation (DTH, cable, prepaid electricity recharge, etc)
    • Delivery notifications, updates, and periodic upgrades.
    • Messages from retail stores related to the invoice, warranty.
    • Messages from schools-attendance/transport alerts.
    • Messages from hospitals/clinics/pharmacies/radiologists/pathologists about registration, appointment, discharge, reports.
    • Confirmatory messages from app-based services.
    • Govt/DOT/TRAI mandated messages.
    • Service updates from car workshops, repair shops, gadgets service centers.
    • Directory services like Justdial, yellow pages.
    • Day-end/month-end settlement alerts to securities/Demat account holders.

    Actual Message

    Template Format

    Thank you for using EMI Facility on your XXXX Bank Credit Card 4***1234 EMI request for Rs. 89000.00 executed on 01/07/2019

    Thank you for using EMI Facility on your IDBI Bank Credit Card {#var#} EMI request for {#var#} executed on {#var#}

    XXX BANK - Your new bill for BESCOM Bangalore - account 0123456000 for Rs 4339.00 could not get scheduled because the auto-pay limit is less than the bill amount.

    XXX BANK - Your new bill for {#var#} - account {#var#} for Rs {#var#} could not get scheduled because the auto-pay limit is less than the bill amount.

    Account: 123456 is your Pansoi account verification code.

    Account: {#var#} is your Pansoi account verification code

     

    Service Explicit

     These are the messages which require explicit consent from the customer, that has been verified directly from the recipient in a robust and verifiable manner and recorded by the consent registrar. Any service message which doesn’t fall under the service-implicit category.

     Note: Additionally, the customer consent template needs to be linked to content templates in the service explicit category.

    • Messages to the existing customers recommending or promoting their other products or services. 

    Actual Message

    Template Format

    Your Rs.500 exclusive voucher is UNUSED!! Redeem it on purchase of Rs.1,000 at M&M. Use code 654321001 Valid till 31st Mar 2020! T&C.

    Your Rs.{#var#} exclusive voucher is UNUSED!! Redeem it on purchase of Rs.{#var#} at M&M. Use code {#var#} Valid till {#var#}! T&C.

    Thai massage 60min(1): 2455.93,aroma massage 60min(1): 1525.42,s.total(2): 2881.35,

    Thai massage {#var#},aroma massage {#var#},s. total{#var#},

    Hi, In order to best serve you and others, could you click on mosl.co/ywq8FBJpAn to share your meeting experience with Ojas Insurance representative on 22

    Hi, In order to best serve you and others, could you click on {#var#} to share your meeting experience with {#var#}

    Baba Finserv Personal Loan needs Minimal Documentation. Fulfill your financial needs in one click http://m.BabajFin.in/Iphr8tFE .T&C

    Baba Finserv Personal Loan needs Minimal Documentation. Fulfill your financial needs in one click {#var#}.

     

    Promotional

    Any message with an intention to promote or sell a product, goods, or service. Service content mixed with promotional content is also treated as promotional. These messages will be sent to customers after performing the preference and consent scrubbing function.

     Note: Additionally, the customer consent template needs to be linked to content templates in the service explicit category.

    Actual Message

    Template Format

    Lifetime Free XXXX Bank Credit Card with Vouchers from LensKart, Pepperfry, Grabon worth Rs.3000. SMS “apply” to 5676766 TnC apply

    Lifetime Free XXXX Bank Credit Card with Vouchers from LensKart, Pepperfry, Grabon worth Rs.{#var#}. SMS “{#var#}” to 5676766. TnC apply

    Pay JUST Rs 640* pm & get Rs 83,333 for 120 months or payout of Rs 1,00,00,000 With LIC*(Life Insurance Cover) For Your Family. http://px2.in/pAD4Tls

    Pay JUST Rs {#var#} pm & get Rs {#var#} for {#var#} months or payout of Rs {#var#} With LIC (Life Insurance Cover) For Your Family. {#var#}

    YOU can win Rs 20,000 in Fantasy cricket use code 542321. Install XXX app now to WIN Click - https://abc.com

    YOU can win Rs {#var#} in Fantasy cricket use code {#var#}. Install XXX app now to WIN Click - {#var#}

      

    Content Template Validations

    • Usage of 2 or more spaces is not advised between 2 words, before a word or after a word.
    • currently, all special characters are allowed. 
    • The variable format is {#var#} which is case sensitive. Or variable can be inserted by clicking the radio button (insert variable). 
    • Trans/Service category messages should have variable mandatorily
    •  Promo category can have complete fixed content or with a variable part.
    •  There is no limitation on the number of variables per message
    •  Values like amount, date, a/c no, merchant names, OTP, codes, URL, customer names, card type, etc. need to be replaced with variables

    Do’s for Content Template

    • Use promotional category for communications intended to send from numerical sender id only. 
    • Transactional category to be used by banking enterprises only & for OTP messages during fund transfer; online payment; merchant transaction only. 
    • Service – explicit category needs to link the consent template as well, without which the template gets rejected. 
    • Choose a relevant/recognizable name for templates. 
    • Use the message type as “TEXT” for all general messages & “Unicode” for regional messages. 
    • Variable {#var#} insertion to be required against values like a date; amount; a/c no; OTP; names; etc

    Don’ts for Content Template

    • Not linking consent templates for content template categories “promotional” & “service – explicit”. 
    • Same content template against multiple headers. 
    • Header selection against irrelevant templates. 
    • Selecting the “Transactional” category by non-banking enterprises. 
    • No or invalid variable format in templates. 
    • Using double spaces in templates (this can be pre-checked by verifying the template on notepad++ before template submission). 
    • Templates with less than 6 char or variable insertion alone as a template.

    How to register a content template in the DLT portal?

     For Jio DLT Platform:

    • Select Template > Content Template Registration
    • Choose template type as SMS
    • Choose your content type – English or other languages
    • Select a Category from the drop-down list
    • Select Consent ID from the drop-down list
    • Choose a type of communication – Promotional / Transactional / Service Inferred / Service -Explicit.
    • Select Header from the drop-down list
    • Add the template content in the ‘template content’ text box and click Submit.

     

  • What are the fees for registering a Sender ID?

    Plivo Support works with carriers to set up the Sender ID based on carrier regulations and the destination country. This may involve a one-time setup fee of USD 25 exclusive of carrier charges* for Sender ID registration for each country.

    There is no fee to enable a Sender ID for destinations where the Sender ID is dynamic. However, Plivo will still need to vet the use and business cases to enable alphanumeric Sender IDs.

    *Certain countries have additional carrier charges for Sender ID traffic. As it is subject to change, this information will be shared with customers on a case-to-case basis after getting a confirmation from the respective local carriers.

    How can I get more than one Sender ID for my account?

    Multiple Sender IDs on an account are only supported on an account that works across different countries. Multiple Senders IDs for the same country are not supported on the same account. 

    For instance, if you have registered the Sender ID "Plivo" towards Denmark from your main account, we are not able to register the Sender ID "PLVSMS" towards Denmark on that same main account. However, it is possible to register a second Sender ID from a sub-account. 

    Can the Sender ID be changed at a later point?

    Yes, the Sender ID can be changed at a charge of USD 25 per country. Read more regarding Sender ID registration by clicking here.

  • Country requirements for Sender ID registration

    Sender IDs are specific to each country. Every country has certain regulations with which Plivo and its carriers need to comply. 

    • For certain countries, Sender IDs are dynamic, meaning that they do not require pre-registration with the respective carriers for that country.
    • For other countries, Sender IDs do require preregistration with the respective carriers. 

    What countries require Sender ID pre-registration?

    Sender IDs must be pre-registered for the following countries. Messages may not be delivered if the Sender ID is not pre-registered. 

    Belarus, Cambodia, Egypt, Nepal, Norway, Saudi Arabia, Sri Lanka, Turkey, United Arab Emirates

    Sender ID registration is recommended, but not mandatory, for the following countries. Messages will be delivered with a generic Sender ID, such as ‘SMS’ or ‘INFO’ if there is no custom Sender ID pre-registered. 

    India, Indonesia, Jordan, Kenya, Kuwait, Nicaragua, Oman, Philippines, Qatar, Russia, Tajikistan, Tanzania, Cuba. 

    What countries do not require Sender ID pre-registration? 

    Sender IDs are completely dynamic in the following countries.* You may set the Sender ID to any acceptable alphanumeric term. 

    Algeria, Anguilla, Antigua and Barbuda, Aruba, Australia, Bangladesh, Barbados, Belize, Bermuda (UK), Bhutan, Bosnia and Herzegovina, Botswana, British Virgin Islands, Burkina Faso, Burundi, Cameroon, Central African Republic, Croatia, Cyprus, Democratic Republic Congo, Denmark, Dominica, Estonia, Falkland Islands, Fiji, Finland, Gabon, Gambia, Germany, Greenland, Grenada, Guadeloupe & Martinique, Guernsey, Guinea, Guyana, Haiti, Honduras, Iceland, Ireland, Israel, Ivory Coast, Jamaica, Japan, Latvia, Liberia, Lithuania, Luxembourg, Macao, Malawi, Maldives, Malta, Martinique, Mauritius, Monaco, Mozambique, Netherlands, Niger, Nigeria, Papua New Guinea, Portugal, Republic of the Congo, Samoa, Seychelles, Sierra Leone, Singapore, Slovakia, Slovenia, Somalia, Spain, St. Lucia, Sweden, Switzerland, Togo, Tonga, United Kingdom, Vanuatu, Zambia

    Alpha Sender ID is fully dynamic in the following countries. Numeric Sender IDs will be replaced with a generic alpha ID: 

    Albania, Angola, Armenia, Austria, Azerbaijan, Bahrain, Brunei, Chad, France, Georgia, Greece, Hong Kong, Iraq, Italy, Laos, Lebanon, Libya, Liechtenstein, Macedonia, Mauritania, Moldova, Montenegro, Morocco, Myanmar, Namibia, Poland, Réunion (France), Senegal, Serbia, South Sudan, Sudan, Swaziland, Timor-Leste, Uganda, Ukraine, Uzbekistan, Zimbabwe.

    If the destination to which you wish to send messages does support Sender ID, then you can have your account whitelisted for Sender ID. Learn more in our articles on registration and charges.

    *While the above countries are fully dynamic, messages with alphanumeric Sender IDs may still be rejected. This is because Plivo accounts are not enabled for alphanumeric Sender IDs by default.

    Kindly contact support if you’d like to enable this feature for your Plivo account.

  • Guide to Registering a Sender IDs

    What is a Sender ID?

    Sender ID is the alpha name or alphanumeric name or number that appears on a mobile phone as the sender of an SMS. It identifies who sent a message to the recipient. A Sender ID can be a number, such as a mobile phone number, or an alphanumeric term such as PLIVO or PLVSMS. 

    How is a Sender ID useful?

    A Sender ID uniquely identifies your business and helps customers remember your brand. 

    Why is registration required?

    Some countries require that you register your Sender ID. These countries have a restriction that only allows A2P messaging registered with network operators. Likewise, registering your Sender ID in advance increases the delivery rate of your messages and reduces the chances of getting blocked by carriers. 

    Check the list of countries that support Sender ID by clicking here.

    What is the process of registering a Sender ID?

    In order to register a Sender ID, you must submit the following details:

    • The Sender ID you wish to use
    • An explanation of the use case for the Sender ID
    • Destination countries for which you need this Sender ID
    • Your company/business name
    • Sample message content
    • Your company/business website
    • Sender ID expansion. For instance, PLVSMS for PLIVO SMS

    Once all these details are shared with Plivo Support, we will get in touch with carriers in the destination countries and work to register the required Sender ID. It takes approximately 10-15 business days for the registration to be completed. 

    What are the prerequisites/restrictions to register a Sender ID?

    • You must have a Plivo standard account in good standing. This service is not available to customers on a free trial account. 
    • The Sender ID is between 6-11 characters, depending on the destination. 
    • The Sender ID cannot contain spaces or hyphens. 
    • The Sender ID cannot be registered for promotional messages.

    Will there be any additional charges to get the Sender ID registered?

    Yes, there might be additional charges to get a Sender ID registered. 

    If you wish to register a Sender ID, please open a ticket with Plivo Support using the ticketing portal: https://support.plivo.com/support/home 

    Once a Sender ID is registered to your account, read our Sender ID documentation for help setting up this feature. 

  • Does Plivo support alphanumeric sender ID for SMS?

    Plivo supports the use of alphanumeric sender IDs, however, you must whitelist your account by contacting Plivo support to enable this feature. Your request should include the sender ID you wish to use, the destination countries you intend to reach, and your specific use case in the support request.

    In addition to Plivo’s restrictions on the use of alphanumeric sender IDs, country-specific restrictions may also apply. In some countries, alphanumeric sender IDs must be pre-approved by the local regulatory bodies. In other countries, no such approval may be required. For countries where regulatory bodies mandate pre-approval of sender IDs, Plivo will facilitate the approval process.

    The whitelisting process can take up to three business days if approval from local carriers and regulatory bodies is not required. Approval from local carriers and regulatory bodies may take up to eight weeks.

    Alphanumeric sender IDs are not supported in the US and Canada.

    Contact us with your specific use case for more details.

    Why is whitelisting for alphanumeric sender IDs required?

    Plivo enforces stringent checks on the use of alphanumeric sender IDs to ensure that all communication originating from Plivo is legitimate and in no way facilitates malicious activities such as social engineering, phishing, vishing etc.

    Why would Plivo reject my request for alphanumeric sender ID whitelisting?

    Plivo will first and foremost seek to verify the legitimacy of your business, as it applies to the sender ID you wish to use. In some cases, we may request an official authorization from your organization’s legal department verifying the use of the requested sender ID. If your sender ID is based on a specific product or service that your company provides, Plivo may seek specific information to establish this association.