Comment by jgalt212
4 days ago
I don't see a problem with this. B2B2C is a tricky dance with many stakeholders whose business needs are often ignored. If procurement cancels a service that users need without telling the users, which they have been known to do, that's a big problem.
Counterpoint: don’t spam my users or I’ll cut off contact at the network level and block your app from running on our laptops.
Sounds a bit disproportionate. If you do that, you better hope the vendor's CEO and your company's CEO are not golfing buddies.
And in my mind, one email alert or pop-up to all current users letting them know the service is going away (in case they had not been told which is as I've said before often the case in large orgs) is very far from the definition of spam.
Conversely, I would not work for a CEO who would block me from doing my job duties. I'm hired to do a job. If I can't do that job, there's no point in being here. Other companies will pay me for my judgment.
If this happened in real life, I'd say "Joe," (because I'm on a first-name basis with the CEO and chat with him daily), "we had to block communications from Tom's company because they're pulling some bonkers stuff. You might let him know that he's pissing off customers right and left and needs to knock it off."
And yes, this is 100% the definition of spam. It's literally unsolicited commercial communication. Sending these mass instructions to flood the local IT admins is an enormous breech of trust.