Delivery Codes and Definitions
When viewing a Message Log generated within the Requested Reports tab, you can choose to include delivery codes based on DLR (Carrier Delivery Receipt). A DLR is an acknowledgement from a destination carrier network that a message was successfully accepted or rejected (including reason for rejection).
There are two types of DLRs: intermediate and final (handset).
What is an intermediate DLR?
An intermediate DLR means the end carrier has received the message and it's usually considered successful. In the US and Canada market for local long codes, ACCEPTD (SMPP 3.4 ACCEPTD) will be the most precise indicator of a successful message. Specifically on Local A2P & Local P2P messaging, you will only see Carrier DLRs supported.
Note: Some destination carriers, even after sending back an acknowledgement, may not be able to deliver the message due to downstream spam filters or other reasons. This is on a per carrier basis. If True Dialog does receive a clear rejection for a message, you'll always see a failed message delivery status reflected.
Even though intermediate DLRs don't represent actual final delivery to a handset, knowing that your message was received at a point along the delivery path to your customer’s handset can help with troubleshooting if True Dialog receives complaints of customers not receiving messages.
What is a final or handset DLR?
A final or handset DLR is a confirmation that your message was delivered to the recipient’s handset and will be sent back to us as DELIVRD (SMPP 3.4).
Note: Depending on the carrier, handset DLRs are only possible for A2P traffic on toll-free numbers and short codes. Carriers only provide intermediate or carrier DLRs for all P2P and A2P long code routes in the U.S. and Canada. The downstream carrier is ultimately responsible for returning a DLR in response to a request for one. If a carrier does send a final DLR, this will be updated within portal and reporting
Common Undelivered Codes and Definitions
|