Message Deliverability: How to Measure Your SMS Delivery
Part 5 of a 5 part series
Your business relies on ROI. The same applies for text-messaging. It’s important to understand that you pay for every message you attempt to send…NOT just the ones that are delivered. With the messaging landscape is rapidly changing, if you’re not paying attention your messages may be getting lost on their way to the inbox. So how do you know if you’re losing money in messaging?
The fifth and final video in our “Message Deliverability: It’s not as simple as hitting send” series takes a look at how to measure and improve your SMS delivery rate.
This is where our friend, the error code comes into play. Error codes are contained within an API callback (or request for information) that is sent to your server. Every message you send that doesn’t reach its final destination gets an error code.
Error codes not only tell you where your messages were stopped, but WHY. But not all error codes are the same—different messaging routes give you different information.
P2P vs A2P Error Codes
On P2P routes, error codes can only tell you if your message makes it to your recipient’s carrier.
On A2P routes, you can track all the way to your recipient’s phone, giving you deeper ROI insight by giving you that extra step that P2P can’t.
Don’t forget your receipt
In addition to error codes, Bandwidth provides you with message delivery receipts. Receipts are provided via an API callback, or you can find them in your Bandwidth Dashboard every 24 hours, and show detailed message delivery insight at a glance.
Once you know how many messages were delivered, you can better understand your messaging ROI, AND make changes to improve your delivery rates.
Read to improve your SMS ROI?
Want to improve your SMS ROI? Visit our Message Deliverability page and request a free Bandwidth delivery assessment—it only takes a few minutes and can help you on your way to maximizing SMS engagement.