Giva Blog
Help Desk, Customer Service, Cloud & Security Insights, with a Side of Altruism!

Save Money-Cloud IT Help Desk and Customer Service Software

As budgets are being set for 2009, your company is looking to save money. Due to budget constraints, the help desk and customer service software markets are really moving rapidly toward Software-as-a-Service (SaaS) to save a lot of money.

The Software-as-a-Service (SaaS) approach can significantly lower your annual costs and provide a better product.  SaaS can significantly decrease capital, deployment, labor, operations, network, training, support and intangible costs.

According to Gartner Group, a global IT research firm, the annual cost to own and manage software applications can be up to four times the cost of the initial purchase. As a result, companies end up spending more than 75% of their total IT budget just on maintaining and running existing systems and software infrastructure.1 The number of software applications that a company may need are infinite. The resources to operate these applications however are finite.

 

1 Timothy Chou, The End of Software, SAMS Publishing, 2005, page 6

 

Here is a great White Paper on Saving Money with SaaS. See https://www.givainc.com/white-papers/Save-Money-with-Software-as-a-Service-SaaS.htm

Calculate ROI-Knowledge Bases

Now let’s examine how we might calculate a monthly return. You may want to modify these to focus on quarterly or annual impacts. When doing so, it is recommended that you adjust your forecasted improvements based on your expectations of the adoption rate and implementation plans.

Reducing the Average Call Time on first contact.
Forecasted improvement: 1 minute
Savings = (Cases per month * Cost per case) * (Improvement / Talk Time for first contact)
Savings = (5000 * $40) * (1/12)
Savings = $16,667 per month

Increasing the First Call Resolution Rate.
Forecasted improvement: 20%
Savings = (Cases per month * Improvement) * ((Escalated Talk Time – Talk Time for first contact) / Talk Time for first contact) * Cost per call
Savings = (5000 * 20%) * ((18 – 12) / 12) * $40
Savings = $20,000 per month

Reducing the Escalation Rate.
Forecasted improvement: 5%
Savings = (Cases per month * Improvement) * (Cost per escalated case – Cost per case)
Savings = (5000 * 5%) * ($150.00 - $40)
Savings = $27,500 per month

Reducing the time required for a new support professional to become productive.
Forecasted improvement: 3 weeks
Savings = ((Improvement * Number of new hirers per year) * (Average burdened cost of a support professional / weeks per year)) / months per year
Savings = ((3 * 8) *($70,000 / 52)) / 12
Savings = $2,692 per month

Redirecting repeat calls to Self-Service.
Forecasted improvement: 10% of current cases redirected to self-service
Savings = (Improvement * Cases per month) * Cost per case
Savings = (10% * 5000) * $40
Savings = $20,000 per month

Developing an ROI for Knowledge Management in your support center depends on your current state, your implementation plans, your team, and your customers. The need for a formal ROI depends heavily on the senior management responsible for the support center. Some companies have minimized this focus because of an existing strong support from senior managers for Knowledge Management. Industry research groups such as Gartner, Forrester, Yankee, and others have well documented the value of Knowledge Management in the support center.

 

Here are some great White Papers on this topic  https://www.givainc.com/white-papers/index.htm

Source: Joslin & Associates

ROI-Knowledge Bases for IT Help Desks

Once you understand your current state, you must make reasonable forecasts regarding the impact Knowledge Management will have on your organization. The Knowledge Management vendors may offer to assist you with developing your ROI. Some vendors provide well-tuned and complex models. To simplify things, let’s examine how some of the benefits can actually be converted to dollars. Before we begin, we need to make some assumptions about the support center.

While these numbers may vary in your organization, the assumptions provide an example for this discussion.

Assumptions:

  1. Number of cases per month is 5000
  2. Average cost per case is $40.00.
  3. Average cost per escalated case is $150.00
  4. Average burdened cost for a support professional is $70,000.00
  5. Average talk time for first contact is 12 minutes
  6. Average talk time for escalated calls 18 minutes
  7. Time require for a new hire to be productive is 6 weeks
  8. Number of new hires per year 8
  9. First call resolution rate is 40%

Here are some great White Papers on this topic  https://www.givainc.com/white-papers/index.htm

Source: Joslin & Associates

Knowledgebase ROI for Customer Service

While most support center managers are able to forecast the costs, they struggle to forecast the savings. This is partially because a number of the benefits of Knowledge Management are defined as soft dollars. Companies struggle to put a value on customer satisfaction, job satisfaction, quality service, or even the intellectual capital that is captured into the knowledge base. Another reason companies struggle is because they lack a benchmark. Before you can forecast an improvement, you have to know where you are.

 

If you would like a white paper on this topic please download it at:

https://www.givainc.com/white-papers/index.htm

Source: Joslin & Associates

Is this interesting information? Please share your thoughts. Thank you!

What is the ROI of a Knowledgebase?

Knowledge Management is an ongoing process of capturing, optimizing, and delivering information. It is not a one-time purchase of a new support center tool. Therefore to calculate the Return On Investment, you need to evaluate the cost of implementation and the cost of management. The cost of implementation relates to the initial purchase of software, hardware, communications, training, and services required for the knowledge base to be placed into production for daily use. The cost of management relates to the ongoing costs of maintaining the knowledge base and the infrastructure that was implemented.

If you would like a white paper on this topic please download it at:

https://www.givainc.com/white-papers/index.htm

Source: Joslin & Associates

Is this interesting information? Please share your thoughts. Thank you!

Service Level Management- IT Help Desk/Customer Service

The effort to create a Service Level Management System is very significant. Organizations that have a system in place have higher customer and employee satisfaction ratings. After all, when every case is considered severity level one and every day is a fire drill, it is hard to enjoy your job for very long. That is why the turnover in support organizations where Service Management Systems are in place is lower than organizations where they are not. So, with higher customer and employee satisfaction, lower turnover, greater productivity and reduced cost, why would you not want to have a Service Management System guiding your organization?

 

Here is a great White Paper on Implementing Service Level Agreements. See https://www.givainc.com/white-papers/index.htm

Select Implementing Service Level Agreements: "The Critical Element in Service Delivery"

Customer Satisfaction Surveys-IT Help Desks

Incident Surveys

Incident surveys are surveys sent to the customer after each case is closed. The advantage to this is that you can capture perceptions immediately and you can link the feedback to both the Service Group and to the Assignee. This is extremely valuable information because both rewards and training can be tailor-made based on the results. The disadvantage is that customers will get usually one survey a week and they might not respond with as great regularity. However, the advantages outweigh the disadvantages. Incident surveys are preferable to periodic surveys.

 

Here is an example of an Incident Survey:

It is short and to the point. Always ask for feedback in a free form field to encourage customers to openly share their thoughts. Customers will tell you things that you will never hear from anybody else. This unfiltered feedback is extremely valuable to help you improve customer service. Also, always ask if you would like a manager to call you. When you get a survey like this, it tells you the perspective of the customer service organization. When the customer reads this they will think, "Wow, these guys actually would have a manager call me, if I ask them to." Many will not request a call.  Those that request a call will tell you much more then you will ever get from a written survey. Are you ready for these gold nuggets from customer who care enough to want to have a call?  Ask probing questions and "peel the onion". See through any emotion and find the "signal" in all the surrounding "noise" and you are on to becoming a master in learning how to get actionable feedback which can be used to effect change in your organization.

Incident_Customer_Survey

 

Here is a great White Paper on Implementing Service Level Agreements. See https://www.givainc.com/white-papers/index.htm

Select Implementing Service Level Agreements: "The Critical Element in Service Delivery"

How Frequently to Survey IT Users?

Periodic Surveys

Quarterly or annually a survey should be sent to all customers asking them their general opinions of the support they receive. You cannot ask for specific information when you do periodic surveys because customers only remember their last one or two incidents. Periodic surveys are not a good measurement of how your organization did for the year. Another limitation of periodic surveys is that survey responses will not be specific to each Support Group or person assigned the case. Customers do not really know, or care, what group handles their request.

Here is a great White Paper on Implementing Service Level Agreements. See https://www.givainc.com/white-papers/index.htm

Select Implementing Service Level Agreements: "The Critical Element in Service Delivery"

Service Level Manangement and Satisfaction Surveys

Checks and Balances

There is a tendency when first starting service level management to focus in on the response performance. It is easy to make the numbers look good. All you have to do is close a case within the time specified without doing anything. While this makes the numbers look good, in the end you will have customers upset. Customers do not really care about the numbers. They only want their issues taken care of to their satisfaction.

Customer Satisfaction Surveys are one way to provide checks and balances to the empirical numbers of SLA compliance reports. Another way to make sure customers are taken care of is to have a policy for re-opening a case if the customer calls in to say they are dissatisfied. You should then have a report that shows re-opened cases. Management should use this for continued training.

Here is an example of a good Customer Satisfaction Survey Report:

Full_Customer_satisfaction_Report

 

Here is a great White Paper on Implementing Service Level Agreements. See https://www.givainc.com/white-papers/index.htm

Select Implementing Service Level Agreements: "The Critical Element in Service Delivery"

Service Level Agreements-SLA Compliance Trends Reports

This report shows SLA compliance over a period of time. Managing trends toward a higher goal can dramatically increase customer satisfaction. This SLA Compliance Trends Report should be part of your standard reports that you study every week.

 

Example SLA Compliance Trends Report

 

SLACOMPLIANCETRENDS

 

Newer Entires     1   ...   26   27   28   29   30   31   32   33   34     Older Entries