68/100

Moderate evidence

ProblemPublished recordLaborProblem Space

EXPRESS: When AI Assists at the Frontline: External and Internal Marketing Effects in the Context of Banking Mortgages

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

Artificial intelligence (AI) increasingly assists frontline employees (FLEs) in nonroutine tasks; however, its implications remain uncertain. This study examines how thinking AI, i.e., a machine learning-based tool that derives recommendations from historical patterns, affects external outcomes (market offerings and satisfaction with FLEs) and internal outcomes (FLE job autonomy and satisfaction with the responses received). Quasi-experimental evidence in banking reveals that AI-assisted FLEs adopt more conserva…

The problem

A quasi-experimental banking study found that frontline staff using AI tools approved fewer mortgages and customers were less satisfied with them, while employees reported less job autonomy in an experiment.

What this doesn’t fix

The authors describe the survey and textual analysis as providing only first evidence consistent with the mechanism, so the explanation of why AI assistance changed behavior is not firmly established.

Sources

1 on file
  1. Journal of Marketing Researchdoi:10.1177/00222437261483524
    Peer-reviewed2026-08-21

Cite this record

v1

Truvace Impact Record TRV-2026-2584, v1: “EXPRESS: When AI Assists at the Frontline: External and Internal Marketing Effects in the Context of Banking Mortgages.” Truvace, 2026-11-12. /record/TRV-2026-2584 (accessed on the day you copy it). sha256 f849362cf4d33a87…

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

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