68/100

Moderate evidence

ProblemPublished recordLifestyleProblem Space

No one is watching: AI service agents and the rise of unethical consumer behavior

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

The growing use of artificial intelligence (AI) agents in frontline service roles is reshaping frontline interactions, with important implications for consumer ethical behavior. This research examines whether AI-mediated service interactions increase unethical consumer behavior and identifies the psychological mechanism underlying this effect. Across a pilot study and three experiments, we show that consumers who interact with AI agents report higher unethical behavioral intentions than those who interact with h…

The problem

In a pilot study and three experiments, consumers who dealt with AI service agents reported higher unethical behavioral intentions than those who dealt with human employees, because they saw the agent as less able to morally judge them.

What this doesn’t fix

The outcome measured was reported unethical behavioral intentions, not observed real-world misconduct.

Sources

1 on file
  1. Journal of Retailing and Consumer Servicesdoi:10.1016/j.jretconser.2026.105001
    Peer-reviewed2026-07-25

Cite this record

v1

Truvace Impact Record TRV-2026-2602, v1: “No one is watching: AI service agents and the rise of unethical consumer behavior.” Truvace, 2026-11-12. /record/TRV-2026-2602 (accessed on the day you copy it). sha256 397a7d62ac46b5df…

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

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