aceModerate evidence
Published recordClimateGood Space
More
Talking green: how chatbot interactivity and transparency foster user receptivity to chatbot recommendations in environmental communication
- Truvace record
- TRV-2026-2683raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- d1cc863d4c68…check it
This study examines how chatbot interactivity and limitation transparency shape users’ receptiveness to chatbot recommendations in environmental communication. Drawing on the theory of interactive media effects, we conceptualize these two chatbot features as distinct design cues that influence message acceptance through different psychological mechanisms. Across three experimental studies with Taiwanese participants, the findings show that chatbot interactivity primarily increases receptiveness by strengthening…
The gain
In a 1,200-person experiment in Taiwan, a chatbot that both invited follow-up questions and admitted it was a language model with limitations produced higher receptiveness to its eco-friendly advice than chatbots lacking one or both features (β=0.626).
What this doesn’t fix
The experiments used a single standardized vignette per condition and no extended multi-turn dialogue, and they measured self-reported receptiveness among Taiwanese online participants rather than real behavior change.
Sources
1 on file- Humanities and Social Sciences Communicationsdoi:10.1057/s41599-026-07965-8
Cite this record
v1Truvace Impact Record TRV-2026-2683, v1: “Talking green: how chatbot interactivity and transparency foster user receptivity to chatbot recommendations in environmental communication.” Truvace, 2026-11-12. /record/TRV-2026-2683 (accessed on the day you copy it). sha256 d1cc863d4c687563…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2683 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.