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

Service Level Agreements-SLA Compliance Reports

Measuring Success

Success of service level management can only be measured by reporting on what percentages of cases by Severity Level were resolved within the goals of the SLA. The reason that you want to measure each Severity Level is that it is absolutely critical to resolve high severity level cases consistently within the SLA. However, sometimes lower severity level cases can fall outside the goals. In other words, we would like to say that we resolve 100% of all Severity Level 1 cases and 90% of Severity Level 4 cases within the times stated in the SLA. Customers will appreciate the process more when they know that if they are really in trouble, there will be resources there to help them.

 

Example Service Level Agreement Compliance Report

SLACOMPLIANCE

 

See Dashboard Reports at https://www.givainc.com/help-desk-dashboard-charts.htm 

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"

Implementing Service Level Agreements-IT Help Desk

Need help in implementing your Service Level Agreements?

1) Pre-SLA. Before you announce the SLA, practice as if you have an SLA. This includes the following:

a. training the Support Center staff,

b. monitoring response time to ensure SLA compliance,

c. resolving cases in accordance with the SLA,

d. setting customer expectations,

e. managing the work flow within the Support Center and between the second level.

2) Training the rest of the department.

a) Weekly meetings. For the first month it is beneficial to meet regularly to find ways to improve communications and workflow, review Cycle Time Reports and exception reports.

b) Service Group Feedback. Ask other service groups to review their cases for the proper Severity Levels. If they find discrepancies, ask them to provide a list of case types and the appropriate Severity Levels. This will be the basis for Support Center training and documentation.

 

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"

Benefits of Service Level Agreements for Service Desk

Every day each one of us experiences the setting of expectations. The following are all examples of setting expectations: setting an appointment time, asking for a delivery time and asking for the wait time at a restaurant or car repair shop. Why should your customer service/call center or help desk organization be any different?

The benefits of an SLA are many for the Internal IT help desk or service desk:

· Improves customer service. You will find that cycle times (time to resolve cases) dramatically decrease.

· Facilitates communication. The Support Center staff will be able to set customer expectations in two ways. First, they can refer to the SLA document for definitions on how priorities are set and the maximum time the support organization has to resolve the case. Secondly, they can refer to periodic performance reports to inform customers how the support organization is actually performing. Average time to resolve is usually much less than the maximum time goal.

· Negotiated and mutually accepted. Since internal customers and the support center jointly created the SLA all customers will more easily accept the SLA.

· Documents agreements. With the SLA posted to your Intranet or in customer handouts, it becomes an “official” agreement.

· Defines procedures. Procedures should be defined and followed by both the service groups and customers. When there is a question or disagreement, the SLA can be used as a written reference.

· Sets standards for customer service. This is a powerful tool. It says “Mr./Ms. Customer, this is how I am going to provide support to you and this is what you must do in order to receive my support. I am ready to be measured on how I do and I will provide everyone with a report on my performance.”

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"

Needs Assessment Tool-Buying Customer Service Software

Giva radically reduces the complexity of the Software-as-a-Service (SaaS) buying process by offering a vendor-independent Needs Assessment Tool that allows companies to make a more rigorous and objective comparison of vendors based upon a prioritized list of feature requirements when buying customer service, call center and IT help desk software.

Customer Service departments, Call Centers and IT Help Desk professionals looking to purchase IT help desk software or customer service software encounter a myriad of problems and obstacles in the purchase process.  Giva is offering its new Needs Assessment Tool on a complimentary basis.

Industry Leading Help Desk & Customer Service Software

This vendor-independent tool allows evaluation teams and senior executives making important business decisions to approach the purchase of software in a much more rigorous and analytical manner. The Tool provides the information essential to negotiate a services contract, avoiding the difficult struggle to understand the differences between software products and assess vague claims.

Here is a quote from a company that used the Excel Tool:

"At Patient Care Technology Systems, we used Giva's Tool to document our requirements across multiple work groups to generate a single prioritized list. We shared this list with a number of vendors and were able to make a more rigorous and defendable vendor recommendation to our senior team," said Jim Kline, Vice President of Client Services, Patient Care Technology Systems. "The Needs Assessment Tool provided the objective criteria we needed to evaluate several vendors on an apples-to-apples basis."

Patient Care Technology Systems used this tool in 2005 to sort through their requirements and select a vendor. They have been a very happy Giva customer for three years. Here is a customer case study. A great deal of their satisfaction is due to the fact that Giva is a great fit for their requirements. Do your homework now to document your requirements.  See https://www.givainc.com/case-study/customer-service-pcts.htm for the medical industry success case.

This Giva Needs Assessment Tool can be a starting place and the single document to drive cross-functional consensus of all the departments involved in the purchase of customer service, call center or IT help desk software. We listened to many companies struggle with this process and they asked us for our help. This vendor-independent Tool really helps management teams make an objective comparison of vendors based upon their prioritized list of requirements.

See the following link for free Access to the Needs Assessment Tool at:  https://www.givainc.com/free-needs-assessment/index.htm

Creating Service Level Agreements (SLAs)-Part 2

1) Escalation procedures. State the escalation path and time for each severity level.

2) Telephone, Web and Email response times. For example: Phone requests will be answered in less than 20 seconds, Web requests within 30 seconds and email within four hours.

3) First contact resolution by the Support Center. For example: The Support Center will resolve at least 70% of all cases it receives.

4) Reporting methods.

a) Weekly management reports on the Web

b) Monthly performance metrics on the Web

c) Quarterly Customer Satisfaction Surveys results on the Web

5) SLA contract period.

a) When the current draft is effective

b) When it will be reviewed?

c) How to request changes

6) Examples of cases by severity level and case type.

7) Sample of the customer satisfaction survey questions.

 

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"

Definition of Service Level Agreements (SLAs) for IT Help Desk

Here is more on getting your SLA written.

1) Definition of terms. Do not assume that everyone will know what you are talking about. You need to define terms to the lowest common level. Be as specific as possible.

2) Service delivery elements

a) Service coverage times. State clearly what business hours are supported and what is supported after hours. Failure to do this will mean you can be called at any time of the night for the most minor of problems or requests. Be sure to consider the various time zones you cover. Keep consistent and list the time zone you are in (e.g., 7AM – 7PM EST).

b) Environment(s) included. What do you cover? If you only support standard hardware and software, be sure to state it here.

c) Environments excluded. If the Support Center will take cases for non-standard hardware and will charge back costs to the customer, then list that here.

d) Specific applications and network services coverage. List specific applications by name, the times they are supported and the times they are not supported. If there are maintenance windows for databases and servers when they will not be available, then make sure to list these windows.

e) Methods for requesting service. For example, for all level 1 and 2 cases the request for service may be via the phone. For example, for level 3 and 4 cases the request for service shall only be via the Web.

f) Customer responsibilities. Some examples are: How to submit a request, what standards are supported, and when customers should be available for the technician.

g) Service tracking and reporting procedures. Some examples are: IT will log 100% of all requests, phone calls will be randomly recorded for quality and performance metrics will be posted on the web.

 

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"

Creating Service Level Agreements (SLAs) for Customer Service

Creating a rough draft

There are several components to an SLA. It is important that the language is familiar to your environment. Use a straw man to introduce the concept to your organization. This will help the rest of the project team understand the complexity and importance. The following is an example of the categories that should be included in your SLA. However, remember that it must be clear, well written, and easy to read and not very long.

1) Introduction

a) Purpose of the SLA

b) Mission of IT (This is not just between the Support Center and customers)

c) Customers covered under the SLA

d) Locations

e) Owner of the SLA document and communications path

f) Services covered. This is only a high level statement.

2) Service Goal.

a) Overall goal. Example: Resolve 100% of all severity level 1 and 2 cases in the timeframe specified. This is the first place that you are making a statement about what is important. You cannot be a success treating all cases equally. Level 1 and 2 are high severity level cases that directly impact the productivity of a number of customers/locations of the company. You must make sure these get done on time. Getting the others done on time is a bonus.

b) Specific goals. List the severity levels and the time the case should be responded to and the time it should be resolved.

 

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"

Measuring Service Level Agreements- Mutual Expectations

Service Level Management is a formal way for setting customer expectations BEFORE the customer has the need to request service. It is a methodology for introducing and implementing reasonable expectations between you and the customers you support. These are most often contained in a document called a Service Level Agreement (SLA). The SLA establishes a two-way accountability for service, which is negotiated and mutually agreed upon. It is really a contract that documents operational and interpersonal relationships, establishes mutual expectations, and provides a standard to measure performance.

Without SLAs in place, you are effectively telling your customers that you will provide support to them, at any time, under any conditions, without any limitations to the systems and services they have. However, this is not the worst part. The worst part is that you cannot possibly ever meet your customers’ service expectations because every customer will have a different expectation and that expectation will change every time they call.

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"

TCO-Call Center/Customer Service Cloud Software

The other day I talked about the TCO of Call Center/Customer Service & Help Desk Software-Acquisition Costs. The following is a listing of the important lifetime costs that you want to make sure you carefully quantify. Ask the vendors that you are considering to put together an analysis to show you what the TCO will be of their solution over 3 years. That is a reasonable time horizon. Most traditional software vendors will actually make you repurchase the entire application every 3 years or so. It is important that you understand this. Carefully read the software license agreements for this important detail. Annual Software Maintenance Agreements will only buy you incremental upgrades with moderate feature enhancements and bug fixes. They never include new User Interfaces and rewrites which are major product releases. How else do you think the traditional software industry has created so many billionaires and multimillionaires. Customers enjoying the economics of the SaaS model are saying the party is over. Are you taking advantage of this sea change or would you rather help your company pay for another software billionaire's yacht?

Here are the Lifetime Costs to consider:

Support Costs:

Cost for Support:

Call Tracking System and add-ons?

Database Support?

Day-to-Day Administration:

Average time to set up a security group?

Average time to add, change or delete users from their system accounts?

Average time to make changes to pull-down lists?

Can I make changes to the system during business hours?

Future Customization:

How much is involved and how long does it take to do a detailed design for changes?

Does any of the following require consulting services and average time to:

Add labeling to a view?

Resize a field?

Move a field?

Add a form?

Add a button?

Add a Menu?

Add a field to the database table?

Add a view?

Average time to modify views for display on different type platforms and monitor resolutions?

Workflow changes:

Average time to modify the way certain calls notify the service technician?

Does this require consulting programming costs or can it be done in house?

Average time to change the way certain calls are routed?

Average time to develop a feature that automatically creates multiple tickets (parent/child and predecessor/successor) based on workflow logic that is maintained by the service groups affected?

Average time to design, write, and debug triggers and stored procedures?

Average time to design, write and debug an application program integration (API) utility?

Average time to document changes made to the system and where are these stored?

Average time required for testing changes?

Are there utilities to help with the testing?

Once changes are made, average time for end users to review and gain acceptance?

Average time to move the changed functions from the development server to the production server?

Upgrades:

Are upgrades backward compatible?

Average time to test, and implement upgrades?

Do upgrades require consulting time? If so, what is the average cost?

People Costs:

Is the system reliable? How much downtime is anticipated a year?

Average time for a user to become proficient?

Ease of client installation?

Creating New Applications:

Do you have templates or down-loadable applications outside the help desk area?

If so, how much do they cost?

If not, how long does it take to create a simple application?

Network Costs:

Average time to log on and load the client program when close to server and from a distance?

What is the average length of time for a query to return 1000 calls when close to server and from a distance?

Average time to submit a call when close to server and from a distance?

If we go to multiple servers, what is the average cost for each server (Application, hardware, software, etc.)?

Will this take consulting to implement?

Do you integrate with network monitoring applications such as LanDESK or SMS?

What is the cost to integrate with a network monitoring application?

Future Application Integrations:

Do you have an Asset Management (AM) application? Cost to integrate?

Do you integrate with remote control/access applications? Cost to integrate?

Do you integrate with Autodiscovery applications to inventory software on the desktops? Cost to integrate?

Do you have a Change Management (CM) application? Cost to integrate?

Do you have a knowledge management application? Cost to integrate?

Do you integrate with enterprise financials such as SAP? Cost to integrate?

Do you integrate with Report Writing packages? Cost to integrate?

Do you integrate with two-way paging applications? Cost to integrate?

Do you integrate with palm computers such as Palm Pilot? Cost to integrate?

TCO Help Desk Cloud Software-Acquisition Costs

It is important to look beyond the "Sticker Price" for your Call Center/Customer Service or Help Desk software!! Your CIO or VP of Customer Service is very interested in the one time acquisition costs as well as the recurring costs which are also called lifetime costs.  The Software-as-a-Service (SaaS) industry is taking significant market share away from the traditional software vendors for good reasons. Many of the reasons are just simple economics. You will not have all of the recurring costs with the SaaS approach as you will with purchasing and deploying traditional software. The initial acquisition costs are also an order of magnitude lower with a SaaS approach.

Here is a list of Acquisition costs to that you should be considering.

Acquisition Costs

Application Cost:

What is the basic cost of the server software?

Licenses:

What is the cost for user licenses?

What is cost for customer licenses?

Is there a charge for creating and viewing records?

Up-front Customization:

If lacking necessary features, what is the average number of hours to customize the tracking system before it can be used? (Small, medium and large changes)

Consulting cost for customizing?

Server Requirements:

What are requirements?

Will we need a new server or an upgrade?

Cost for server hardware?

What databases are supported?

Will we need a new database or an upgrade?

Cost for database?

Operating system software requirements?

Cost for upgrade or new operating system?

What server applications are necessary for network connectivity?

Cost for network software?

Web Implementation:

Cost of Web application to allow customer submits and queries and users to close calls?

Web server hardware requirements?

Cost of Web server or server upgrade?

Operating system software requirements?

Cost for upgrade or new operating system?

What server applications are necessary for network connectivity?

Cost for network software?

Cost of licenses to have any customers use the Web tool.

Report Writer:

Does application have a built-in report writer so that graphical results can be distributed?

Average cost of report writer application?

Average cost to integrate with report tool?

Is there a real-time view of the information?

Development Environment:

Cost for a development server application?

Cost for admin licenses?

Cost of user license?

Cost of customer licenses?

Cost of operating system software?

Cost of networking software?

Cost of database and license?

Training Costs:

Cost to train administrators?

Cost to train uses?

Is there multiple training locations for my global company?

What are there the training options available for all the different needs I might have?

 

For a good White Paper on the topic, please see https://www.givainc.com/white-papers/index.htm and select

Looking Beyond Sticker Price: "What It Really Costs to Operate a Call Tracking System"

 

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