Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

  • Home
  • Get Help
  • Troubleshooting
  • Zap Sequence Breaks (& Stops Entire 45 Step Zap For Every Recipient) Every Time Someone Unsubscribes via Twilio with an SMS STOP Message

Using Facebook Lead Integration, we ingest email and phone number parameters. 

 

At some point in the 30 day sequence of “SMS texts” (these are educational texts), if an active recipient “Unsubscribes” from the Twilio texts with a STOP Unsubscribe message, the Zap sequence doesn’t know this and continues to ATTEMPT to send texts to the recipient based on their position in their respective 30-day sequence. 

At a certain point, the Zap STOPS all executions for all SMSs for every active recipient in the sequence with the ERROR message: Attempting to send SMS to an unsubscribed recipient. 

 

What is the solution/workaround to integrate the “unsubscribe” signal back to the active Zap so it opt outs the “unsubscribed” lead rather than continuing to send to it - thereby breaking the entire zap for every lead in the active 30-day sequence?

 

This is very frustrating. The same happens for non-validated phone numbers. 

Hi @MarcusAurelius 

Good question.

 

Twilio help articles related to SMS Opt-Out/Unsub: https://www.google.com/search?q=unsub+sms+twilio+webhook

 

Sounds like you probably want to redesign your Zap into multiple Zaps to address some of these issues/shortcomings.

 

You’d be better served using a operational hub app to track and trigger your sequence, using a database app like Airtable.

  • Airtable has Views.
  • View can have Filters. (e.g. Days = X)
  • Views can be used to trigger Zaps.

Plus doing so will likely save you Zap Tasks while offering more flexibility.

 

At a minimum you need to log the unsubscribes somewhere. (e.g. Airtable Base.)

Then you can add additional Zap steps before each SMS send. (Then again that’s only adding more Zap Tasks.)

  • Find Record
  • Filter

Tremendous answer. Thank you so much for taking the time!

Hi there, @MarcusAurelius!

Just wanted to check-in to see if you were able to solve this using Troy’s suggestions here? Eager to make sure you’re all set! 🙂

Terms & Conditions