70/100

Moderate evidence

ProblemPublished recordCrimeProblem Space

Reporting crime to police via human and AI live chats: the salience of procedural justice and outcome favourability

Truvace record
TRV-2026-2495raw data (JSON)
Version
v1Published
First published
Evidence type
Randomized controlled trial
Sources
1 sourcePeer-reviewed
sha256
86ecd1c988d6…check it

As police services adopt automated systems for crime reporting, questions arise about how these technologies affect public perceptions of fairness and legitimacy. This study examines how people evaluate police–public interactions conducted via human or AI-operated live chat. In an online experiment (N = 648), participants read a simulated exchange in which a burglary was reported to either a human officer or an AI chatbot. We manipulated operator type (human vs. AI), procedural justice (fair vs. unfair), and out…

The problem

In an online experiment of 648 participants, identical police behaviour in a simulated burglary report was rated less fair and less satisfactory when delivered by an AI chatbot than by a human officer.

What this doesn’t fix

The study used simulated written exchanges in an online experiment, so participants evaluated a scenario they read rather than a burglary they reported to police.

Sources

1 on file
  1. Police Practice and Researchdoi:10.1080/15614263.2026.2741740
    Peer-reviewed2026-10-18

Cite this record

v1

Truvace Impact Record TRV-2026-2495, v1: “Reporting crime to police via human and AI live chats: the salience of procedural justice and outcome favourability.” Truvace, 2026-11-12. /record/TRV-2026-2495 (accessed on the day you copy it). sha256 86ecd1c988d69bb3…

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

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