Include SMS error as trigger in Workflows | Voters

Include SMS error as trigger in Workflows

Norbu Losang

Currently, if a phone number cannot receive an SMS we just get an error. Whatever the reason for the error, it would be so helpful if we could use SMS error as a trigger. So that we can notify ourselves if we need to reach out to a prospect to get another (functional) phone number. It is impossible at scale to manage this otherwise. Thanks!

March 18, 2024

Ben Vickers

Pretty sure this feature is already active.
The following SMS error codes are selectable as a trigger under the trigger "Messaging Error - SMS":
- Landline / SMS incapable
- USA Toll free # not verified
- Unreachable
- Carrier Violation
- Number doesn't exist
- A2P Rego pending
- SMS DND active
I recently had an issue with error 30006 not triggering, but this now works.  Ive not personally tested any of teh otehrs, such as A2P.

Ben Opps

+1 to all of this AND please include ALL error types as possible workflow triggers. It looks like this feature request was partially done - it is currently possible to trigger workflows based on "SMS incapable" or "Not valid" error codes. However, this would be waaaay more useful if we could trigger based off of any SMS failure code. Other options include things like "unreachable destination handset", "error code 32107", "unknown destination handset", etc. These should all be options to trigger a workflow. Please and thanks!

Chad Lukens

THIS IS A HUGE ISSUE WITH A2P BEING SUCH A BEAR WE ARE LEFT WITH NO EFFECTIVE WAY TO MANAGE AND IMPROVE.

Even if the trigger is LC SMS error generically. If we could get the content of the error and use that as a value we send externally create note etc, that would make our life SO much easier. We are trying to figure out why clients are getting shut down and it takes copious amounts of effort to go in and hover over each message read the error and then record it to get a feel for what is going on and the work around is currently watching for opt out and dnd etc which is only so effective. Building reports is almost impossible this way. The data is there because you can see it when you hover over it so being able to add it to a report, webhook payload and a note would be awesome.

Gracen Duffield

There is a twilio validation error, but I did not see one for the LC phone.

Norbu Losang

Gracen Duffield They do not have the feature for LC phone yet.. But hopefully soon!

Alexis Counts

Gracen Duffield Twilio Validation feature will work for LC Phone Users :)

But for other errors for message filtering, this is not yet a feature. Hopefully soon!

Melissa Smith

Yes, this would be so great!

Ken Barnes

This would be really great!

Gee Tamayo

This would be great!

Charles Palaming

This is a very great idea!

Emily Zezov

This would be very productive. Great idea!

Cynthia Fenwick

YESSSS!! This would be very helpful

→