Show simple item record

dc.contributor.advisorSanjay Sarma and Stephen C. Graves.en_US
dc.contributor.authorElliott, Grant Stephenen_US
dc.contributor.otherLeaders for Manufacturing Program.en_US
dc.date.accessioned2009-12-10T19:11:49Z
dc.date.available2009-12-10T19:11:49Z
dc.date.copyright2009en_US
dc.date.issued2009en_US
dc.identifier.urihttp://hdl.handle.net/1721.1/50095
dc.descriptionThesis (M.B.A.)--Massachusetts Institute of Technology, Sloan School of Management; and, (S.M.)--Massachusetts Institute of Technology, Dept. of Mechanical Engineering; in conjunction with the Leaders for Manufacturing Program at MIT, 2009.en_US
dc.descriptionIncludes bibliographical references (p. 50).en_US
dc.description.abstractWhen a customer calls or e-mails customer service, a customer service agent will diagnose the issue, render a solution, and then wrap-up the call or e-mail. For many customer service departments, this wrap-up process requires the agent to classify the reason the customer contacted customer service. Typically, this classification is done by assigning a code that describes the reason for a contact. Additionally, if a contact requires a concession, the agent will classify the reason the customer requires a concession, and select an appropriate code. These codes are used by the various business teams within the company to identify and correct failures in their processes. Therefore, these codes should drive down to the root cause for a contact or concession to allow for efficient correction. Possessing codes that do not clearly identify the root cause for a contact are of little or no use for the company. Additionally, the codes must be developed in such a way that they can be accurately chosen by either the agent or the customer. Having agents select the wrong code not only obscures the true cause for a contact, but also creates additional work due to the process involved in determining the correct code. This thesis looks at the challenges inherent in developing a list of codes that both provides clear insight into the root cause for customer contacts, and can be accurately selected by the customer service agent or the customer.en_US
dc.description.statementofresponsibilityby Grant Stephen Elliott.en_US
dc.format.extent50 p.en_US
dc.language.isoengen_US
dc.publisherMassachusetts Institute of Technologyen_US
dc.rightsM.I.T. theses are protected by copyright. They may be viewed from this source for any purpose, but reproduction or distribution in any format is prohibited without written permission. See provided URL for inquiries about permission.en_US
dc.rights.urihttp://dspace.mit.edu/handle/1721.1/7582en_US
dc.subjectSloan School of Management.en_US
dc.subjectMechanical Engineering.en_US
dc.subjectLeaders for Manufacturing Program.en_US
dc.titleImproving customer service contact root-cause analysisen_US
dc.typeThesisen_US
dc.description.degreeS.M.en_US
dc.description.degreeM.B.A.en_US
dc.contributor.departmentLeaders for Manufacturing Program at MITen_US
dc.contributor.departmentMassachusetts Institute of Technology. Department of Mechanical Engineering
dc.contributor.departmentSloan School of Management
dc.identifier.oclc458584790en_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record