68/100

Moderate evidence

ProblemPublished recordMedia & ArtsProblem Space

The effect of response typing speed on trust in AI chat interfaces

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

Trust in artificial intelligence systems has become increasingly important as these systems assume advisory and decision-support roles. The present studies examine whether the temporal presentation of artificial intelligence (AI) generated responses, specifically typing animation speed, affects trust in chat-based interfaces. In Experiment 1, participants ( N = 71) interacted with three AI agents using pre-scripted question-response pairs detailing different facts about exotic animals. Response presentation spee…

The problem

In two experiments with 71 and 68 participants, AI chat responses shown with a typing animation earned higher trust ratings than instant responses, even though content was unchanged, so a display effect can shift trust.

What this doesn’t fix

Each experiment had fewer than 75 participants, and Experiment 1 used pre-scripted answers about exotic animals, which limits how far the results extend to other topics.

Sources

1 on file
  1. Computers in Human Behavior Reportsdoi:10.1016/j.chbr.2026.101451
    Peer-reviewed2026-11-19

Cite this record

v1

Truvace Impact Record TRV-2026-3077, v1: “The effect of response typing speed on trust in AI chat interfaces.” Truvace, 2026-11-20. /record/TRV-2026-3077 (accessed on the day you copy it). sha256 cc7ce2a9124b9525…

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

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