68/100

Moderate evidence

ProblemPublished recordBusinessProblem Space

AI Chatbot Anthropomorphism and Consumer Decision-Making: A Dual-Pathway Calibration Model

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

Anthropomorphism has shown inconsistent effects on human judgment, yet the underlying cognitive mechanisms remain underspecified. This research develops and tests a Dual-Pathway Calibration Model (DPCM) integrating dual-process theory, construal level theory, metacognition theory, and regulatory focus theory to explain how anthropomorphic cues influence cognitive processing in human–artificial intelligence (AI) interaction. Three experiments (N = 832) manipulated anthropomorphism and cue inconsistency, examining…

The problem

In three online experiments with 832 adults in China, decision outcomes with an AI chatbot adviser followed an inverted U (quadratic b = −0.05, p = 0.001), so maximum humanlike design did not give the best results.

What this doesn’t fix

All three experiments used simulated advisory scenarios with participants recruited online from mainland China, and the inverted-U relationship was framed as an exploratory hypothesis.

Sources

1 on file
  1. Behavioral Sciencesdoi:10.3390/bs16081269
    Peer-reviewed2026-07-23

Cite this record

v1

Truvace Impact Record TRV-2026-2674, v1: “AI Chatbot Anthropomorphism and Consumer Decision-Making: A Dual-Pathway Calibration Model.” Truvace, 2026-11-12. /record/TRV-2026-2674 (accessed on the day you copy it). sha256 dd879f461bc4baa8…

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

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