Set a date (and user) for content review

This is a great idea, and it’s surprising to see this hasn’t generated more traction with Gainsight’s product team, especially since it’s still very relevant. Like many others, we manage content across both CC and CE, and the ability to schedule content reviews natively in these tools would save a lot of manual effort while helping ensure our published materials stay accurate and up to date. 

There are lots of use cases for which this would be beneficial. Here are some that immediately come to mind: 

• Announcements and updates that expire or need a follow up (e.g., product releases, events/incentives, upcoming changes, beta program info)
• Knowledge base articles that are published before all the details are available, or that need to be refreshed as the product evolves
• Media assets with limited usage rights or relevance (like images or videos that need to be removed or replaced after a year, or as the product evolves, co-branded assets)
• Content tied to policies or regulations that need to be reviewed on a regular cadence 
• Educational content that’s seasonal, recurring, or tied to a time sensitive programs

Being able to set a review date, leave a note, and assign it to a specific admin or moderator (with an email or system reminder when it’s due) would make this process much more manageable. More importantly, it would help CC and CE customers by keeping content timely and relevant.  

As an org using both CC and CE, this would be a major quality of life improvement for our admins and moderators. It would also help eliminate unnecessarily tedious manual tracking and follow-up work. Ultimately, this comes down to content hygiene, which is something I suspect to be a shared priority across the board for most Gainsight customers managing community or education platforms. 

Assigning a content review date and owner in Gainsight would be transformative, fostering simpler collaboration with clear accountability and deadlines – essentially a built-in CTA like we have in Gainsight CS.

This idea would directly translate to higher quality content and better efficiency by ditching manual tracking. A valuable implementation for streamlined content management, and a step forward towards #parity across the entire Gainsight ecosystem, providing a more consistent and comprehensive user experience.

Couldn’t agree more with the comments above! In addition, I’ll offer another perspective that I am increasingly feeling pressure here in our new AI age. We’re finding that community content is surfaced in LLMs in a way that’s much harder for us to track. And while there’s a ton of potential here for even broader impact and utilization of knowledge from our community, there’s a correspondingly greater risk of someone seeing a less-than-accurate post. This tool would be a massive advantage in our ability to make and keep our community accurate.