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-2586 version: 1 kind: certified reason: Certified into the record timestamp: 2026-11-12T07:57:58.235146Z status: published lens: g_space sector: business headline: Communication style synergy in chatbot-human service teams: dividing warmth and competence to enhance customer satisfaction dek: Artificial intelligence (AI) chatbots are increasingly used in customer service, but customers still prefer human agents due to chatbots’ limited empathy. Hybrid service models that combine chatbots with human agents offer a solution, but it remains unclear how best to coordinate their communication styles. This research investigates whether mixing communication styles (one agent using a task-oriented, efficient approach while the other uses a warm, social approach) yields better outcomes than using a uniform st… gain_title: In an online experiment of 800 participants reading scripted e-commerce chats, teams where the chatbot and human agent used different styles (one task-focused, one warm) scored about 4.5 to 4.8 on satisfaction versus about 3.6 to 3.7 for same-style teams. problem_title: (none) trace_subject: (none) gain_reading: In an online experiment of 800 participants reading scripted e-commerce chats, teams where the chatbot and human agent used different styles (one task-focused, one warm) scored about 4.5 to 4.8 on satisfaction versus about 3.6 to 3.7 for same-style teams. gain_evidence: Study 1 found that mixed-style chatbot-human teams generated higher customer satisfaction than same-style teams by fostering greater teamwork and empathy. problem_reading: (none) problem_evidence: (none) quick_read: Researchers ran two scenario-based online experiments on hybrid customer service in which a chatbot hands a customer over to a human agent. In Study 1, 800 participants read scripted e-commerce chats. Teams in which one agent was task-focused and the other warm and social produced higher satisfaction than teams in which both used the same style (β = 0.56, p < 0.001). Mean satisfaction on a 7-point scale was 4.80 for social chatbot with task-focused human, 4.52 for task chatbot with social human, 3.64 for social-social and 3.69 for task-task. Participants in mixed-style conditions also rated the agents' collaboration and empathy higher, and these ratings partly explained the satisfaction gain. Study 2 (1,200 participants) looked only at mixed-style teams. A warm-first sequence raised perceived collaboration more in post-purchase scenarios, and empathy mattered more to satisfaction when customers themselves asked for a human. All participants responded to scripted dialogues rather than real service encounters. limitation: Both studies used scripted chat dialogues read by online panel participants imagining themselves as customers, and transfer initiation in Study 2 was chosen by participants rather than assigned. tag: Evidence-backed gain key_points: Study 1 used 800 valid responses (from 828) split evenly into four conditions of 200, crossing chatbot style with human agent style. | Mixed-style pairings beat same-style pairings on satisfaction (β = 0.56), perceived collaboration (β = 0.92) and perceived empathy (β = 1.09). | The two same-style conditions did not differ significantly on satisfaction (3.64 vs 3.69, p = .690), so neither all-warm nor all-task teams did better. | A social chatbot followed by a task-focused human scored higher on satisfaction (4.80) than the reverse order (4.52, p = .012). | Study 2 used 1,200 valid participants (from 1,273); the warm-first advantage on perceived collaboration was larger in post-purchase scenarios (after-sales price adjustment) than pre-purchase ones (asking about a discount). | Study 2 found that service stage did not significantly change perceived empathy (interaction p = .236). | When customers chose to be transferred to a human, perceived empathy predicted satisfaction more strongly, while perceived collaboration predicted it less strongly than under system-initiated transfers. rundown: Study 1 used a 2 × 2 between-subjects design in which participants imagined themselves as customers contacting an e-commerce platform. The chatbot replied first and a human agent then took over. Social styles used greetings like "Hello there!" and empathic statements, while task styles were strictly transactional. Participants came from the Credamo panel, were paid RMB 2, and answered 7-point scales for collaboration, empathy and satisfaction. Bootstrapped mediation analysis showed both perceived collaboration (indirect effect 0.246) and perceived empathy (0.190) carried part of the style-mismatch effect on satisfaction, with a direct effect remaining. Mean collaboration scores were 5.57 and 5.02 in the mixed conditions versus 4.30 and 4.45 in the same-style ones. Study 2 manipulated communication order and service stage; transfer initiation was decided by participants who chose yes or no to a transfer prompt. Quotas of 150 per cell were applied, and respondents were paid RMB 3. The warm-first order outperformed task-first, with the gap largest after purchase and when customers requested the handoff. The authors suggest service teams could structure chats so warm engagement comes before task resolution. They note that the sequencing effect reflects how warmth and competence cues are configured across agents, not sequencing acting as a separate mechanism. sources: - peer_reviewed | Humanities and Social Sciences Communications | https://doi.org/10.1057/s41599-026-08477-1 | 2026-08-21 prev: 0000000000000000000000000000000000000000000000000000000000000000
- SHA-256 hash
- 8030aff58174567411e1f5de3123e803e8644e29d1c4e6aa4200f106d755bb81
- Previous version’s hash
- 0000000000000000000000000000000000000000000000000000000000000000
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2586 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