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"

Client Success

MetroHealth System Logo
  • 50% reduction in time to deploy Giva's change, incident, problem, asset management and knowledgebase modules
  • 60% reduction in the 5 year Total Cost of Ownership (TCO)
  • Saved at least 1 FTE due to lower ongoing administration
  • Saved 1 week per month due to easy to use reports
Athens Regional Health System Logo
  • Increased to 90% achievement in meeting service level agreements
  • 70% reduction in generating reports and admin; eliminated 35 hours/month
  • 50% faster to create/assign a service request
  • 60% increase in information captured during the initial phone call
  • 50% increase in the number of service requests created due to intuitive design
Santé Health Systems Logo
  • 80% increase in productivity by using Giva's dashboards and reports
  • 60% increase in meeting service level agreements
  • 50% increase in productivity by using Giva's integrated custom forms
  • 45% increase in the number of the calls logged due to Giva's intuitiveness and ease of use