It appears you don't have support to open PDFs in this web browser. To view this file, Open with your PDF reader
Abstract
An important aspect of the emerging user care discourse is the apologies offered by companies. Previous research has focused on public apologies; however, there has been little focus on the users’ comments in response to apologies. This case study aimed to investigate (i) the structure of the public apologies in terms of their frequency and sequence, and (ii) the users’ responses to these apologies as indicated in their comments. Four public apologies were purposively selected: They were all presented in English by the executives and posted on Facebook between 2011 and 2015. The responses to these apologies were also collected. The results of content analysis indicate that apology strategies, including taking full responsibility, asking for forgiveness, being sincere, and being published in a timely manner are the most effective strategies to elicit positive responses. The results have useful implications for research and practice in the area.
You have requested "on-the-fly" machine translation of selected content from our databases. This functionality is provided solely for your convenience and is in no way intended to replace human translation. Show full disclaimer
Neither ProQuest nor its licensors make any representations or warranties with respect to the translations. The translations are automatically generated "AS IS" and "AS AVAILABLE" and are not retained in our systems. PROQUEST AND ITS LICENSORS SPECIFICALLY DISCLAIM ANY AND ALL EXPRESS OR IMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATION, ANY WARRANTIES FOR AVAILABILITY, ACCURACY, TIMELINESS, COMPLETENESS, NON-INFRINGMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Your use of the translations is subject to all use restrictions contained in your Electronic Products License Agreement and by using the translation functionality you agree to forgo any and all claims against ProQuest or its licensors for your use of the translation functionality and any output derived there from. Hide full disclaimer





