People often use a mix of approaches to create knowledge bases. Some hire consultants for initial setup and strategy, while others rely on customer service representatives to develop and maintain the content. Knowledge bases can be created when a helpdesk is first established as they gather more insights and frequently asked questions.
The information for a knowledge base typically comes from customer service interactions, feedback, and common inquiries. It can also draw from existing documentation, product manuals, and input from various teams within the organization.
Thanks guys! That information was super useful - I took a crack at building a tool that can turn helpdesk tickets into a nice knowledge base (mainly for the Breeze AI Customer agent).
We use the knowledge base as a shared resource, and KB articles are created by all departments, for both internal and public use, but we are still in early days of usage.
It's great for creating things like FAQs on topics that you can send out repeatedly as a link in an email.
We (Support team) are currently working on creating a peer-review process prior to publishing for client documents, so that we can be sure we are providing the most accurate and current information.
People often use a mix of approaches to create knowledge bases. Some hire consultants for initial setup and strategy, while others rely on customer service representatives to develop and maintain the content. Knowledge bases can be created when a helpdesk is first established as they gather more insights and frequently asked questions.
The information for a knowledge base typically comes from customer service interactions, feedback, and common inquiries. It can also draw from existing documentation, product manuals, and input from various teams within the organization.