Process completeness: Strategies for aligning service systems with customers' service needs
Increasingly, customers are expecting more and better service. As such, enterprises need guidelines and frameworks for addressing these expanding requirements. The concept of process completeness helps us to consider service from the customer's viewpoint; arguably, the only perspective to take. Process completeness is achieved when a firm's service delivery system matches the typical customer's breadth of expectations. While customers think in sets of services (e.g., I need a flight, a hotel, airport parking, wireless Internet), firms think in terms of single services (e.g., we can provide a flight). There are four basic service systems: (1) transaction--execute a basic request and nothing else, (2) process--handling all firm-related service requests through one touch point, (3) alliance--handling service requests through a single touch point via stitching together a static firm-selected alliance of service partners, and (4) agility--handling service requests through a single touch point via stitching together a dynamic customer-selected alliance of service partners. In addition to exploring the four service systems, this article guides executives regarding the selection and implementation of the appropriate service strategy that meets their typical customer's process completeness expectations.
If you experience problems downloading a file, check if you have the proper application to view it first. In case of further problems read the IDEAS help page. Note that these files are not on the IDEAS site. Please be patient as the files may be large.
As the access to this document is restricted, you may want to look for a different version under "Related research" (further below) or search for a different version of it.
When requesting a correction, please mention this item's handle: RePEc:eee:bushor:v:52:y:2009:i:4:p:367-376. See general information about how to correct material in RePEc.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: (Zhang, Lei)
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
If references are entirely missing, you can add them using this form.
If the full references list an item that is present in RePEc, but the system did not link to it, you can help with this form.
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your profile, as there may be some citations waiting for confirmation.
Please note that corrections may take a couple of weeks to filter through the various RePEc services.