70/100

Moderate evidence

GainPublished recordHealthGood Space

Beyond functionality: how conversational elements and usefulness perceptions shape voice AI experience in healthcare interactions

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

This study investigates how conversational elements in AI healthcare chatbots influence user experience during chronic headache consultations. Using three controlled participant-based voice experiments (N = 1,200), the study examines how empathy type, linguistic softeners, and prosodic diversity shape users’ evaluations of voice-based healthcare AI. The results show that emotional empathy produces significantly more positive user experiences than cognitive empathy, challenging the assumption that factual accurac…

The gain

In three controlled voice experiments with 1,200 participants on chronic headache consultations, a healthcare voice AI that used emotional empathy produced significantly more positive user experiences than one using cognitive empathy.

Sources

1 on file
  1. Behaviour & Information Technologydoi:10.1080/0144929x.2026.2682278
    Peer-reviewed2026-06-04

Cite this record

v1

Truvace Impact Record TRV-2026-2686, v1: “Beyond functionality: how conversational elements and usefulness perceptions shape voice AI experience in healthcare interactions.” Truvace, 2026-11-12. /record/TRV-2026-2686 (accessed on the day you copy it). sha256 d33ad054e62bbf3d…

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

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