SMS Features

What is URL encoding?

URL encoding converts characters into a format that can be sent through the internet. We should use URL encoding for all GET parameters because POST parameters are automatically encoded.

Why URL encoding?

URLs often contain characters outside the ASCII set, the URL has to be converted into a valid ASCII format. URLs use some characters for a special use in defining their syntax, when these characters are not used in their special role inside a URL, they need to be encoded. URL encoding is done to encode user input.

Example:

GET- https://control.msg91.com/api/sendhttp.php?authkey=YourAuthKey&mobiles=9999999999&message=test & new&mobile&sender=123456&route=default

In this API, the message content  "test & new" includes the '&' operator, due to which URL encoding is necessary, otherwise it will break your message content and an incomplete message will be sent

NOTE: If sent without a country code, submission and deduction depend on the detected country based on the starting number: For, 91xxxxxxxxxx, etc

Click here to encode

Blacklisted or blocked numbers are those which are restricted from receiving any SMS sent by the user. There are two ways of blocking any number:

One is by adding the numbers in the Blacklist Numbers option.

Another one is when we receive NDNCUCC complaints data from the Operator we block all the numbers in our Database, and messages will fail to deliver and the failure reason will show as Blocked Numbers.

Step 1:

1. Login to your Dashboard.

2. Select “SMS” from the Dashboard.

3. Click on the “Blacklist” option from the left-hand side panel.

4.  You can add all the numbers to be blacklisted here and click on “Add”. 

5. You can export all the numbers in a .csv format by clicking on “Export All Contacts”. 

How to Unblock

To unblock a number, you need to delete it from the blacklist after selecting the numbers.

SSL stands for Secure Socket Layer. 

SSL error arises when your website is not SSL certified and the one which you try to access is certified or vice-versa.

Thus the server asks for your permission to carry forward the navigation. 

To add SLL refer to this video link: https://www.youtube.com/watch?v=yHXUU60oOp8

MSG91 is a CPaaS platform to help you communicate with your users on multiple channels that provide secure and robust APIs and ready-to-use tools.

Click here for Login/Signup- https://control.msg91.com/signin/

I. Configure the channel(s) that you would like to use

​Communication Channels-

a. SMS

b. WhatsApp

c. Email
d. Voice

a. SMS-

From the Sender ID approval process to creating templates and sending SMS - Follow its doc here

b. WhatsApp

From creating a Facebook Business account to adding the number and templates- Follow its doc here

c. Email

For full Email configuration from adding a domain to sending Email - Follow its doc here

d. Voice - 

From creating templates to sending voice- Follow its doc here

For any help in the below configuration, take help from our tech support team https://calendly.com/support--msg91

II. There are 5 services to use the above-configured channels

a. Hello - Two-way communication with your customers - Tickets, Live Chat, Bot & Help-Centre - HelpDoc

Use Hello when you want to-

i) Manage your customer email tickets

ii) Facilitate your customer with live chat and view its analytics

iii) Create internal teams to manage email tickets and live chat

iv) Connect your customer on call or on-screen sharing

v) Manage your Help articles/docs and publish them for customers

b. Segmento (Contact Management system) - HelpDoc

Step by Step guide to start Segmento and utilize it fully-

i) Update your existing user data by CSV.

ii) Add API to bring new users and new user fields/attributes/events.

iii) Create Segments

iv) Send messages over SMS, WhatsApp, Email, etc. (run campaign) manually to all users of a particular segment or Automate based on user falls in any segment.

c. OTP verification service (Two-factor authentication)

​Use the Send OTP API for sending OTP SMS and using voice as backup in retry with the Resend OTP API and verifying the OTP via the Verify OTP API.

​Or you can integrate the Login with OTP Widget on your end and all these 3 APIs (Send, Resend, and Verify) will be called automatically. HelpDoc

d. Automate via RESTful APIs

​Integrate a single Campaign API for all channels - HelpDoc [Recommended]

​​

e. Integrate APIs separately for every channel -

For very specific use case which is not being solved by Campaign APIs

Use dedicated APIs -

​

i) For SMS

ii) For Email

iii) For Whatsapp

NOTE: If sent without a country code, submission and deduction depend on the detected country based on the starting number: For, 91xxxxxxxxxx, etc

You can get the report for a specific number by following the below-written steps:

1. In the SMS section, go to the Logs section from the sidebar.

2. Search the number for which you want to receive the report. Make sure you search with the country code.

3. You can also filter these SMS Route and Campaign name wise.
   
   

For checking the failure reason please hover the cursor on the status section where you will be able to see the failure reason of the message.

​

​

   Once you click on any specific number status  you will be able to see the failure reason:

NOTE: If sent without a country code, submission and deduction depend on the detected country based on the starting number: For, 91xxxxxxxxxx, etc

We are facing some issues with sending Custom/Personalised SMS (via CSV file upload or Phonebook) using the MSG91 dashboard.
As an alternate solution, you can send SMS via our Excel Plugin and Google spreadsheet add-ons..
-- Excel plugin Help Doc
-- Google sheet Help Doc

If you are observing API/server response as: "The request was aborted: Could NOT CREATE SSL/TLS secure channel", then it means that the server doesn't have a valid HTTPS certificate with the path used. But don’t worry. 

We are here to help!

The issue is observed when the SSL version being used with the code is an outdated version & the same is probably deprecated already. As a result, the API is bound to support the HTTPS protocol.

However, some of our below practices have helped users diagnose and resolve the aforementioned errors. If this doesn’t help, we’d suggest checking this with core developers.

• Upgrade to the latest code libraries if available.
  
  

• Ensure to adhere to updates TLS/SSL as the older versions may depreciate with time.
  
  

• Try DNS-Flush as this can help resolve security, internet connectivity, and other propagation-related issues.
  
  

• Ensure to use the updated versions of the code/framework (Java, PHP, .net, etc).

Now you can block the countries for SMS in credit accounts also to eliminate submissions from untargeted countries.

1. Goto the Limit Communication option in the left dashboard.

2. Search the country that you wish to block from the Search box. Click on the Block button on the right of the country to block it. Once blocked, Unblock button will be shown to unblock it.

You also have the option to Block all countries and Unblock all countries.