63/100

Moderate evidence

GainPublished recordBusinessGood Space

Striking the Right Pitch: The Inverted U-Shaped Effect of AI Anchor Pitch Variability on Consumer Engagement

Truvace record
TRV-2026-2664raw data (JSON)
Version
v1Published
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
cedbdd8cabfb…check it

As artificial intelligence and digital human technologies become increasingly integrated into livestream commerce, AI anchors are becoming important marketing agents. Yet prior research has focused primarily on their visual characteristics, leaving dynamic vocal cues largely unexplored. Drawing on social response theory and perceived authenticity research, this study examines the nonlinear association between AI anchor pitch variability and consumer engagement, together with a proposed psychological pathway and…

The gain

In 4,322 segments from 330 Douyin AI-anchored livestreams, moderate pitch variability went with the most live comment engagement, and a preregistered experiment found it raised perceived authenticity and engagement intentions versus the extremes.

What this doesn’t fix

The appearance-realism moderation result was conditional and specification-sensitive, and the authors say stimulus-level generalization and causal mediation require further replication.

Sources

1 on file
  1. Peer-reviewed2026-08-14

Cite this record

v1

Truvace Impact Record TRV-2026-2664, v1: “Striking the Right Pitch: The Inverted U-Shaped Effect of AI Anchor Pitch Variability on Consumer Engagement.” Truvace, 2026-11-12. /record/TRV-2026-2664 (accessed on the day you copy it). sha256 cedbdd8cabfb3d42…

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

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