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.

In reply to Re^2: adding to existing cpan module by MikeL
in thread adding to existing cpan module by MikeL

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.