Moderate evidence
Published recordHealthGood Space
More
The Effects of Social Presence of Dementia-Prevention Chatbot on Isolation and Interpersonal Resilience Among Older Adults Living Alone: Evidence on Three-Wave Experiment
- Truvace record
- TRV-2026-2591raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- e694c4cb095c…check it
Dementia-prevention technologies have mostly focused on cognitive enhancement, often neglecting the social aspects of healthy aging. This study examines whether the perceived social presence of a dementia-prevention chatbot, developed through sustained use, can reduce isolation and strengthen interpersonal resilience through communication networks among older adults living alone in Korea. A three-wave experimental design ( N = 110) was implemented over 8 weeks using a smartphone-based chatbot that engaged partic…
The gain
In an 8-week experiment with 110 older adults living alone in Korea, those who felt a dementia-prevention chatbot was more socially present at the midpoint showed greater interpersonal resilience, both at that time and later.
What this doesn’t fix
The chatbot's perceived social presence did not significantly affect isolation, so the benefit is limited to interpersonal resilience and does not show reduced loneliness.
Sources
1 on file- Cyberpsychology, Behavior, and Social Networkingdoi:10.1177/21522715261453464
Cite this record
v1Truvace Impact Record TRV-2026-2591, v1: “The Effects of Social Presence of Dementia-Prevention Chatbot on Isolation and Interpersonal Resilience Among Older Adults Living Alone: Evidence on Three-Wave Experiment.” Truvace, 2026-11-12. /record/TRV-2026-2591 (accessed on the day you copy it). sha256 e694c4cb095c89cb…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2591 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.
ace