Service Failure

Service Failure
Author :
Publisher : AMACOM/American Management Association
Total Pages : 210
Release :
ISBN-10 : 9780814431993
ISBN-13 : 0814431992
Rating : 4/5 (992 Downloads)

Book Synopsis Service Failure by : Jeff Toister

Download or read book Service Failure written by Jeff Toister and published by AMACOM/American Management Association. This book was released on 2013 with total page 210 pages. Available in PDF, EPUB and Kindle. Book excerpt: What causes poor customer service? You might be surprised.


Service Failure Related Books

Service Failure
Language: en
Pages: 210
Authors: Jeff Toister
Categories: Business & Economics
Type: BOOK - Published: 2013 - Publisher: AMACOM/American Management Association

GET EBOOK

What causes poor customer service? You might be surprised.
Customer Evaluations of Service Failure and Recovery Encounters
Language: en
Pages: 287
Authors: Klaus Schöfer
Categories: Business & Economics
Type: BOOK - Published: 2003-01-10 - Publisher: diplom.de

GET EBOOK

Inhaltsangabe:Abstract: Although many firms may aspire to offer zero defects service, the possibility of service failures cannot be wholly eliminated simply bec
Leveraging Computer-Mediated Marketing Environments
Language: en
Pages: 492
Authors: Bowen, Gordon
Categories: Business & Economics
Type: BOOK - Published: 2019-01-25 - Publisher: IGI Global

GET EBOOK

Social media has redefined the way marketers communicate with their customers, giving consumers an advantage that they did not have previously. However, recent
Zero Fail
Language: en
Pages: 561
Authors: Carol Leonnig
Categories: Political Science
Type: BOOK - Published: 2021-05-18 - Publisher: Random House

GET EBOOK

NEW YORK TIMES BESTSELLER • “This is one of those books that will go down as the seminal work—the determinative work—in this field. . . . Terrifying.”
Site Reliability Engineering
Language: en
Pages: 552
Authors: Niall Richard Murphy
Categories:
Type: BOOK - Published: 2016-03-23 - Publisher: "O'Reilly Media, Inc."

GET EBOOK

The overwhelming majority of a software system’s lifespan is spent in use, not in design or implementation. So, why does conventional wisdom insist that softw