aceModerate evidence
Published recordLaborProblem Space
More
Trust in AI vs human expert: investigating behavioral intention among employees
- Truvace record
- TRV-2026-2611raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- f58d884db32e…check it
Purpose This study aims to investigate the interactive effect between information quality (high vs low) and agent (artificial intelligence [AI] expert vs human expert) on hospitality employees’ trust and behavioral intention. Design/methodology/approach Five scenario-based survey experiments were conducted, systematically varying the combinations of information quality and agent. Data were collected from hospitality employees to examine their responses regarding trust, perceived effectiveness and behavioral inte…
The problem
In five scenario-based survey experiments with hospitality employees, low-quality information was more likely to be trusted and followed when it came from an AI expert than from a human expert.
What this doesn’t fix
The evidence comes from scenario-based survey experiments, which measure stated trust and behavioral intention rather than actual workplace behavior, and the mitigating role of critical thinking is described only as something that "may help".
Sources
1 on file- International Journal of Contemporary Hospitality Managementdoi:10.1108/ijchm-07-2025-1078
Cite this record
v1Truvace Impact Record TRV-2026-2611, v1: “Trust in AI vs human expert: investigating behavioral intention among employees.” Truvace, 2026-11-12. /record/TRV-2026-2611 (accessed on the day you copy it). sha256 f58d884db32ef8c6…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2611 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.