70/100

Moderate evidence

GainPublished recordHealthGood Space

Efficacy of relational agents for loneliness across age groups: a systematic review and meta-analysis

Truvace record
TRV-2026-2795raw data (JSON)
Version
v1Published
First published
Evidence type
Systematic review or meta-analysis
Sources
1 sourcePeer-reviewed
sha256
7863697b3267…check it

Abstract Background Loneliness is a serious public health concern. Although previous interventions have had some success in mitigating loneliness, the field is in search of novel, more effective, and more scalable solutions. Here, we focus on “relational agents”, a form of software agents that are increasingly powered by artificial intelligence and large language models (LLMs). We report on a systematic review and meta-analysis to investigate the impact of relational agents on loneliness across age groups. Metho…

The gain

A meta-analysis of 14 studies with 286 participants aged 19 to 100 found that relational agents (companion robots and app-based conversational agents) reduced self-reported loneliness by a moderate amount (Hedge's g = -0.552).

What this doesn’t fix

Most of the 14 studies were small, high risk of bias and short in follow-up (mean 5.92 weeks), and a publication-bias adjustment shrank the effect by roughly 64% to a non-significant g = -0.198.

Sources

1 on file
  1. BMC Public Healthdoi:10.1186/s12889-024-19153-x
    Peer-reviewed2024-07-06

Cite this record

v1

Truvace Impact Record TRV-2026-2795, v1: “Efficacy of relational agents for loneliness across age groups: a systematic review and meta-analysis.” Truvace, 2026-11-12. /record/TRV-2026-2795 (accessed on the day you copy it). sha256 7863697b3267f630…

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

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