The discussion revolves around implementing Knowledge-Centered Support (KCS) in Discourse. marceld is seeking suggestions on how to adapt KCS to the Discourse support model, having moved from a traditional CRM. Their initial idea involves creating a private thread for case work, which is then locked and potentially moved to a public category.
osioke clarifies the KCS definition and asks about the limitations of the previous CRM and expected gains from switching to Discourse. They recommend using the Discourse Docs plugin for documentation and leveraging email support via a specific plugin.
IAmGav suggests using the Discourse Assign and Discourse Solve plugins to implement marceld’s idea.
marceld appreciates the suggestions and explains that the move to Discourse is part of a shift towards a community-centric support model. They also thank IAmGav for the plugin recommendations, which they will explore further.
Hi,
My company is moving from a traditional CRM to Discourse. We’ve been using the KCS process to document solutions to cases. I’m trying to figure out how to implement KCS within the Discourse support model and looking for suggestions on how to make this work. One thought is that an agent creates a thread in a private category while their case is being worked. When they’re done, the thread is locked and, if it makes sense to do so, moved into a public category for users and other agents to find.
Have any of you implemented KCS in Discourse? Should I be thinking about this differently? Any suggestions would be appreciated.
Thanks Osioke. I’ll take a look at those plugins. I think they’ll be helpful.
The move is not about limitations with the CRM. We’re moving to a support model that revolves around the community. to that end, we’re updating our overall support workflows with the community as the primary entry point for issue reporting and discussion.