alt Hacker NewsIt kinda depends on which platform handles their bulk messages. For example, if they are messaging you through Twilio, replying with "STOP" will cause Twilio itself to opt you out of messages (https://help.twilio.com/articles/223134027-Twilio-support-fo...), and the sender can't disable that (https://help.twilio.com/articles/360034798533-Getting-Starte...). It's kinda like how Mailchimp handles unsubscriptions for recipients, no matter what the sender wants.
However, if they're using some other carrier or rolling their own VOIP setup, etc., or sending from a toll-free number instead of a shortcode, there's no guarantee that their particular platform will honor STOP. And there's no way for you, as a recipient, to know which is which.
Generally I will reply STOP if it's something I know I signed up for but no longer want. Things I never signed up for just get reported as spam and I don't reply.
Replies
Twilio is sort of a dream for spammers, they'll just make new accounts on it and spam campaigns on those new accounts. Political organizations do it all the time, if you get on a list you're never getting off. Lookup the numbers sending to you (Twilio's own lookup tool works great for this) and it almost always comes back Twilio/Zipwhip.
I only recommend responding STOP to short codes since there's more investment and vetting on getting a short code. Carriers will intercept the request for TFN/local numbers sometimes but I don't really trust it. These numbers are all going to be spammers buying pools of numbers to churn and burn. They'll just import their list into a new account if it unsubs.
Oh and btw, it's actually easier now as a spammer to tell when numbers get burned. A few years back when the CTIA handover on regs happened (and sending costs went up) the carriers finally started to respond with the delivery status of the sent messages. Before this they didn't respond and you only knew your provider delivered the messages to the carrier, not whether the carrier delivered them to the handset.
You can check if a number is using Twilio via a special number: https://www.twilio.com/en-us/blog/lookup-phone-carrier-recor....
Twilio actually does allow companies to opt out of the automatic STOP handling (I've done it while working on a txt automation system).
There is a tiny bit of vetting involved and you've got to be a slightly larger account, but it is possible, so it's not safe to assume that if the message is coming from Twilio that STOP will block them at the platform level.
Worked for a company that offers marketing & transactional SMSes: our SMS provider relayed the STOPs and we were obligated to honor it, but the provider couldn't check it.
Also, the provider relayed the STOP to the last of their client that reached the number, they had no way to trace it back with 100% confidence.
Unsubscribing from one Mailchimp subscription doesn't remove you from any other subscriptions...
Speaking mostly for the US here.
The STOP keyword is mandated as unsubscribe at the carrier level (Verizon, ATT, TMo) not just the vendor level. So if you reply STOP, it's very likely that you will not receive another message from that number.
This will be true for any programmatic SMS vendor. There could be smaller scale & more manual approaches, but that would be rare.
There has been a big effort in the last year+ to clean up the space and require consent before any SMS is sent.
FWIW, somewhat surprisingly, my google pixel has an amazing spam filter for SMS and I rarely get SMS that I don't want.
What I want to know is, what's the purpose of those random texts that just say something like, "How's it been?" from a number that I've never communicated with? What's the angle there? Anyone know?