Automated Replika Check-in Engagement Tracking
Every Monday, WebRun opens Replika, reviews each enrolled participant's recent check-in activity, logs the last-active date for each into Airtable, and emails the care team a short summary flagging anyone who hasn't checked in during the past week.
How do I track weekly check-in activity for a Replika-based care program?
WebRun reviews each enrolled participant's Replika check-in activity every Monday, logs the last-active date for everyone into Airtable, and emails the care team a short summary flagging anyone who hasn't checked in that week. It tracks only whether and when someone checked in, never conversation content, so quiet participants get noticed fast without reading anyone's chats.
- Quiet participants get flagged within a week, not a month
- The care team gets one summary instead of checking every account
- A running Airtable history builds up automatically
Built for Care program coordinators · senior wellbeing programs · community support teams · nonprofit case managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
replika.comin a real browser with your saved login - no setup, no API keys. -
1
Replika - check each participant's recent activity
replika.com
WebRun checks each participant's recent activity in Replika. - Open the account for each enrolled participant
- Read the date of their most recent check-in
- Note any participant with no activity this week
Done when Every participant's most recent check-in date is captured.
-
2
Airtable - log the last-active date
airtable.com
WebRun logs the last-active date in Airtable. - Open the participant tracking base
- Update each record with this week's last-active date
- Flag anyone with no activity in the past 7 days
Done when Every participant record reflects this week's activity.
-
3
Gmail - email the engagement summary
gmail.com
WebRun emails the engagement summary through Gmail. - Draft a summary email listing anyone who hasn't checked in
- Include their name and last-active date
- Send it to the care team's internal distribution list
Done when The care team has this week's engagement summary in their inbox.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it read the content of conversations?
No. WebRun only tracks whether and when each participant checked in. It never reads or logs what was actually said.
Who sees this report?
Only your internal care team distribution list. It's never shared with participants or anyone outside your organization.
What if a participant is on an excused break?
Mark them accordingly in Airtable and future runs skip flagging them as inactive until you change the status back.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.