68/100

Moderate evidence

GainPublished recordHealthGood Space

How Empathic Cues Influence Persuasion: The Mediating Role of Perceived Capacity to Feel and the Moderating Role of Message Narrativity

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

This study investigates how empathic cues displayed by an AI chatbot influence perceptions of the chatbot’s mental capacities and persuasive outcomes, and whether these effects vary as a function of message narrativity in the context of mental health care. Using an online experiment (N = 716) across two issues (social isolation and anxiety), we found that in the social isolation context, a chatbot’s expression of empathy increased its perceived capacity to feel, which, in turn, was positively associated with att…

The gain

In an online experiment of 716 people, a chatbot's expression of empathy raised its perceived capacity to feel in the social isolation scenario, which was linked to more positive attitudes toward its recommendations.

What this doesn’t fix

The effect of empathy was not consistent across issues: in the social anxiety context it depended on message narrativity, so the social isolation result does not hold across both scenarios.

Sources

1 on file
  1. Peer-reviewed2026-08-10

Cite this record

v1

Truvace Impact Record TRV-2026-2680, v1: “How Empathic Cues Influence Persuasion: The Mediating Role of Perceived Capacity to Feel and the Moderating Role of Message Narrativity.” Truvace, 2026-11-12. /record/TRV-2026-2680 (accessed on the day you copy it). sha256 1157409adb1ea408…

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

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