We have identified a few key issues that are causing messages to fail and want you to get these checked from your end so that you can continue to send messages to your customers with no difficulties.
Please make sure that the SMS sent from your website/app is an exact match of the approved template. Even a minute change in the registered content template can cause delivery failure.
Below are some of the use cases where the SMS will not be delivered.
- If the static content sent in the message is not a 100% match to the template uploaded in the DLT portal.
Example 1: If the message registered is:
“Success! We’ve received your entry. We’ll contact you if you are declared a winner. Visit www.abc.in. Stay #abcready. Team abc. T&Cs apply”.
and if the message sent is:
Success! We’ve received your entry. We’ll contact you if you’re declared a winner. Visit www.abc.in. Stay #abcready. Team abc. T&Cs apply”.
Why did this message fail to deliver?
The template was rejected because in the registered template, “you are” is registered instead of “you’re.”
Example 2: if the message registered is:
Hello, your OTP for abc transaction is {#var#}
and if the message sent is:
Hello, your OTP for abc transaction is {#var#}.
Why did this message fail to deliver?
The template was rejected because in the registered template “full stop(.)” was not registered.
- If the brand name is not added as per the registered template on the DLT platform.
Example: If the message registered is:
{#var#} is your one time password for ABC login. It’s valid for {#var#} minutes only.
and if the message sent is:
{#var#} is your one time password for ABC login. It’s valid for {#var#} minutes only. – ABC
Why did this message fail to deliver?
The template was rejected because in the registered template, the Brand name – ABC is not mentioned at the end of the message.
- If a spacing difference is there on the registered message template on DLT and the message sent.
Example: If the message registered is:
Hello, your _OTP is {#var#}
and if the message sent is:
Hello, your OTP is {#var#}
Why did this message fail to deliver?
The template was rejected because, in the registered template, double spacing was registered between “your” and “OTP”.
- A new line or paragraph is added in the registered template, but not in the message sent.
A new line or paragraph is formed when we press “enter” to move to the next line. If a new line was added while registering the message content with the operator, but when the same is not encoded and sent while pushing the messages via API, these messages will be rejected.
Example: If the message registered is:
Hello, Your OTP is {#var#}
and if the message sent is:
Hello,
Your OTP is {#var#}
Why did this message fail to deliver?
The template was rejected because in the sent message there is a NEW LINE between “Hello,” and “Your”.
You can fix the message failed issue with your SMS services either by uploading a new template that you wish to send, in the DLT portal, OR by sending the message content in the exact format that has been registered in the DLT platform.