FAQs
Q1. What happens when an SMS is sent to a user who is out of network coverage?
The SSP integrated with the Lemnisk will receive all the SMS campaigns you set to create engagement. Even though the user is out of network coverage or if the device is switched off, these SSPs will continue to attempt delivery as per the queueing duration specified while creating the campaign.
During the attempt,
The message can be dropped by the SSP when the queueing duration expires before the user can be reached.
The message will be dropped by the SSP right away after the first attempt at delivery if queueing is disabled while creating the campaign.
If a user receives multiple messages while out of network range or with their phone off: As soon as the user is reachable, all messages will be sent back to back.
Q2. Why messages do not get delivered to some users?
Messages may not get delivered to some reasons due to various reasons like incorrect phone numbers, unsupported geographical locations, out-of-network, expired monthly quota, and so on.
Q3. Why do the messages get queued for some users?
The messages get queued to the campaign's target audience because the messages are lined up for delayed delivery. It happens in DND hours or based on the frequency cap settings that are applicable to the users.
Q4. How to check whether my template is working or not if I get a new DLT template?
Once the configuration is saved, you can test if the credentials are working fine by using our Try It Out option.
Click on the TRY IT OUT tab.
In the Text Message add a DLT-approved text message template.
In To, enter the mobile number you want to send the SMS to.
You can see the API response in the Response section.
Q5. Why SMS Notification not get delivered?
There are several reasons that make your SMS notification undelivered. The most common reasons are:
Frequency Caps: This failure occurs when the frequency cap limit is exhausted. It depends on parameters that are measured daily, weekly, monthly, or over a lifetime. Users whose frequency cap value is >0 will receive your engagement. To learn more about Frequency Caps, click here.
Personalization Failure: This failure indicates that the engagement failed to send while replacing the personalizing parameters with the actual value stored in the users' profile. Use Case: Suppose there is a user in a segment with no premium amount registered. You create engagement for that segment of users using a premium amount macro with an expiration date. The user with no registered amount will not receive the engagement as that parameter does not exist in his/her stored profile.
Hard Bounce: Hard bounce events from SSP will be displayed here when they occur for a particular SMS. If we receive a hard bounce, it means that either the number is invalid or the person has blocked the sender. Therefore, the user's contact number must be marked as unreachable for any further SMS communications.
Insufficient Credits: If the ESP quota limit has been reached or there are not enough credits available with the client, it will fall in this category.
Invalid Sender ID: If the sender's user ID is invalid.
Dropped: A vendor's decision led to SMS being dropped. Each vendor can drop it for several reasons.
Last updated
