Certified into the record
The exact text we saved
This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.
TRUVACE RECORD VERSION record: TRV-2026-2657 version: 1 kind: certified reason: Certified into the record timestamp: 2026-11-12T16:57:23.046269Z status: published lens: g_space sector: business headline: The Effects of Chatbot Recovery Strategies and Anthropomorphic Image Type on Service Recovery Satisfaction: The Mediating Roles of Perceived Warmth and Competence dek: The widespread adoption of chatbots enables companies to provide customer service at low cost and with high efficiency. However, the inherent limitations of chatbots often lead to service failures, highlighting the necessity of effective recovery strategies. Nevertheless, the optimal approaches for chatbots to implement self-recovery strategies remain unclear. Drawing on the Computers As Social Actors (CASA) paradigm and the Stereotype Content Model (SCM), this study investigates the interactive effects of recov… gain_title: In two scenario experiments with 162 and 350 Chinese university students, a chatbot whose avatar matched its recovery style (competent look with an informational fix) scored 6.479 on satisfaction versus 4.370 for the mismatched emotional reply. problem_title: (none) trace_subject: (none) gain_reading: In two scenario experiments with 162 and 350 Chinese university students, a chatbot whose avatar matched its recovery style (competent look with an informational fix) scored 6.479 on satisfaction versus 4.370 for the mismatched emotional reply. gain_evidence: a match between a chatbot’s emotional recovery strategy and a warm image (or an informational recovery strategy and a competent image) enhances service recovery satisfaction | M information = 6.479 > M emotion = 4.370 problem_reading: (none) problem_evidence: (none) quick_read: Two offline experiments with university students tested what a customer service chatbot should say, and look like, after it fails. In Study 1 (162 students), those who saw a chatbot with a competent-looking avatar and an informational recovery scored satisfaction 6.479 on a 7-point scale, against 4.370 when the same avatar gave an emotional reply. With a warm avatar, the emotional reply won, 6.096 to 4.864. Students judged a flight-booking failure in which the chatbot hit an error and then completed the booking. The match between wording and avatar worked partly by changing how warm or capable the chatbot seemed. Study 2 (350 students) added time pressure: under high pressure the competent look plus informational reply did best, and under low pressure the warm look plus emotional reply did best. The work used imagined scenarios and student participants from two Chinese universities, so it shows how people judged described interactions rather than real customer complaints. The authors present the results as guidance for designing chatbot recovery scripts and avatars. limitation: tag: Evidence-backed gain key_points: Study 1 used 162 valid students in a 2x2 design: emotional versus informational recovery, and warm versus competent avatar. | With a warm avatar, the emotional recovery scored 6.096 on satisfaction against 4.864 for the informational one. | With a competent avatar, the informational recovery scored 6.479 against 4.370 for the emotional one. | Perceived warmth and perceived competence each partly explained the effect of a matching recovery and avatar, with bootstrap tests that excluded zero. | Perceived competence also mediated the warm-avatar plus emotional-reply effect, which the authors had not predicted. | Study 2 had 350 valid students and added low versus high time pressure; the three-way interaction was significant (F(1, 338) = 4.527, p = 0.034). | Under high time pressure the competent avatar plus informational reply gave higher satisfaction; under low pressure the warm avatar plus emotional reply did. rundown: The scenario had a customer booking a flight from Harbin to Tianjin through a chatbot. After about 20 seconds the chatbot returned an unknown error. In the emotional version it apologized, expressed empathy and urged a retry; in the informational version it listed possible causes and solutions. Both then completed the booking on the second try. Avatars differed by a bright smile and casual dress (warm) or a slight smile and formal dress (competent). Study 1 ran in March 2026 at a behavioral laboratory at a university in Northeast China. It recruited 169 undergraduates, screened for prior chatbot use, and dropped four who failed an attention check, leaving 162 (63 men, 99 women). A two-way ANCOVA found no main effect of avatar type, a significant main effect of recovery strategy, and a large interaction (F(1, 154) = 124.384, p < 0.001). Study 2 ran in April and May 2026 at a university in eastern China, with 356 recruited and 350 valid participants (162 men, 188 women). High time pressure was a scenario with six hours before a 14:00 meeting and a flight to book at once. Low pressure was two days of lead time. Manipulation checks for avatar, strategy and time pressure all passed, and participants rated the scenarios as realistic and immersive. The authors say the findings give firms practical guidance for designing chatbot recovery scripts, such as pairing informational fixes with a professional-looking avatar when customers are in a hurry. Participants were paid 3 RMB each and responded anonymously, and tests for common method bias did not show a serious problem. sources: - peer_reviewed | Behavioral Sciences | https://doi.org/10.3390/bs16091564 | 2026-09-03 prev: 0000000000000000000000000000000000000000000000000000000000000000
- SHA-256 hash
- d832a8d9fb396d3a4e1dbff69b3bf4415cc8fe6f6a93053bb189b86afcc9afc8
- Previous version’s hash
- 0000000000000000000000000000000000000000000000000000000000000000
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2657 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace