aceModerate evidence
Published recordLifestyleProblem Space
More
“I am here for you”: Adolescents’ perceptions of relational conversational AI and the social-emotional correlates of preference
- Truvace record
- TRV-2026-2546raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 4515a6d52fbc…check it
General-purpose conversational AI chatbots and AI companions increasingly offer adolescents emotionally supportive conversations, raising questions about how conversational profile shapes immediate social perceptions and preferences. In a preregistered online experiment with 284 adolescent–parent dyads, youth aged 11-15 and their parents read two closely matched transcripts in which a chatbot responded to the same everyday social problem using either a relational conversational profile (affiliative and commitmen…
The problem
In an online experiment with 284 US adolescent-parent pairs, 11-to-15-year-olds who preferred the relational chatbot ("I am here for you") reported lower family relationship quality and higher anxiety than those who preferred the transparent one, as measured in a single sitting.
What this doesn’t fix
The study used written transcripts rather than live chatbot conversations, and its cross-sectional design cannot show whether distress leads teens to prefer relational chatbots or the reverse.
Sources
1 on file- Computers in Human Behavior Reportsdoi:10.1016/j.chbr.2026.101297
Cite this record
v1Truvace Impact Record TRV-2026-2546, v1: ““I am here for you”: Adolescents’ perceptions of relational conversational AI and the social-emotional correlates of preference.” Truvace, 2026-11-12. /record/TRV-2026-2546 (accessed on the day you copy it). sha256 4515a6d52fbcbd51…
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-2546 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.