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

Sounds like a fun project!

I also went through the 10DLC registration on Plivo and they approved the company profile easy enough (satisfaction surveys delivered to renters on behalf of landlords), but got hung up on associating a number with a campaign. AT&T approved but T-Mobile failed it, no reason given. I removed the association and tried again, and it went through after a few days.

Did you create the controller for "STOP" and "HELP" verbs? I'm not sure if they tested that, but I implemented those before I tried registering just to make sure I was complying with their rules.

A different way to handle the alcohol-association problem might have been to set up a second website (can be on the same server) that only handles the Plivo SMS endpoint, and could just say stuff about weather. That way none of your users would need to reconfigure anything.

Replies are listed 'Best First'.
Re^4: adding to existing cpan module
by MikeL (Acolyte) on May 18, 2023 at 17:35 UTC
    Dealing with Plivo support has been pretty much the worst tech support experience I have ever had in my life (I've been in the computer industry since 1978).

    I simply could not make them understand that I'm basically a hobbyist, that there's only about a dozen recipients, that all of them have spent hundreds of dollars for weather station equipment and demand these txt msgs, and that I'll never send but a few messages in a day.

    Yes, I did "move" the entire project away from the winery website to my webhosting businesses URL. If you look closely at the winery website, there is still a link to the project, but nobody would look there as it's not called out in any plivo registration. If you believe plivo, no alcohol-related business will ever be allowed to market via txt msg. Yet just yesterday I read about an advertising company that is doing marketing for small wineries via txt msg...

    Thanks for mentioning the HELP and STOP words. I explained to them that there was a help response which includes the URL to the website. I also explained that unsubscribe was done by a checkmark on a settings page in the website after the user has logged in.

      I would still recommend implementing STOP. It shouldn't be too hard (10 lines of code?), and could be handy if a bug in the service went on a sending spree and someone wasn't at their computer.