Truace
Subscribe
68/100

Moderate evidence

ProblemPublished recordLaborProblem Space

Full story
More
Export record JSONEmailLinkedInX

How rejection letters from AI recruiters shape recruiter's prestige and experienced respect

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

Introduction Organizations increasingly rely on artificial intelligence (AI) in recruitment, yet little is known about how AI systems should communicate unfavorable outcomes such as rejection. The present research examined how type of rejection letters of an AI recruiter shape applicants' perceptions of the recruiter and their experienced respect. Methods Two experiments were conducted. In Study 1, the type of AI-generated rejection letter (considerate vs. typified) and applicants' employment status (unemployed…

The problem

In a scenario experiment with 232 adults, a generic AI rejection email made the recruiter seem more machine-like than a personalized, explained one, and that perception was linked to lower recruiter prestige and less felt respect.

What this doesn’t fix

Both studies were scenario-based experiments in which participants imagined being rejected, and the vignette did not specify any particular AI system, so real applicants' reactions may differ.

Sources

1 on file
  1. Frontiers in Organizational Psychologydoi:10.3389/forgp.2026.1933320
    Peer-reviewed2026-09-07

Cite this record

v1

Truvace Impact Record TRV-2026-2526, v1: “How rejection letters from AI recruiters shape recruiter's prestige and experienced respect.” Truvace, 2026-11-12. /record/TRV-2026-2526 (accessed on the day you copy it). sha256 bedacac52f59fcb5…

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

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