70/100

Moderate evidence

GainPublished recordHealthGood Space

Effectiveness of Communication Competence in AI Conversational Agents for Health: Systematic Review and Meta-Analysis

Truvace record
TRV-2026-2737raw data (JSON)
Version
v1Published
First published
Evidence type
Systematic review or meta-analysis
Sources
1 sourcePeer-reviewed
sha256
2a3e6f153c91…check it

Background: With advancements in artificial intelligence and large language models, researchers and designers have increasingly focused on enhancing the conversational capacity of health-related conversational agents (CAs). Communication competence, a key concept in interpersonal communication influencing relational and health outcomes, has been extended to human-machine communication to emphasize the CAs' ability to demonstrate appropriate communicative behaviors in managing relationships with humans. Objective…

The gain

A meta-analysis of 25 experiments with 4,525 participants found that health chatbots built with more communication skills, such as empathy, were rated higher (Hedges g=0.45) and led to better psychological outcomes (g=0.49) than less skilled versions.

What this doesn’t fix

Health outcomes were analysed in only 3 of the 25 studies and the pooled estimate shifted from 0.00 to 0.44 when single studies were removed, so the lack of a health effect is preliminary.

Sources

1 on file
  1. Peer-reviewed2025-11-03

Cite this record

v1

Truvace Impact Record TRV-2026-2737, v1: “Effectiveness of Communication Competence in AI Conversational Agents for Health: Systematic Review and Meta-Analysis.” Truvace, 2026-11-12. /record/TRV-2026-2737 (accessed on the day you copy it). sha256 2a3e6f153c9168a7…

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. Publishedv12a3e6f153c91…

    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-2737 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.