TRV-2026-2585Version 1 · Published

Saved · see the current record

Why this version exists

Certified into the record

The exact text we saved

This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.

TRUVACE RECORD VERSION
record: TRV-2026-2585
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-11-12T07:57:57.465698Z
status: published
lens: trace
sector: business
headline: Empowered generative artificial intelligence in retail service recovery: Recovery justice, customer effort reduction, trust restoration, and purchase behaviour
dek: Retailers increasingly deploy generative artificial intelligence (GenAI) to handle complaints, yet evidence remains limited on when these agents restore purchasing rather than merely improve immediate evaluations. We develop a configuration model in which recovery agent identity (GenAI versus human) is separated from recovery agent empowerment, defined as authority to complete a remedy during the encounter. Across a qualitative study, two pretests, two randomised experiments, and two secondary-data studies in Un…
gain_title: In experiments and UK retail field studies, generative AI complaint agents that could issue refunds, replacements, delivery upgrades or credits improved perceived justice, cut customer effort, restored trust and produced the strongest purchase outcomes.
problem_title: Generative AI complaint agents without visible authority to complete a remedy were not better than human agents, and the study found customers with strong relationships penalised low-empowerment AI more.
trace_subject: Generative AI agents handling retail customer complaints
gain_reading: In experiments and UK retail field studies, generative AI complaint agents that could issue refunds, replacements, delivery upgrades or credits improved perceived justice, cut customer effort, restored trust and produced the strongest purchase outcomes.
gain_evidence: Empowered GenAI improved justice, reduced effort, and restored trust, and generated the strongest purchase outcomes.
problem_reading: Generative AI complaint agents without visible authority to complete a remedy were not better than human agents, and the study found customers with strong relationships penalised low-empowerment AI more.
problem_evidence: GenAI was not inherently superior to a human agent. | customer relationship strength amplified both the penalty for low-empowerment GenAI and the reward for empowered GenAI
quick_read: A peer-reviewed study of generative AI in UK retail complaints found that the identity of the agent mattered less than its authority. AI agents that could issue refunds, replacements, delivery upgrades or account credits during the encounter improved perceived fairness, reduced customer effort and restored trust, and produced the strongest purchase outcomes.

The work combined a qualitative study, two pretests, two randomised experiments and two secondary-data studies. The experiments used an incentivised purchase choice, while the field studies tracked repeat purchase, spending, time to next purchase and churn.

The advantage was not universal. Severe failures weakened the benefit of empowered AI, and strong customer relationships raised both the penalty for a low-authority AI agent and the reward for an empowered one. The authors recommend selective empowerment for routine failures and hybrid escalation to people for severe or data-constrained cases.
limitation: Failure severity weakened the advantage of empowered generative AI, so the benefit does not hold equally for severe or data-constrained complaints.
tag: Dual reading
key_points: Generative AI was not inherently better than a human agent at handling complaints. | Its advantage appeared when it had visible, executable authority to issue refunds, replacements, delivery upgrades or account credits. | Empowered AI improved perceived recovery justice, reduced customer effort and restored trust. | Empowered AI generated the strongest purchase outcomes among the configurations tested. | Field studies observed repeat purchase, spending, time to next purchase and churn in UK retailing. | Severe failures weakened the advantage of empowered AI agents. | Stronger customer relationships amplified both the penalty for low-empowerment AI and the reward for empowered AI.
rundown: The research separates two features usually bundled together: whether the complaint handler is AI or human, and whether it is empowered, meaning it has authority to complete a remedy during the encounter. This lets the authors test each independently.

The evidence base spans seven parts in UK retailing: a qualitative study, two pretests, two randomised experiments and two secondary-data studies. Experiments measured an incentivised purchase choice; field studies observed real repeat purchase, spending, timing of the next purchase and churn.

The authors propose an authority-identity decoupling view: customers respond not only to who communicates but to whether the recovery system gives that agent the data access, decision rights and operational capability to act.

Their practical conclusion is selective empowerment for routine failures, with accountable hybrid escalation to humans for severe or data-constrained cases.
sources:
- peer_reviewed | Journal of Retailing and Consumer Services | https://doi.org/10.1016/j.jretconser.2026.105042 | 2026-08-18
prev: 0000000000000000000000000000000000000000000000000000000000000000
SHA-256 hash
d4f998b6fd6280768091bc0641d9299d24a1ba9017365622933c1f3847f356e9
Previous version’s hash
0000000000000000000000000000000000000000000000000000000000000000
Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2585 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.