SMS Delivery is a measure of the percentage of outgoing SMS and MMS messages which are received at their intended destination. While sometimes referring to the status of a single message, SMS delivery usually is a rate of delivered versus intended messages and summarized as an 'SMS Delivery Rate.'
As opposed to thumbing out a text on a phone, SMSes sent programmatically through an SMS Gateway have an advantage; application logic can verify delivery, increasing total SMS Deliverability by working around issues with sent messages. Through choosing reliable API partners (Twilio's current SLAs with Programmable SMS are here), implementing read receipts or falling back to a different process or number, you can keep your SMS Deliverability rate close to 100%.
Twilio's Messaging Services' Fallback to Long Code feature can automatically fall back to long codes on SMS delivery failure
Of course - even with best practices in place, you'll still have some failures. Here's how to measure your success... and how to improve it.
There is no standard time frame for measuring SMS or text message deliverability, but most often rates are quoted annually, quarterly, or daily. The equation then becomes:
TOTAL MESSAGES DELIVERED / MESSAGES INTENDED
It's important to note that deliverability isn't measured by total API calls or messages sent. Message Deliverability strictly measures how many messages are delivered versus the number intended in a defined time frame.
This key difference means that your logic can implement fallbacks and use messaging auditing features to increase deliverability, even if that requires additional API calls and redundant logic. As SMS deliverability strictly focuses on intention versus result, Twilio can help you increase deliverability through our value-added services and your business logic and code.
There are quite a few places where SMS and MMS delivery might fail, especially as messages move through the interfaces between pieces of infrastructure.
Although not an exhaustive list, common failure vectors include:
The device endpoint is an especially common vector for deliverability issues. Sometimes roaming devices or quickly moving devices do not acknowledge SMS or MMS reception, leading to messages being received more than once, or never received at all. (As with multiple API calls, messages delivered multiple times should only be counted as one delivered message.) Additionally, sometimes end devices or numbers just can't receive SMSes - Twilio's Phone Number Lookup can help solve this problem.
Note that sometimes deliverability issues are deliberate - for example, messages judged 'spam' may be blocked by our carrier partners. Twilio lists message error codes here.
Invalid numbers are the most common reason for message delivery problems. Changed (or fake) phone numbers won't reach their intended destination, decreasing your message delivery score.
As listed above, there are quite a few SMS delivery failure modes - but not all are in your control. For your application, the content and meta content as well as any recovery logic are reasonable places to improve your deliverability.
With these best practices, you'll ensure high SMS delivery rates. High-quality content and graceful exception handling will ensure you see the highest possible deliverability.
If you still would like more help with deliverability, talk to Twilio sales - we have loads of experience helping customers perfect their SMS Marketing efforts.