68/100

Moderate evidence

GainPublished recordBusinessGood Space

From psychological empowerment to human-AI rapport: how Artificial Intelligence Social Responsibility enhances consumer well-being in hospitality

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

As the penetration of artificial intelligence (AI) in the hospitality industry deepens, its ethical and social responsibility issues have become critical factors affecting the customer experience. This research aims to explore how Artificial Intelligence Social Responsibility (AISR), an emerging concept, enhances customer well-being. By integrating Affordance Theory and Self-Determination Theory, the study constructs and tests a moderated chain mediation model. This model proposes that AISR positively influences…

The gain

In three online experiments on hospitality AI, customers who saw AI practising social responsibility reported higher well-being, through a stronger sense of empowerment and closer rapport with the AI.

What this doesn’t fix

The conclusions rest on three online experiments rather than observation of customers in actual hotels.

Sources

1 on file
  1. Journal of Hospitality Marketing & Managementdoi:10.1080/19368623.2026.2683829
    Peer-reviewed2026-06-08

Cite this record

v1

Truvace Impact Record TRV-2026-2681, v1: “From psychological empowerment to human-AI rapport: how Artificial Intelligence Social Responsibility enhances consumer well-being in hospitality.” Truvace, 2026-11-12. /record/TRV-2026-2681 (accessed on the day you copy it). sha256 e0f31f280fd7cccd…

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

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