Truace
Subscribe
70/100

Moderate evidence

GainPublished recordEducationGood Space

Full story
More
Export record JSONEmailLinkedInX

Let’s Chat: Leveraging Chatbot Outreach for Improved Course Performance

Truvace record
TRV-2026-2480raw data (JSON)
Version
v1Published
First published
Evidence type
Randomized controlled trial
Sources
1 sourcePeer-reviewed
sha256
b770b0d2fb56…check it

This study provides pre-registered, experimental evidence on the use of non-generative artificial intelligence (AI) chatbots to support students in large-enrollment undergraduate courses. We find the chatbot messaging increased students’ final grades and engagement with academic supports, such as tutoring. Treatment effects were generally consistent across student demographics, with the exception of treated women in a Microeconomics course, who earned final grades that were seven percentage points higher than wo…

The gain

In randomized trials covering 2,483 students at Georgia State University, students assigned to course chatbot texts were four percentage points more likely to earn an A or B than the 61% of control students who did.

What this doesn’t fix

Only about half of Government students completed the end-of-course survey, with response rates lower for Black students, course retakers and students with lower high school GPAs, and no survey was fielded in Microeconomics; the authors also caution against over-interpreting the mechanism results.

Sources

1 on file
  1. NBER Working Paperdoi:10.3386/w35397
    Peer-reviewed2026-07-01

Cite this record

v1

Truvace Impact Record TRV-2026-2480, v1: “Let’s Chat: Leveraging Chatbot Outreach for Improved Course Performance.” Truvace, 2026-11-12. /record/TRV-2026-2480 (accessed on the day you copy it). sha256 b770b0d2fb562ccc…

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

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