Interpreting Message Error Codes

  • Updated

 

Virtually all text messaging actions (whether Peer-to-Peer or Broadcast) will encounter some level of errors in sending. Ideally, these errors are relatively minimal. Sometimes your action may encounter a higher-than-usual level of erroring, whether due to list cleanliness, script content (more info on script best practices here), or 10DLC registration status. Regardless, it's helpful to be able to assess your texting action's error performance. 

This article will walk you through how to access this information, and how to interpret the meaning of each error code you might receive. 

 

How to Access Error Code Information

The easiest way to assess the error codes that are impacting your texting action is by navigating to the Errors table on the View Results page of either a Peer-to-Peer Texting or Broadcast Texting action. From your action page (whether P2P or Broadcast), click View Results, then scroll down to the bottom of the page and click the "Errors" tab. This tab will open a table of the error codes being encountered by your texting action, and how prevalent each one is. 

Screenshot 2023-08-31 at 2.23.29 PM.png

 

If you'd like to pull a CSV report of errors on a per-contact/per-message basis for a certain action, navigate to Data > Exports, then select the export type Messages. (You can also access the Messages export from the bottom of that action's results page.) You'll find the error code(s) associated with each contact/message in column AE, "error_code", and a description of the error code in column AD, "aasm_message." Learn more about exports here

 

Error Types

There are three types, or categories, of error codes that may occur during your texting action: 

 

Impactive Safeguards

These errors are filtered out by Impactive before your messages even reach Twilio/carriers, to save you money by not attempting to send messages that won't go through. These errors often have to do with messages being sent to a certain contact too frequently, an undeliverable landline number, etc. More on Impactive's 10DLC safeguards here

 

Twilio Errors

These errors occur when Twilio (our messaging provider) attempts to send messages and has an issue. These errors often have to do with invalid phone numbers, 10DLC registration issues, etc. Find a full glossary of errors here, directly from Twilio's support documentation (use Control-F to find a specific error). 

 

Carrier Filtering

These errors occur when Impactive and Twilio have passed your messages through, but carriers (AT&T, Verizon, etc.) prohibit them from reaching the recipient. This is error code 30007, explained in more detail by Twilio here; essentially, carriers will filter messages if they suspect them of being spam or fraud. Adhering to script best practices can minimize this error type.

 

Glossary of Common Error Codes

Error Code

Type

Description

1001

Impactive Safeguard

Recipient has received an identical (duplicate) message already. 

1002

Impactive Safeguard

Recipient has been messaged within the last 6 hours and your "Prevent Frequent Texting" setting is ON. 

 

This setting can be turned OFF, in Campaign Settings for either Peer-to-Peer Texting or Broadcast Texting, if you would like to allow recipients to be messaged more than once within 6 hours. 

 

Can also occasionally mean blank message or blank number. 

1101

Impactive Safeguard

User attempts to send a message to a contact that is neither a campaign contact nor their personal synced contact, so phone number is not available.

1105

Impactive Safeguard

User within this campaign attempts to send a message to a contact that is not on a list belonging to this campaign. 

1107

Impactive Safeguard

Message could not be sent via Twilio's API after 10 tries, usually due to an invalid number of some sort. 

1112

Impactive Safeguard

Recipient has been marked Hostile within Impactive and will not receive further messages. 

1114

Impactive Safeguard

Opted-out contact.

1202

Impactive Safeguard

Messages sent after campaign's allowed texting hours. (Edit allowed texting hours in Campaign Settings > Peer-to-Peer Texting and/or Broadcast Texting > Texting Hours.) 

1204

Impactive Safeguard

Number recently resulted in a Twilio error. 

1205

Impactive Safeguard

Invalid mobile number (landline, etc.). 

1206

Impactive Safeguard

Contact on National Do Not Call List.

1207

Impactive Safeguard

Unable to send message due to heavy carrier filtering.

1301

Impactive Safeguard

Contact not opted-in to broadcast.

1302

Impactive Safeguard

Opted-out contact. 

1303

Impactive Safeguard

User attempts to send message to a contact that they are not assigned to, and typically is instead assigned to another user. 

1305

Impactive Safeguard

User attempts to invite a personal synced contact to the campaign, but contact has already been invited by user. 

1306

Impactive Safeguard

Invalid phone number (landline, etc.) or opted-out contact. 

1310

Impactive Safeguard

T-Mobile daily message cap exceeded (will reset tomorrow).

1311

Impactive Safeguard

T-Mobile daily message cap exceeded (will reset tomorrow).

9000

Impactive Safeguard

Invalid mobile number (landline, etc.). 

9001

Impactive Safeguard

"Message locked," typically due to invalid phone number (landline, etc.). 

12300

Twilio Error

"Invalid content" - usually related to an error with an uploaded image (for MMS).

30003

Twilio Error

"Unreachable destination handset" - usually means invalid mobile number (landline, etc.). 

30005

Twilio Error

"Unknown destination handset" - usually means invalid mobile number (improperly formatted, out of service, etc.) 

30006

Twilio Error

"Landline or unreachable carrier" - usually means landline or out of service. 

30007

Carrier Filtering

Filtered by carriers in the course of routine spam/fraud protection. 

30008

Twilio Error

"Unknown error" - unfortunately, this error type is simply unknown.

30011

Twilio Error

MMS not supported by the receiving number.

30023

Twilio Error

"US A2P 10DLC - Daily Message Cap Reached" - usually means that your campaign has exceeded daily messaging limits, often for a single carrier (usually T-Mobile). If your campaign routinely encounters this error to a large degree, reach out to us at support@impactive.io; we can help file an appeal to boost your daily limit with that carrier(s). 

30024

Twilio Error

"Numeric sender ID not provisioned on carrier" - usually means number is out of service.

30034

Twilio Error

Traffic filtered due to lack of full 10DLC registration; reach out to support@impactive.io for help with registration next steps. 

 

More Questions?

Encountering an error code not listed here, confused about your action's error results, or any other questions? Reach out to us at support@impactive.io

 

Was this article helpful?

/