The "Messaging Error – SMS" trigger is a powerful automation tool that enables you to initiate workflows in response to failed SMS delivery attempts. When an SMS message cannot be delivered, the system generates a specific error code indicating the reason for failure, ranging from invalid numbers to carrier issues or blocked content. Read on to learn more about this trigger and the steps to add it to your workflow.

Implementing the Messaging Error Trigger

To add this trigger to your workflows, go to the Automation > Workflows tab. From there, either choose an existing workflow or create a new one.

Next, click the "Add New Trigger" button and search and select “Messaging Error - SMS” as the trigger event.

Assign a clear and descriptive name to the trigger to ensure easy identification within your workflow.

Add filters to refine the trigger by specifying particular error codes. This allows you to target and respond only to relevant messaging failures, ensuring that your workflow is activated under the appropriate conditions.

The following error codes are supported by this feature and can be selectively included or excluded based on your specific requirements:

• 30003 - Unreachable/Out of Service Number
• 30004 - Do not want SMS/DND enabled
• 30005 - User Inactive/Number does not exist
• 30006 - Landline/Incapable to receive SMS
• 30007 - Carrier Violation
• 30032 - Toll-Free Number not verified
• 30034 - A2P Registration Pending on Number

Once you are satisfied with your configurations, go ahead and save the trigger to your workflow.

By leveraging this trigger, you can automatically respond to these undelivered messages with tailored workflows, such as notifying internal teams, retrying the message, or escalating the issue for further review. This not only improves communication reliability but also enhances your ability to proactively manage messaging errors and maintain a seamless customer experience.