Truace
Subscribe
70/100

Moderate evidence

GainPublished recordBusinessGood Space

Full story
More
Export record JSONEmailLinkedInX

Communication style synergy in chatbot-human service teams: dividing warmth and competence to enhance customer satisfaction

Truvace record
TRV-2026-2586raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
8030aff58174…check it

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…

The gain

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.

What this doesn’t fix

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.

Sources

1 on file
  1. Humanities and Social Sciences Communicationsdoi:10.1057/s41599-026-08477-1
    Peer-reviewed2026-08-21

Cite this record

v1

Truvace Impact Record TRV-2026-2586, v1: “Communication style synergy in chatbot-human service teams: dividing warmth and competence to enhance customer satisfaction.” Truvace, 2026-11-12. /record/TRV-2026-2586 (accessed on the day you copy it). sha256 8030aff581745674…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv18030aff58174…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
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.