Certified into the record
The exact text we saved
This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.
TRUVACE RECORD VERSION record: TRV-2026-2666 version: 1 kind: certified reason: Certified into the record timestamp: 2026-11-12T16:58:06.155806Z status: published lens: g_space sector: business headline: From Stranger to Someone: How Naming Creates Closeness and Buffers Chatbot Service Failure dek: 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… gain_title: 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. problem_title: (none) trace_subject: (none) gain_reading: 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. gain_evidence: consumers exhibit higher reuse intention toward chatbots they name themselves than toward chatbots they do not name problem_reading: (none) problem_evidence: (none) quick_read: A peer-reviewed paper in Psychology & Marketing reports four experiments plus a content analysis of naming texts. Consumers who named a chatbot themselves showed higher intention to reuse it after a service failure than those who did not name it. The researchers also compared consumer-assigned, firm-assigned and unnamed chatbots. This separated the act of naming from simply having a name, and the benefit came from the consumer doing the naming. The effect ran through closeness: giving the chatbot a name made it feel relationally closer, which raised reuse intention. It was stronger in hedonic (enjoyment-oriented) services and weaker in utilitarian ones, so it may help firms less where tasks are purely functional. limitation: The naming benefit was weaker in utilitarian service contexts, so it does not apply equally across all types of chatbot services. tag: Evidence-backed gain key_points: The research combines four experiments with a content analysis of the texts consumers used when naming chatbots. | Consumers who named their chatbot reported higher reuse intention after a failure than those with unnamed chatbots. | Consumer-assigned, firm-assigned and unnamed chatbots were compared to separate the act of naming from the mere presence of a name. | Feelings of closeness to the chatbot mediated the effect of naming on reuse intention. | The naming effect was stronger in hedonic service contexts and weaker in utilitarian ones. rundown: The study responds to chatbot service failures becoming more common across service settings, which reduce consumers' willingness to reuse these technologies. It tests whether naming behavior can preserve reuse intention after a failure. Its design compares three conditions: chatbots named by consumers, chatbots named by firms and unnamed chatbots. That comparison lets the authors distinguish the effect of performing the naming action from the effect of the mere presence of a name. The authors identify service type as a boundary condition. The effect is stronger for hedonic services and weaker for utilitarian ones, and they present consumer-assigned naming as a preventive pathway that firms can use to manage chatbot failures. sources: - peer_reviewed | Psychology & Marketing | https://doi.org/10.1002/mar.70250 | 2026-08-11 prev: 0000000000000000000000000000000000000000000000000000000000000000
- SHA-256 hash
- 040117ca0cfb6a7b4e244398145984403e64594b5fe935ddbf121ff154ccd67c
- Previous version’s hash
- 0000000000000000000000000000000000000000000000000000000000000000
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.
ace