{"id":251782,"date":"2020-03-01T00:00:00","date_gmt":"2020-03-01T05:00:00","guid":{"rendered":"https:\/\/www.servicexrg.com\/blog\/do-you-need-slas\/"},"modified":"2022-06-14T17:27:32","modified_gmt":"2022-06-14T21:27:32","slug":"do-you-need-slas","status":"publish","type":"post","link":"https:\/\/www.servicexrg.com\/blog\/do-you-need-slas\/","title":{"rendered":"Do You Need SLAs?"},"content":{"rendered":"
\n
\n
\n
\n

Every technical support organization should have service level guidelines as a basis for determining how to prioritize cases and allocate resources and for managing consistent expectations with customers. Introducing service level agreements with committed performance levels is only required when customers demand them, or it is necessary for competitive differentiation.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n
\n
\n

SLA Types<\/h2>\n

There are three primary types of service level agreements used within the technology industry.\u00a0 The primary elements of the agreements include the committed or targeted level of performance, the conditions and definitions for how performance will be measured, and the provisions by which performance commitments will be enforced.\u00a0 Typical technology service level agreement types include:<\/p>\n

Agreements<\/h4>\n

Agreements state a committed level of service and the terms by which this service will be provided.\u00a0 Service level agreements are typically enforced by some form of penalty when promised performance levels are not met.<\/p>\n

Level of Performance<\/strong>: Performance commitments.<\/p>\n

Conditions:<\/strong>\u00a0Stringent definitions and conditions for determining SLA non-compliance.<\/p>\n

Enforcement:<\/strong>\u00a0Typically a penalty in the form of a rebate of service fees.<\/p>\n

Firm Targets<\/h4>\n

Service level targets express a target level of performance for a particular service.\u00a0 Targets are expressed in specific terms however there is no commitment or guarantee of performance or penalty imposed if not met.<\/p>\n

Level of Performance<\/strong>: Specific performance targets.<\/p>\n

Conditions:<\/strong>\u00a0May vary by customer type, support program level or issue severity.<\/p>\n

Enforcement:<\/strong>\u00a0None.<\/p>\n

Soft Targets<\/h4>\n

Service level targets may also be expressed in soft terms where a level of performance is suggested for some but not all situations.\u00a0 When soft service level targets are missed there are no penalties.<\/p>\n

Level of Performance:\u00a0<\/strong>Performance ranges.<\/p>\n

Conditions:\u00a0<\/strong>May vary by customer type, support program level or issue severity.<\/p>\n

Enforcement:\u00a0<\/strong>None.<\/p>\n

Why Use SLAs<\/h2>\n

Service level statements are used for a variety of reasons, most notably to establish differentiation from direct competitors or within a service offering to distinguish between program levels and tiers.\u00a0 In some instances, customers will demand service level agreements as a prerequisite for doing business.\u00a0 In all cases SLAs are effective for setting and managing customer expectations.\u00a0 Well defined performance SLAs can prescribe how quickly to respond to issues, which issues to work on first, and who to get involved with issue resolution.<\/p>\n

    \n
  • Set Customer Expectations<\/li>\n
  • Competitive Differentiation<\/li>\n
  • Service Tier Differentiation (within a Portfolio)<\/li>\n
  • Prioritization and Resource Allocation<\/li>\n<\/ul>\n

    Do You Need SLAs?<\/h2>\n

    Every technical support organization should have service level guidelines as a basis for determining how to prioritize cases and allocate resources and for managing consistent expectations with customers. Introducing service level agreements with committed performance levels is only required when customers demand them or it is necessary for competitive differentiation.<\/p>\n

      \n
    • Do your customers expect them?<\/li>\n
    • Do your competitors provide them?<\/li>\n<\/ul>\n

      If the response to either question is \u201cyes\u201d then you should be offering SLAs.<\/strong><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

      Every technical support organization should have service level guidelines as a basis for determining how to prioritize cases and allocate resources and for managing consistent expectations with customers. Introducing service …<\/p>\n","protected":false},"author":4,"featured_media":251783,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","footnotes":"","_wp_rev_ctl_limit":""},"categories":[35,46,51,11],"tags":[89,125,98,63,75],"acf":[],"_links":{"self":[{"href":"https:\/\/www.servicexrg.com\/wp-json\/wp\/v2\/posts\/251782"}],"collection":[{"href":"https:\/\/www.servicexrg.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.servicexrg.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.servicexrg.com\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.servicexrg.com\/wp-json\/wp\/v2\/comments?post=251782"}],"version-history":[{"count":5,"href":"https:\/\/www.servicexrg.com\/wp-json\/wp\/v2\/posts\/251782\/revisions"}],"predecessor-version":[{"id":252992,"href":"https:\/\/www.servicexrg.com\/wp-json\/wp\/v2\/posts\/251782\/revisions\/252992"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.servicexrg.com\/wp-json\/wp\/v2\/media\/251783"}],"wp:attachment":[{"href":"https:\/\/www.servicexrg.com\/wp-json\/wp\/v2\/media?parent=251782"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.servicexrg.com\/wp-json\/wp\/v2\/categories?post=251782"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.servicexrg.com\/wp-json\/wp\/v2\/tags?post=251782"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}