The Community Management team reviews content on an ongoing basis throughout the day based on three primary sources:
- Abuse Reports sent by members
- Content actively reviewed by our Community Specialists
- Flagged content from our rules and AI engine
Abuse Reports From Members
Members are a critical part of the compliance effort of our Community Policies. Members see the content early and have a unique insight into whether a post or comment is relevant to the company they are following. We take every abuse report sent by a member seriously, and each report will be manually evaluated by a Community Specialist against all Community Policies.
As a member, we ask that you respect this process and don’t be frivolous in your claims. Frivolous claims mean we waste time evaluating content that would be better spent identifying real issues. Together we can keep the community discussions constructive and positive.
Content Actively Reviewed
The Community Management team comprises Community Specialists who review and assess content on-site throughout the day. We follow trends in activity, hot topics, how members interact with each other, and many other factors in determining where we focus our efforts. If we identify content violating one or more Community Policies, that content will be removed.
We do not expect that we can review every post on-site. The sheer number of posts that occur in the day runs into the thousands. We rely largely on the Abuse Reports from Members to highlight concerning content.
Stockhouse has built some sophisticated tools that will help the Community Management team identify and evaluate potential violations of the Community Policies. Each flagged post or comment from our engine will be raised to a Community Specialist to review and evaluate. Every report is looked at by a team member to ensure that we have a personal evaluation of the content to ensure we aren’t incorrectly taking down any content. All legitimate content is very important to us and the community, so we’ll do our best to ensure content remains up on site.