aceModerate evidence
Published recordBusinessThe Trace
More
Too Caring to Be Real? Autonomy‐Supportive AI, Intimacy Gains, and Authenticity Loss
- Truvace record
- TRV-2026-2614raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- d3583c5bc406…check it
ABSTRACT Artificial intelligence‐mediated communication increasingly incorporates autonomy‐supportive and empathic language to foster emotionally meaningful consumer relationships, yet relational outcomes are not uniformly positive. This research introduces Perceived Autonomy Support in AI Communication (PAS‐AI) to explain why empathically framed AI simultaneously enhances perceived intimacy and, beyond a threshold, undermines perceived authenticity. Across a staggered field rollout, a longitudinal user‐level pa…
55Gain side
How the two sides scoreProblem scores higher
60Problem side
The gain
Across a field rollout, a user panel and a 207-person experiment, moderate autonomy-supportive wording in AI messages increased relational intimacy, shown by longer replies and voluntary re-engagement.
The problem
The same research found that when autonomy-supportive cues became overly consistent or fluent, users reported lower authenticity and described AI responses as scripted or "too caring to be real."
A fixed formula sets both scores from the evidence and its sources. Reader votes don’t move them.
What the scores mean
G is the gain side, out of 100. It goes up when the gain is specific, when it measurably helped people and when the sources behind it are strong.
P is the problem side, out of 100. It goes up when the problem is specific, when it measurably hurt people and when the sources behind it are strong.
Sources
1 on file- Psychology & Marketingdoi:10.1002/mar.70187
Cite this record
v1Truvace Impact Record TRV-2026-2614, v1: “Too Caring to Be Real? Autonomy‐Supportive AI, Intimacy Gains, and Authenticity Loss.” Truvace, 2026-11-12. /record/TRV-2026-2614 (accessed on the day you copy it). sha256 d3583c5bc406f97d…
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-2614 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.