Texting Error Codes
These are the most common error codes returned by the texting service when a text message can't be delivered. Each entry includes the underlying error code so you can quote it back to ACST Support if needed.
| Code | Explanation | Action |
|---|---|---|
| 21472 | The texting account associated with your church is not active. Realm cannot send texts until the account is activated. | If you're sure your texting account was approved, contact Support to investigate why the account is inactive. For more information about the approval process, see Application Status and Approval |
| 21610 | The carrier or the recipient's device blocked the message before delivery. This often happens when the recipient previously opted out at the carrier level, or when the message was flagged by a spam filter. | Confirm the recipient hasn't replied STOP by checking the Texts Opt-Outs tab of the Opt-Out Management page. If the same number repeatedly blocks messages, ask the recipient to contact their carrier, or contact Support. |
| 21703 | Your church's texting setup is missing a phone number, so messages cannot be sent. | Contact Support to resolve the issue. |
| 30001 | Too many messages were queued for delivery at the same time. The texting service could not accept the request. | Wait a few minutes and try again. If the error continues, contact Support. |
| 30002 | The texting account associated with your church has been suspended. | Contact Support to resolve the suspension. |
| 30003 | The recipient's phone was off, out of range, or otherwise unable to receive the message at the time of delivery. | Try again later. If the same number repeatedly fails, verify the mobile number on the recipient's profile. |
| 30004 | The recipient's carrier or device blocked the message. The cause is similar to error 21610. | Confirm the recipient hasn't replied STOP. If the same number repeatedly blocks messages, contact Support. |
| 30005 | The recipient's phone number is not recognized by the carrier. The number may be invalid, mistyped, or disconnected. | Verify the mobile number on the recipient's profile. Correct any errors and try again. |
| 30006 | The destination number is a landline, or its carrier doesn't support SMS. Landlines cannot receive text messages. | You can update the individual's profile with a mobile number. Once updated, you'll need to re-send the Opt-in Email. |
| 30007 | Your message was filtered and blocked before it reached recipients. Filtering is applied by the text carrier to prevent spam and fraudulent messages. Unfortunately, legitimate messages are sometimes filtered by mistake. | Texting Best Practices contains information that may help you understand why your message was filtered or blocked. If you receive a 30007 error, review your message content before trying again. If the error recurs across multiple messages, contact Support. |
| 30008 | The texting service reported a failure without specifying the cause. | Try sending the message again. If the error continues, contact Support and quote the code. |
| 30009 | Part of a multi-segment message did not arrive at the texting service. The message could not be reassembled and was not sent. | Try sending the message again. If the message is unusually long, consider shortening it. |
| 30010 | The cost of sending the message exceeded the maximum price configured on the account. | This error does not apply to customer sites, so you should not see it. But if you do, please contact Support. |
| 30034 (A2P 10DLC) | Message from an unregistered number.
All texts your church sends through Realm are considered A2P — meaning they are sent from a software application (Realm) to individual people. The A2P 10DLC system requires all sending organizations to be registered, which is why the enrollment process includes a Campaign Registry application. |
Complete registration before sending messages to US numbers. Or verify the number's A2P registration status. For further assistance, contact Support. |