aceModerate evidence
Published recordLaborProblem Space
More
AI Usage in Interpersonal Helping Comes at a Cost: Understanding Its Negative Effect on Gratitude and Reciprocation in the Workplace
- Truvace record
- TRV-2026-2538raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- f9fda53c96a8…check it
As the use of artificial intelligence (AI) in interpersonal helping among coworkers grows, its impact on recipients remains underexplored. This research examines how varying levels of AI usage in interpersonal helping (AUIH) impact recipients' reciprocation, alongside the underlying mechanisms and boundary conditions. Through a scenario-based experiment (Study 1, N = 300) and a critical incident technique (Study 2, N = 345), both studies demonstrate that higher levels of AUIH are associated with lower perception…
The problem
In two studies (a 300-person scenario experiment and a 345-person incident survey), colleagues who received help that relied more on AI saw the helper as less effortful and less well-meaning, felt less gratitude and were less likely to return the favour.
What this doesn’t fix
The findings rest on a scenario-based experiment and recalled critical incidents, and they describe associations between AI use, perceptions and reciprocation rather than direct measures of workplace behaviour over time.
Sources
1 on file- International Journal of Human–Computer Interactiondoi:10.1080/10447318.2026.2708474
Cite this record
v1Truvace Impact Record TRV-2026-2538, v1: “AI Usage in Interpersonal Helping Comes at a Cost: Understanding Its Negative Effect on Gratitude and Reciprocation in the Workplace.” Truvace, 2026-11-12. /record/TRV-2026-2538 (accessed on the day you copy it). sha256 f9fda53c96a85901…
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-2538 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.