Respond and Resolve-Service Level Agreements


How will you prioritize the blizzard of requests from employees or customers? Do your best to prioritize requests based upon their impact to revenue generation.

Respond and resolve times will properly set expectations. See Giva whitepaper on SLAs:

This whitepaper teaches you how to prepare your customers for SLAs, how to write an SLA and how to get buy-in from customers/employees. An SLA is really an agreement between the support organization and your customers.

Respond and resolve times should be associated with each severity level.

Downtime from major outages or product failures, also need to measure the impact in terms of # of customers and quantify the # of hours of customers not productive. Giva Tsunami ticket report will show the number of hours and how many people affected.


Download the webinar slides:  Metrics For IT Help Desk & Customer Service Organizations

Click for IT Help Desk Reports, KPIs & Metrics examples

Click for Customer Service Reports, KPIs & Metrics examples

Client Success

  • 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
  • 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
  • 80% increase in productivity by using Giva's dashboards and reports
  • 60% increase in meeting service level agreements
  • 45% increase in the number of the calls logged due to Giva's intuitiveness and ease of use
  • 50% increase in productivity by using Giva's integrated custom forms