Using the Messaging Error - SMS Workflow Trigger

Overview

The Messaging Error - SMS trigger allows you to start a workflow automatically whenever an outbound SMS message fails to be delivered and the system receives a specific error code. This is useful for proactively managing your contact list and improving future message delivery rates by addressing the reasons for the failure.

Trigger Details

Trigger Name

Messaging Error - SMS

Trigger Description

This trigger is activated when an SMS message is undelivered and a corresponding error code is returned. You can use it to perform actions like updating a contact's status, adding a tag, or removing them from a list to maintain a healthy sending reputation.

How to Configure the Trigger

To set up this trigger within a workflow, follow these steps:

1. Choose a Workflow Trigger: In the workflow builder, select Messaging Error - SMS from the list of available triggers.
2. Workflow Trigger Name: Give the trigger a clear, descriptive name so you can easily identify its purpose later.
3. Filters: You can add filters to target specific error codes. The available error codes are listed below:
   • 30007 - Carrier Violation
   • 30034 - A2P Registration Pending on Number
   • 30032 - Toll Free Number not Verified
   • 30005 - User Inactive/Number does not exist
   • 30003 - Unreachable/Out of Service Number
   • 30004 - Do not want SMS/DND enabled
   • 30006 - Landline/Incapable to receive SMS
   • 30023 - US A2P 10DLC - Daily Message Cap Reached
   • 21408 - Permission to Send SMS Not Enabled for Region
   • 30008 - Unknown Error
   • 21606 - Invalid 'From' Phone Number
   • 21211 - Invalid 'To' Phone Number
   • 21614 - 'To' Number Is Not a Valid Mobile Number
   • 21610 - User Replied with STOP (Opted Out)
   • 30011 - MMS Not Supported by Recipient Number or Region
   • 30033 - A2P Campaign Suspended or Deleted
   • 21661 - 'From' Number Is Not SMS-Capable
   • 21635 - 'To' Number Cannot Be a Landline
   • 30037 - Outbound Messaging Disabled
   • 30002 - Sub-Account Suspended

Example Use Case

Imagine you are running an SMS campaign to promote a new product. You want to automatically handle contacts whose messages fail to deliver due to a specific issue, like a carrier violation.

To set this up:

1. Choose a Workflow Trigger: Select Messaging Error - SMS.
2. Workflow Trigger Name: Enter a name such as "Carrier Violation Handler".
3. Filters: Set the filter type to Error Code is and select the specific error, for example, 30007 - Carrier Violation.

You can then add workflow actions, such as removing the contact from the campaign list or adding a tag to review their status later. For more complex logic, you can create multiple branches in your workflow to handle different error codes with different actions.