Fmr employee as well. I'm gonna go out on a limb here and guess you've never been involved in running/managing a huge online community(ies) with in person social interactions as the primary goal. I might be wrong, so apologies ahead of time if so.
Anywho -
It actually isn't unprofessional when the goal is to protect the members from some organizer who might be malicious in nature. There are a lot of rules and guidance around how organizers should do things, and Support's main goal is making sure the general members of Meetup aren't preyed upon. You're idea of giving a heads up, what are the parameters around before action is taken? 24 hours? 48 hours? A week? What if this post went "i was on vacation for a week so didn't read the email, and they deleted my group, how could they!!". It wouldn't matter. TOS are TOS.
If this person was malicious how much negative should the community accept? In that time how much spamming of a product the creator is trying to sell happening? How much misleading around the member base is there?
You need to deal with these things as quick as possible, and the TOS exists to give people the framework of usage. A violation of a TOS(on any site) is just that, and it needs to be dealt with equally across violations. Support can and will make mistakes. That's human nature. THis isn't one of those. The poster in this case was even told they could re-create the group because at this point the old one is considered poisoned, and not to be trusted. Given Meetup has been doing this for over 10 years now, I'd like to think they have these policies pretty well grounded in reality and experience.
That is a great reason to say, "This one-time meet-up sounds like a better fit for $Competitor, as we are trying to foster recurring meetups", but NOT a great reason to irrevocably delete a group with no communication. TOS may be TOS, but few customers read them quite closely enough.
Is the recurring vs one-time distinction (and, more importantly, that one-time meetings are NOT welcome) made clearly? I realize that they say "Meetups are ...." on the help page, but it seems like this group really got screwed.
This meeting was for people who already followed a podcast, as part of a local software development community. There might have been later meet-ups. As long as it is clearly stated what the frequency is, does it matter if the meetups are once a month, once a year, or once a decade? You could still have a passionate community of people who want to use your system to help them organize in-person meetings.
On top of any policy / communication quirks, there should have been technical tools in place to ensure that the organizers' hard work was not lost.
When is the last time that you have read a TOS? You are shifting blame to the user, and it should not rest there. This is bad UI, and laziness. Meetup's TOS reads like a boiler-plate legal document; no one will read it.
Everything you say is correct, at the very least technically. I still feel meetup can do better here. Why not just disable the group? To everyone else it looks as though the group is gone or at least indisposed, but admins can still log in and see things while the issue gets resolved? This would also give meetup a chance to indicate to the admins why the group was disabled and options they can do to fix it. Potentially a win/win for everyone, as the group could evolve into a profitable one with a little bit of coaxing/aid.
Anywho -
It actually isn't unprofessional when the goal is to protect the members from some organizer who might be malicious in nature. There are a lot of rules and guidance around how organizers should do things, and Support's main goal is making sure the general members of Meetup aren't preyed upon. You're idea of giving a heads up, what are the parameters around before action is taken? 24 hours? 48 hours? A week? What if this post went "i was on vacation for a week so didn't read the email, and they deleted my group, how could they!!". It wouldn't matter. TOS are TOS.
If this person was malicious how much negative should the community accept? In that time how much spamming of a product the creator is trying to sell happening? How much misleading around the member base is there? You need to deal with these things as quick as possible, and the TOS exists to give people the framework of usage. A violation of a TOS(on any site) is just that, and it needs to be dealt with equally across violations. Support can and will make mistakes. That's human nature. THis isn't one of those. The poster in this case was even told they could re-create the group because at this point the old one is considered poisoned, and not to be trusted. Given Meetup has been doing this for over 10 years now, I'd like to think they have these policies pretty well grounded in reality and experience.