Microsoft Dynamics CRM has a fairly detailed system around capturing and tracking knowledge base articles and knowledge in general; however, when talking about this feature in the field I have found people want to "upload" a word document or who might not want to "change".
The key with the Dynamics CRM KBA is that you have a process for filtering good "will be useful for a long time" knowledge from "every bit of detail" that might cross a support person's desk.
The product wants a human to think about what they are putting into the KBA and the product has a "draft, review and publish" feature for management as well.
I have found that even at the smallest firms this systematic approach can increase their ability to offer high quality and extremely efficient support. After just a few months, junior resources can look to the KBA as opposed to using up valuable human bandwidth when they are first researching a problem and as any of us who have managed a support department know, 80% of all questions are redundant.
Teach your team to share what they know will be asked again with a simple process and let the noise go. Then teach your resources to leverage the internal Search tools.
The Process:
From Microsoft Dynamics CRM,
Choose Service,
Choose Knowledge Base,
Create a new Item
1. Create a title
2. Add some key words
3. Type the "Question" or "Problem Addressed"
4. Cut and Paste in the solution (most likely from an e-mail that you already sent to the client)
Total Time = 5 minutes
It is all habit, good management and process