Checking your reports for deliverability
Message errors are a part of everyday sending. After messages have left ThruText, they are sent to our provider. Sometimes, our provider encounters an issue attempting to move the message forward to the carriers. For example, you may have texted a contact from another country, and our partner refused to send the message, or a more significant issue might have occurred in the texting environment.
GetThru displays the message error code and the message error type in Message Exports. Message errors are codes generated by our providers, and while some are billable, some message errors are not billable. Errored messages can be billable, "Y" (yes) or "N" (no), according to the Message Exports "billable" column. Errors that are not billable are not counted on the Usage Analytics or the Network Account Usage pages.
Examples of billable message errors
| Message Error Code | Message Error Type | Further Description |
| 9902 | Timed out waiting for delivery receipt. The reason a delivery receipt was not received is not known. | Our message provider timed out waiting for the delivery receipt from the carrier; this could be because the downstream provider did not send the requested delivery receipt, or they sent it after the system timed out at two hours. |
| 4700 | Carrier Rejected as Invalid Service Type | Second Most Common Error Type. This usually means messaging (SMS or MMS) is not supported by the carrier or handset. We recommend not texting this number again. |
| 4720 | Carrier Rejected as Invalid Destination Address | Most Common Error Type. This could mean the number is just invalid or is not enabled for messaging. We recommend not texting this number again. |
| 4750 | Carrier Rejected Message | The destination carrier has rejected the message but provided no specific reason. |
| 4751 | Message is too long or message length is invalid for the carrier. | Carrier has rejected for message length being invalid or too long. For messages to AT&T users, messages with 10 segments or greater will be rejected. If using MMS, we recommend keeping attachments under 750kb. |
| 4770 | Carrier Rejected as SPAM | The Carrier is reporting this message as blocked for spam. Spam blocks could result from content or SHAFT violations. |
| 4771 | Rejected due to shortened url | There was an error with the shortened URL used. Our message provider recommends customers obtain their own dedicated domain if shortened links are needed for their messaging campaign or send the full URL. |
| 4774 | Issue with TN provisioning in industry database | There is an issue with how the number is provisioned in the industry's database. There may be some components of 10DLC provisioning that are incorrect or missing. |
| 4780 | T-Mobile rejected due to volumetric violation | Your T-Mobile EIN Daily Cap limits how many segments you can send to T-Mobile customers in a given day. |
| 4781 | AT&T rejected due to 10DLC volumetric violation or throttling | AT&T rejected due to volumetric violation. This error can indicate throttling by AT&T for 10DLC or other reasons, including high spam rates. |
| 4470 | Rejected as SPAM | This message has been filtered and blocked for spam. Messages can be blocked for various reasons, including, but not limited to, volumetric filtering, content blocking, SHAFT violation, etc. |
| 4740 | Carrier Rejected as Invalid Source Address | Carrier is rejecting the message due to invalid source address - the number does not exist in the numbering plan. Other reasons for this error code is the source carrier is invalid or disabled or source not authorized or the number type is not supported. |
| 4730 | No route to destination carrier or no roaming route exists. | The carrier is reporting there is no route available for the messages. This could be because no routing exists to the destination, no roaming route is available, the destination handset is roaming on a network that cannot be reached, or routing was denied. This error can also occur if the texting phone number isn't fully configured to the campaign. This error is most likely to occur if messages are sent immediately after launching, particularly within the first 2 minutes. |
| 4711 | Media size too large | The downstream vendor could not retrieve the media as the MMS attachment was too large. We recommend sending with a smaller media file. |
| 4702 | Destination subscriber is unavailable | This error indicates the subscriber is unavailable. There are several reasons for this; the subscriber has turned off handset, the destination is unreachable or barred, the GSM subscriber is busy for outbound SMS, SIM card is full, voicemail is full, or cannot reach the destination handset. |
| 4773 | Campaign inactive for destination | The TCR campaign this TN is assigned to is not active. |
| 5620 | Carrier Application Error | The carrier is reporting a general error associated with their application processing the message. |
| 9999 | Unknown error from downstream. | Provider does not recognize the vendor's error response or does not have the vendor code mapped internally. |
| 30003 | Unreachable destination handset | The destination handset you are trying to reach is switched off or otherwise unavailable. |
| 30005 | Unknown destination handset | The destination number you are trying to reach is unknown and may no longer exist, the device you are trying to reach is not on or does not have sufficient signal, the device cannot receive SMS (for example, the phone number belongs to a landline), or there is an issue with the mobile carrier. |
| 30006 | Landline or unreachable carrier | Your message was sent to a landline, or an unreachable carrier for this phone number type. |
| 30007 | Message filtered | Your message was identified as spam or unwanted, or it was flagged as objectionable and blocked by a wireless carrier. |
| 30008 | Unknown error | This means that your message was not delivered for unknown reasons. Our carrier partner provided a very generic error message that provides no further details. |
| 30011 | MMS not supported by the receiving phone number in this region | The destination handset either doesn't support MMS, or MMS is not currently enabled on the device. |
| 30034 | US A2P 10DLC - Message from an Unregistered Number | You are sending messages to the US using a US 10DLC number that is not associated with an approved A2P 10DLC Campaign. |
If you encounter an unlisted error type in your export, please reach out to support for any questions. To prevent spam errors, please follow our guide on Tips for Initial Message Creation and Recommended Replies.
Examples of unbillable message errors
| Message Error Code | Message Error Type | Further Description |
| 4432 | Messaging to country forbidden | Our message provider indicated this country is outside of messaging reach. |
| 4303 | Malformed To Number | The "To" number associated with the message is a number not routable to a carrier. |
| 4410 | Could not download media | There was an error retrieving the media. |
| 4405 | Unallocated from number | The From telephone number is considered unallocated when the number does not exist in the provider database as an active number. This number is either not enabled for messaging at the industry level, or the number is not yet released in the industry |
| 4406 | Unallocated to number | The To number associated with this message, while a valid North American number, is not yet assigned to a carrier and the message cannot be sent downstream. |
| 4360 | Message expired | Message was not sent because the specified expiration date passed before the message was able to send. |
| 21610 | Attempt to send to unsubscribed recipient | Opt these contacts out. One of our providers has a system to opt-out contacts automatically when they send specific keywords. Attempting to reply to these conversations will error. |
| 21408 | Permission to send an SMS has not been enabled for the region indicated by the 'To' number | You have attempted to send an SMS or MMS to a country that is not supported. |