aceModerate evidence
Published recordBusinessProblem Space
More
Anthropomorphism and risk perception: The role of trust and domain knowledge in decision-support AI
- Truvace record
- TRV-2026-2503raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- fd6eae6449be…check it
Anthropomorphic design is increasingly used to make conversational AI systems more approachable and socially engaging, yet its effects on users’ risk judgments remain unclear. Drawing on theories of anthropomorphism and cognitive–affective trust, we develop a moderated mediation model explaining how perceived anthropomorphism relates to risk perception in AI decision support. We conducted a large-scale between-subjects online experiment (N = 1,256) using a simulated financial advisor chatbot with a 2 2 2 anthrop…
The problem
In an online experiment with 1,256 people, the more human-like a simulated financial chatbot seemed, the more participants trusted it and, through cognitive trust, the less risky they judged its investment advice, an effect strongest for those with low financial knowledge.
What this doesn’t fix
The authors note they inferred mental processes from psychometric questionnaires, and say the results suggest but do not prove that trust reduces risk perception; domain knowledge was self-reported and the advisor was a simulated chatbot.
Sources
1 on file- International Journal of Human-Computer Studiesdoi:10.1016/j.ijhcs.2026.103956
Cite this record
v1Truvace Impact Record TRV-2026-2503, v1: “Anthropomorphism and risk perception: The role of trust and domain knowledge in decision-support AI.” Truvace, 2026-11-12. /record/TRV-2026-2503 (accessed on the day you copy it). sha256 fd6eae6449be6811…
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-2503 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.