This post was split from the topic: Important changes to SMS by Zapier
Three things:
- By referring Zapier users to Twilio, you are expecting your paying customers to pay for a third-party service to do something that was previously included as part of our not-inexpensive monthly Zapier fees? As in “to bad, so sad, that’s the way it is”?
- This is the part that really irks me: if you knew that these changes were upcoming, and you KNOW who uses what numbers (since YOU provide the numbers to us users), why in the world did you not send notification about these changes WELL IN ADVANCE OF THE DEADLINE? What you have done is broken our critical business workflows, expecting us to fix that on a long weekend. This breaks any level of trust we once had toward Zapier as a reliable vendor.
- You can stamp your “important changes” post by blaming T-Mobile, but has anyone at Zapier stopped to consider how this could have been handled better. For instance, we are in Canada, where T-Mobile does not operate. We have absolutely no idea what mobility provider you use for the outgoing SMS numbers that YOU (I repeat YOU) provided. Do you really expect end users to interpret your “T-Mobile, T-Mobile, T-Mobile” alarms and figure out how that applies to us when YOU have that data in your systems and presumably we are paying you for your ability to handle your integrations?
We are a long-time user of Zapier, and a long-time booster of your services to developers and business owners, but with outages, issues, declining support quality, and price increases in the last couple of years, we’re reconsidering relying on Zapier. This SMS issue just might be the last straw.
I hope your management takes this feedback to improve how you operate, because in our experience with Zapier lately has been sinking rapidly.