68/100

Moderate evidence

GainPublished recordBusinessGood Space

Breaking the Silence: How Chatbots and Human Agents Persuade Noncomplaining Consumers Following Service Failures

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

ABSTRACT Firms are less likely to identify and resolve service deficiencies when consumers do not voice their complaints after service failures. A pressing question is how to persuade those noncomplaining consumers to provide feedback, yet empirical research in this area remains scarce. Our study draws on key questions of persuasion (i.e., who should say what to whom ?) to explore the matching effect of the persuasion source, persuasion message, and persuasion recipient on encouraging disclosure among noncomplai…

The gain

Across five scenario experiments, chatbots using self-benefit appeals made noncomplaining consumers significantly more willing to disclose a past service failure than human agents using other-benefit appeals.

What this doesn’t fix

The evidence comes from scenario experiments, which measure willingness to disclose rather than actual feedback given to firms in real service failures.

Sources

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

Cite this record

v1

Truvace Impact Record TRV-2026-2665, v1: “Breaking the Silence: How Chatbots and Human Agents Persuade Noncomplaining Consumers Following Service Failures.” Truvace, 2026-11-12. /record/TRV-2026-2665 (accessed on the day you copy it). sha256 438c02a090feeab7…

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

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