Reason for switch is that Plivo keeps shutting me off!
My txt sending app simply notifies subscribers of weather events from their own weather station - it is not marketing. Their weather station regularly uploads data to my server, which hourly analyzes their data and sends them any notifications they've opted in for, e.g. temp below 36F.
I originally built the app for myself, on my winery&vineyard website, then over time it grew to encompass other subscribers.
Now, with 10DLC, you must register every app with your upstream provider.
At first they refused me due to the fact that it's on the website of an alcohol producer. Fine, at significant pain to my customers, I've moved the website to my generic webhosting URL so as to disassociate from alcohol.
But they still just can't grasp the fact that a subscriber has to login to the website, and go to a Preferences page in order to en/dis-able their txt msging.
I've spent many hours in moving the website and working with customers to re-configure their weather stations. I've already spent about as much money on failed attempts to get 10DLC approval as I spend on an entire year of sending txt msgs, and I'm still not approved. I'm hoping Twilio will be able to handle this better. |