Thanks Jake!
I realize that I wasn't totally clear on my initial ask. Apologize to all for the long post!
For our Community, we lock down topics based on our pre-defined business criteria to avoid necroposting, topic hijacks, and runaway threads. In our Community we support OOTB products as well as platform development for Apps, which are heavily influenced by specific business use case requirements.
In our platform development support forums, we are seeing a trend where Members have the same question, however, based on their particular use case, the question may be the same, but the member specific business use case requirements are different. So the designated Accepted Solutions and/or associated replies, do not capture the subtle differences on a use case basis - thereby initiating the community member action to follow up on legacy topics.
It is worth mentioning that we are investigating the "Me Too" rating feature. Based upon initial analysis, our community categories that support our product developers, Me Too is a "voting" system and can not support members who have the same question with the above and beyond business use case considerations. (Will not bore anyone with further detail beyond that!)
Right now, our members have to create new topics and create the hyperlinks to the original topic, or our moderators have to "create new topic's" and insert the hyperlinks to the originating topic to ensure transparency/continuity. (naturally - with appropriate notifications to the OP of our actions) I don't know about anyone else - but our capacity allocation for moderation support has low bandwidth as we support multiple channels. (internal/external)
In our annual SBR meeting with Khoros, we were discussing new platform functionality, and this topic was raised. Our Community team had captured this topic for something as a follow up item (clearly - I won that action item). 🙂
Our understanding from this discussion was that, for topics that were blocked for new replies, there was a Community feature which we could leverage the facilitation on new Topic generation on existing topics where the Block New Replies had been implemented. This would support the minimization on moderation demand while also improving out Community member experience. .
Rather than entering a case (I thought I would spare the Khoros Community team this time around), I wanted to check in with the Khoros Community to see if anyone else had some feedback, as I couldn't find anything based upon my search criteria.
Based on your response, I have now reached out to our Account Team to clarify our understanding of this discussion point during our SBR.
When I have feedback from them, I would be happy to update this thread for the benefit of others in the Khoros Community who face a similar situation/question, if for no other reason than that this is the behaviour we encourage within our Community! 🙂
Again - my understanding with our Khoros account team from a month ago may be flawed. So more to follow based on our follow up!
Best,
Leigh
