2 of 5 Migration of MSO links to MSE links

Since I can't find a contact email anywhere on their site, I've submitted a request via their "Panic Button" sales form. Since I don't know where that goes, I'm copying the text here on the off-chance that someone from Woo finds this post:

###Please don't just redirect your support forum to WordPress Answers

It recently came to our attention that y'all are redirecting folks looking for your community forum to WordPress Answers. Folks on that site are not particularly happy about this: http://meta.wordpress.stackexchange.com/questions/2595/woocommerce-dumping-its-support-here-in-a-direct-menu-link

While WordPress Answers is an excellent place for technical questions on WordPress development - including the use of 3rd-party extensions and themes - it is NOT a general-purpose discussion forum, and folks expecting it to be will be upset to find their questions closed and deleted.

Stack Exchange works really well for technical support, as long as you're not trying to outsource your entire customer support channel to Stack Exchange. There's a good meta post covering the issue below; the top two answers are worth reading:

Is it okay to use Stack Overflow as the support forum for a product or project?

We've had the best results from following the model used by Google Android to support their developers (http://android-developers.blogspot.com/2009/12/hello-stack-overflow.html). Following their example, we've put together a few guidelines about how to use Stack Exchange for community support:

Start with a page on your site listing where members should go for various support-related tasks. Stack Exchange should only be ONE of the options available. Make sure you have other resources for support apart from Stack Exchange. Issues like bug reporting, feature requests, generalized discussions, and specific customer support issues do not fit into our Q&A model, and will be quickly closed by the community.

Please don't try to "seed" common questions about your product on Stack Exchange. Our communities are very sensitive to this type of astroturfing, and they can react very negatively when a company seems to be posting staged questions simply to get them out there on Stack Exchange. You don't want to be labeled a spammer. Communities expect questions to represent actual problems asked in good faith from those who are actually seeking the help.

While we have a very active community, there are some questions that can only be answered by one of your internal team members. Make sure you jump on these quickly to establish your tag as THE place to get help with the harder questions. Have someone on your team whose job it is to monitor the tag daily and respond to any unanswered questions. Monitor activity on your tag using tag filters and subscriptions. You can setup a subscription to notify you or your team whenever there is new activity on your tag at http://stackexchange.com/filters/.

I hope you find these suggestions helpful, and are able to quickly take action to avoid further confusion for your users and distress to our community. If you have any further questions, please don't hesitate to ask.

-Joshua Heyer, Community Manager at Stack Exchange

The above is based on the standard advice, written by Robert Cartaino, that we provide to organizations seeking to integrate Stack Exchange into their support system. Hopefully, the good folks at WooThemes are able to respond.