Reasons a post was flagged as abusive?

Question

Is there a way for a regular user to report WHY they are flagging a post as abusive? 
 I had a community member flag a post as abusive, but I couldn't figure out why. I reached out to him directly and he confirmed he flagged it as a duplicate. Giving this user that option (versus spam, offensive, etc.) would help me as the moderator narrow down how to review this. I thought I've seen this before, but I can't find an option for it. If not, I'll create an Idea for it.

Ben Tiedt · Answer

I apologize. Let me attempt again. 
 Christopher G. Stanton said: But that isn't in the platform user interface by default for some reason? 
 The functionality was originally in the platform to inquire about a reason for abuse at the time the report is filed and, based on feedback, it was simplified to a single action while leaving the API for backwards compatibility or customization. At the time, the feedback we received was that the two step process was cumbersome and unneccessary. 
 Christopher G. Stanton said: At which point is something a "you should do this via your own customisation / our customisation services" vs "we will include it in a future release" ? Clarity on this would be helpful and ease frustration. 
 Over the history of the Community platform, there have been a few features that have flipped back and forth (often related to SEO as recommendations changed, but also user-related features that have gone in and out of favor over time). This feature was one that is being requested to be restored by feedback after being asked to be removed by feedback. That's not a bad thing and expectations and use-cases change over time. The goal of the platform is to provide a successful initial experience for the majority of users. When a feature request/change has significant support, it is considered to be included in the product by default. 
 Specifically to address when should a feature be custom vs. included in the product: 
 
 It should likely be custom if it is not a generally beneficial feature. We gauge this by market review and the ideation. 
 It should likely be custom if it is needed sooner than it will be included in the platform if it is scheduled to be included in the platform by default. 
 It should likely be included in the platform if it is requested by a significant number of existing customers and/or is a market/strategic direction.

Reasons a post was flagged as abusive?

Top Replies