68/100

Moderate evidence

GainPublished recordBusinessGood Space

From Stranger to Someone: How Naming Creates Closeness and Buffers Chatbot Service Failure

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

ABSTRACT Chatbot service failures have become increasingly common across service settings, reducing consumers' willingness to reuse these technologies. This research examines whether naming behavior can preserve reuse intention following chatbot service failure. Across four experiments and a content analysis of naming texts, we find that consumers exhibit higher reuse intention toward chatbots they name themselves than toward chatbots they do not name. By comparing consumer‐assigned, firm‐assigned, and unnamed c…

The gain

In four experiments, consumers who named a chatbot themselves reported higher intention to reuse it after a service failure than consumers whose chatbot was unnamed, because naming made it feel closer.

What this doesn’t fix

The naming benefit was weaker in utilitarian service contexts, so it does not apply equally across all types of chatbot services.

Sources

1 on file
  1. Psychology & Marketingdoi:10.1002/mar.70250
    Peer-reviewed2026-08-11

Cite this record

v1

Truvace Impact Record TRV-2026-2666, v1: “From Stranger to Someone: How Naming Creates Closeness and Buffers Chatbot Service Failure.” Truvace, 2026-11-12. /record/TRV-2026-2666 (accessed on the day you copy it). sha256 040117ca0cfb6a7b…

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

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