70/100

Moderate evidence

GainPublished recordHealthGood Space

Wired for companionship: a meta-analysis on social robots filling the void of loneliness in later life

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

BACKGROUND AND OBJECTIVES: Loneliness is a significant public health concern affecting over a quarter of older adults worldwide. Emerging research suggests that artificial intelligence (AI)-enabled social robots may offer a viable alternative for providing a new form of social support and reducing loneliness. This meta-analysis evaluates the effectiveness of AI-enabled social robots in reducing loneliness among older adults and examines the conditions under which these interventions are most effective. RESEARCH…

The gain

A meta-analysis of 19 studies with 1,083 older adults found AI-enabled social robots cut loneliness, with a pooled effect size of -0.590 and larger reductions in nursing homes, dementia centers and hospitals than at home.

What this doesn’t fix

Egger's test and the funnel plot showed asymmetry suggesting publication bias that may overestimate the effect, and most studies came from high-income countries, limiting applicability elsewhere.

Sources

1 on file
  1. The Gerontologistdoi:10.1093/geront/gnaf219
    Peer-reviewed2025-09-27

Cite this record

v1

Truvace Impact Record TRV-2026-2776, v1: “Wired for companionship: a meta-analysis on social robots filling the void of loneliness in later life.” Truvace, 2026-11-12. /record/TRV-2026-2776 (accessed on the day you copy it). sha256 d922b34d932cd696…

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

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