scispace - formally typeset
Search or ask a question
Topic

Service level objective

About: Service level objective is a research topic. Over the lifetime, 7894 publications have been published within this topic receiving 218701 citations.


Papers
More filters
Journal ArticleDOI
TL;DR: In this article, the authors explore and empirically investigate the characteristics and contingencies of service delivery system design, and show how this contingency has implications for the extents of employee skills, employee discretion, task routineness, automation, and for front office (FO) and back office (BO) configurations.
Abstract: Purpose – The aim of this paper is to explore and empirically investigate the characteristics and contingencies of service delivery system design.Design/methodology/approach – Informed by the service strategy triad, a single embedded case study was designed to explore empirical data on four target markets, four service concepts, and on the design characteristics of the corresponding four service delivery systems. Data were collected in a market‐leading organisation in the business‐to‐business sector within the power industry. The service delivery systems comprise processes that sell electricity contracts and processes that bill against those contracts.Findings – First, the findings indicate what design characteristics are contingent upon the degree of customisation of the service concept. The authors show how this contingency has implications for the extents of employee skills, employee discretion, task routineness, automation, and for front office (FO)‐back office (BO) configurations. Second, the authors...

112 citations

Patent
Igor Sedukhin1
19 May 2003
TL;DR: A web service broker (200) as discussed by the authors provides an interface between an enterprise and at least one of a service client and a service provider, the service client discovering web services on a service registry and using corresponding web services from the service provider.
Abstract: A web service broker (200) method comprises providing an interface between an enterprise and at least one of a service client and a service provider, the service client discovering web services on a service registry (12) and using corresponding web services from the service provider, communicating between the enterprise and the at least one of the service client and the service provider and performing at least one of a) converting information from/to the enterprise to a form appropriate for the at least one of the service client and the service provider and b) converting information from/to the at least one of the service client and the service provider to a form appropriate for the enterprise.

111 citations

Journal ArticleDOI
TL;DR: In this article, the authors propose that satisfaction with service recovery should be based on customers' expectations of the recovery encounter, which would be shaped by their expectations of "non-failed" encounters.
Abstract: Purpose – The purpose of this paper is to extend thinking on service recovery processes and satisfaction with service recovery, using multi‐dimensional consumer outcomes. The objective of the work was to propose that satisfaction with service recovery should be based on customers' expectations of the recovery encounter, which would be shaped by their expectations of “non‐failed” encounters.Design/methodology/approach – The paper adopts a theoretical approach. Using the existing service recovery literature as well as the traditional services literature, the conceptual framework and associated research propositions are developed.Findings – The proposed framework suggests that service recovery is a service encounter it its own right. The effectiveness of recovery encounters will be based on how encounters operate relative to customer expectations and experiences with regard to the recovery activity.Research limitations/implications – The research propositions and proposed framework need further empirical inv...

111 citations

Patent
17 Aug 2001
TL;DR: In this article, a service may be comprehensively managed by using collected quality and/or performance data from the network to verify that the network is providing a level of service expected by a client.
Abstract: Embodiments of methods, systems, and computer program products are provided for managing a service For example, service quality and/or performance requirements may be obtained from a client and quality and/or performance data may be collected from the network The collected quality and/or performance data may then be compared with the service quality and/or performance requirements to determine if the network quality and/or performance requirements are satisfied Thus, a service may be comprehensively managed by using collected quality and/or performance data from the network to verify that the network is providing a level of service expected by a client

111 citations

Journal ArticleDOI
TL;DR: In this article, the authors provide an analysis of the real estate brokerage industry for the purposes of identifying the determinants of service quality, the level of services quality, and possible service quality.
Abstract: This study provides an analysis of the real estate brokerage industry for the purposes of identifying the determinants of service quality, the level of service quality, and possible service quality...

111 citations


Network Information
Related Topics (5)
Competitive advantage
46.6K papers, 1.5M citations
84% related
Information system
107.5K papers, 1.8M citations
82% related
Organizational learning
32.6K papers, 1.6M citations
82% related
Empirical research
51.3K papers, 1.9M citations
82% related
The Internet
213.2K papers, 3.8M citations
82% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
202318
202259
202125
202040
201938
201843