As the single point of contact for customers, the service desk is the face of IT. With services becoming more complex, agents now have to keep up with the range of technologies and procedures needed to effectively support customers. This makes knowledge management more important than ever. Not only does knowledge improve service quality, but it lowers the overall cost of support by boosting productivity.
Find out where your knowledge is and centralize it
As technology evolves, knowledge will exist in more and more disparate places. Information gets stuck in email, social media interactions, forum discussions, comments, tickets, and even in the brains of individual service desk agents. If you don’t already have one, aggregate your knowledge in a single repository or system as an easy solution. Centralizing all of that content accelerates learning and helps your team make better decisions. If one person holds knowledge about a particular system, have them document it. If customers are commenting about a service, update your documents with that feedback. If your team receives multiple common tickets, create an article about the topic.
Put simply, having a knowledge base to work from helps agents respond to and resolve issues faster.
Make your knowledge accessible and actionable
Resolving incidents faster means being able to find the information you need. Whether your knowledge base is confined to agents or available to customers, make sure your system is easy to update. That way, agents can flexibly refresh content and empower the team with better solutions. Not only does this improve your First Contact Resolution, but it can also reduce cost per contact.
Make knowledge management part of your workflow
We all know that carving out time for articles is hard to do when you’re fighting fires. In an ideal world, creating and updating knowledge should be part of every agent’s job. This is one of the core facets to knowledge-centered support. Craig Samuel, HP’s Chief Knowledge Officer, says that knowledge sharing is not a technology issue. In his estimation, work processes and cultural issues account for 90% of problems*. An effective knowledge management practice is about cultivating a culture of collaboration—shifting from a focus on the individual, to a focus on the team.
One way of making knowledge part of your team’s process is to ensure that articles are written before changes are implemented. When a new service is transitioned into production, documentation is available to help facilitate adoption and prevent incidents.
Keep information current to speed up agent onboarding
The time it takes to train new agents can become costly. One way to get people to deliver value quicker is to always have up-to-date knowledge accessible for your team. Your team can do this by having agents refine articles as they use them. This means that your knowledge base reflects the team’s collective experience to date.
Allow customers and agents to give feedback
Is your knowledge actually helping? Customer feedback is the best way to fine-tune your content to deliver the best answers. Without feedback, you’re shooting in the dark. This could be as simple as a “thumbs up,” or as rich as a comments section. Either way, a feedback loop drives the quality and performance of your knowledge.
Deflect tickets with self-service
Not only is knowledge management critical for agents, but it’s also important to customers. 60% of consumers use web self-service to find answers to their questions**. If knowledge isn’t optimally collected and shared, customers will simply go somewhere else for answers. Why not allow them to search for answers from a customer portal or Intranet? Enabling self-service both satisfies customers and frees up time for your team. In fact, the results of applying knowledge-centered support can mean up to 50% incident deflection.***
Measure to improve business performance
How does your knowledge add value to your organization? Which articles are being utilized the most? Measuring knowledge is the first step towards improving your team’s performance. Metrics to consider include: the number of articles attributed to First Contact Resolution, the number of articles created and updated by the team, the number of articles utilized by the team, and the number of incidents with article links.