This report will help you understand the flow of knowledge articles and who is the most productive in your organization.
Download the webinar slides: Metrics For IT Help Desk & Customer Service Organizations
This is specifically for each knowledge article. There is also a report to tell you when articles were created, last modified and last used.
Download the webinar slides: Metrics For IT Help Desk & Customer Service Organizations
This report will tell you which knowledge article categories are most helpful and highly rated. This will help you monitor and keep the knowledge base relevant to user/customer needs.
Download the webinar slides: Metrics For IT Help Desk & Customer Service Organizations
This report is the holy grail to obtain the appropriate KPIs/metrics for an incentive program to reward people for submitting high quality knowledge on an ongoing basis. It is easy to run and very objective.
When an article is used, the problem solving score is incremented by 1. This happens when the article is copied to a resolution in a ticket or emailed to a customer.
Articles are rated by agents as they are using the articles and by customers as they are using the self help portal.
Problem Solving Score- Knowledge Base Record
When a knowledge base record is used, a "Problem Solving Score" is incremented. The search engine utilizes these ratings to prioritize subsequent knowledge base search results. Reports use the "Problem Solving Score" to indicate which knowledge base records have the highest value and which may need improvement.
User Rating Score-Knowledge Base Record
An Agent can rate knowledge base records each time they are used. The search engine utilizes these user ratings to improve subsequent knowledge base search results. Reports use knowledge base record ratings to indicate which records have the highest value and which may need improvement.
A knowledge base system should learn and get "smarter" over time.
Download the webinar slides: Metrics For IT Help Desk & Customer Service Organizations
In ten seconds or less, can you determine which Agents are generating knowledge records and at a very granular level can you determine if this knowledge is solving problems?
Does your firm provide valuable incentives to reward Agents for building and maintaining a high quality knowledge base?
In ten seconds or less, can you determine what categories of knowledge customers need?
In ten seconds or less, can you determine the quality of knowledge by user ratings and how often knowledge records were used to solve problems?
In ten seconds or less, can you determine if an increase in knowledge records is causing an associated increase in First Contact Resolution?
Knowledge Base Records by Creator
This report helps you to understand which knowledge creators are creating high value knowledge. This report displays all the status of knowledge records by each user. It also displays the numbers and percents of all the different status of knowledge base records at a given time. The report tracks:
The number of knowledge base records each user has proposed.
The number knowledge base records each user has had rejected.
The number of knowledge base records approved. For knowledge base records approved, the report will display the problem solving score and the user rating, if you drill down.
Download the webinar slides: Metrics For IT Help Desk & Customer Service Organizations
Root Cause Analysis Reports, like other 'deliverables' can vary in quality. Each stakeholder can have their own qualitative and quantitative acceptance criteria. There are some general possibilities for evaluating root cause analysis outputs.
First: Is it readable? If it is readable it will be grammatically correct, the sentences will make sense, it will be free of internal inconsistencies, terms will be defined, it will contain appropriate graphics, and the like.
Second: Does it contain a complete set of all of the causal relationships? If it did contain a "complete set of all of the causal relationships" one could (at least): 1. Trace the causal relationships from the harmful outcomes to the deepest conditions, behaviors, actions, and inactions. 2. Show that the important attributes of the harmful outcomes were completely explained by the deepest conditions, behaviors, actions, and inactions.
Download the webinar slides: Metrics For IT Help Desk & Customer Service Organizations
Study the FCR by category to help give you insight to whether new knowledge articles could be useful on specific topics. This will also point you to agent training issues.
Ultimately, customers are more concerned with issue resolution than contact resolution—the call is just the means to the end, hopefully. Recognizing this, customer surveying should be geared to the type of issue that was reported. For instance, if it was a billing concern, it makes the most sense to contact the customer for resolution feedback after they have received the next bill rather than 2 days after they called the contact center. They may think their issue has been resolved but don't really know for sure until they see the correction on the next bill. An after-contact follow-up surveying approach that is geared to check back with the customer after a milestone has been accomplished probably makes the most sense for issues that take some time to resolve. Post-call surveys can easily be deployed to tackle one-and-done calls, to ensure that your agents are handling them effectively and to the satisfaction of callers.
A multi-source FCR measurement approach is best. Because it can be challenging and costly to measure first contact resolution, a multi-measure approach is more flexible. For instance, customer satisfaction surveys can be used to determine overall FCR performance, by contact type, while call quality monitoring results and post-call surveys can deliver agent-level FCR performance and at the same time, point out developmental improvement opportunities. Internal call statistics can be used to calculate overall center-level repeat-call performance, and if your system permits, agent and team level repeat-call performance. Try a set of measures to gather as much information as possible about your customer service response.
Download the webinar slides: Metrics For IT Help Desk & Customer Service Organizations
This is a trend customer service report showing the percentage of total service requests resolved by the Customer Service team over time. With this trend report, you are able to see your progress toward your goals.
Customer feedback surveys also have the potential to find out whether issues are ultimately resolved to the customers' satisfaction. Internal measurement can only assume, by the lack of a repeat contact, that the issue was resolved. You really don't know for sure if it was resolved or if the customer just gave up, unless you ask the customer. And the timing of when you do ask the customer is important too—has everything happened that needed to happen to resolve the problem?
Internal FCR metrics are necessary for root cause analysis and process streamlining. Call quality FCR determinations and FCR call stats are great for identifying training and coaching needs, and process improvement opportunities. Most CRM systems facilitate the tracking of customer contact. That is after all the goal of a customer relationship management system—to know everything possible about customers and their interaction with the company. Other customer support systems may not be structured to so easily track and measure contacts and resolution.
Agent logging can also gather FCR performance by contact type, however it's really not appropriate for measuring individual agent performance due to the built in bias of agents determining whether the contacts they handled were resolved or not. If you do use agent-driven measurement, audit the results periodically and/or use it in combination with other measures, such as a customer satisfaction measure of FCR and a call quality monitoring measure of FCR.
Repeat-call calculations, agent logging and tick sheets, and call quality-monitoring determinations are all approximations of customer experience. Most companies have found that internal first contact resolution measures are overstated—the customer's view of first contact resolution is usually lower than an internal measurement. In other words, don't get too comfortable with your measurement of your performance, ask your customers too. If you're primarily relying on internal measures, use customer feedback periodically to calibrate your performance.
Keep in mind that internal metrics are more prone to manipulation and may be more self-serving, depending upon how the data is collected, the scope, the qualifying window, repeat-call calculation definition, and subjectivity of the determination. Internal metrics are also subject to data integrity issues due to the difficulty of collecting and manually categorizing the data.
Download the webinar slides: Metrics For IT Help Desk & Customer Service Organizations
How many of your customers' issues are resolved on the first contact? It sounds like it should be easy to measure, however many companies have found it difficult to define first contact resolution, much less measure it consistently. Tactics to measure first contact resolution vary greatly from company to company. Our survey confirms this. While some companies are measuring first contact resolution, many are not and would like to.
Customers expect to bring a problem or question to your attention and have it resolved in a timely manner. Not all inquiries can be resolved immediately or on the first contact. However, advances in technology, increasing employee empowerment, and scrutinizing evaluation will increase the number that can.
80% first contact resolution performance sounds good. Yet with an 80 percent first contact resolution, 20 percent of customers require multiple contacts with your company to achieve resolution. An 80 percent first contact resolution means your customers average 1.2 contacts to resolve a question or issue. The 20 percent repeat contacts represent increased call volume and field visits, inflated operating expenses, and most importantly, dissatisfied customers. Dissatisfied customers are more likely to defect and more likely to tell others about their experiences.
First Contact Resolution (FCR) is a critical determinant of customer satisfaction, making FCR one of the more powerful customer care metrics. Improvement in FCR brings the best of both worlds—improvement in efficiency and effectiveness. You don't have to worry that you are sacrificing quality because you are reducing costs, or vice versa. When you improve FCR you're improving quality, reducing costs, and improving customer satisfaction, all at the same time.
Measuring First Contact Resolution is the first step towards improvement. Due to the nature of what is being measured—an outcome—it can be challenging. Our research identified four primary measures—three of which are internal approximations of First Contact Resolution, the fourth provides true customer feedback and perception. While each approach has its application, customer perception is king—the customer's evaluation is what matters most.
Download the webinar slides: Metrics For IT Help Desk & Customer Service Organizations
This customer service report shows SLA compliance over a period of time. Managing trends toward a higher goal can dramatically increase customer satisfaction.
Service level agreements can contain numerous service performance metrics with corresponding service level objectives. A common case in IT service management is a call center or service desk. Metrics commonly agreed to in these cases include:
Uptime is also a common metric, often used for data services such as shared hosting, virtual private servers and dedicated servers. Common agreements include percentage of network uptime, power uptime, number of scheduled maintenance windows, etc.
Many SLAs track to the Information Technology Infrastructure Library specifications when applied to IT services.
Download the webinar slides: Metrics For IT Help Desk & Customer Service Organizations
Newer Entires 1 ... 6 7 8 9 10 11 12 13 14 15 16 ... 27 Older Entries
