Score weekly 15Five check-in completion
Every Friday afternoon, WebRun opens 15Five, checks who has submitted their weekly check-in, posts a Slack reminder to managers whose team members are still missing, and sends HR a Telegram summary of the week's completion rate.
- No credit card
- Under $0.01 per run
- Cancel anytime
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
my.15five.comin a real browser with your saved login - no setup, no API keys. -
1
15Five - check weekly check-in status
15five.com
WebRun opens 15Five to check weekly check-in status. - Open 15Five and pull this week's check-in submission status
- List employees who haven't submitted yet
- Group the list by manager
Done when Every employee's check-in status for the week is captured.
-
2
Slack - remind managers of gaps
slack.com How to Automate Slack
WebRun opens Slack to remind managers of gaps. - Post each manager their team's missing check-ins
- Give managers time to nudge their own team before the week closes
Done when Every manager with a gap has been notified in Slack.
-
3
Telegram - summarize completion for HR
telegram.org How to Automate Telegram
WebRun opens Telegram to summarize completion for HR. - Send HR the week's overall completion percentage
- Flag any team below 80 percent completion
Done when HR has this week's completion rate in Telegram.
How do I track weekly 15Five check-in completion?
WebRun tracks 15Five check-in completion every Friday. It reads who has submitted their weekly check-in, posts each manager a Slack list of their team's gaps, and sends HR a Telegram summary of the overall completion rate, so managers can close the week's gaps before the next check-in cycle opens.
- Managers see their team's gaps before the week closes
- HR gets a completion rate every Friday without pulling a report
- No employee is messaged directly about a missing check-in
Built for People managers · HR operations · engagement leads
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 WebRun submit a check-in for anyone?
No. It only reads submission status. Writing or submitting a check-in always stays with the employee themselves.
Who gets notified about missing check-ins?
Managers, about their own team, in Slack. WebRun never messages an individual employee about their own missing check-in.
How is the completion rate calculated?
Submitted check-ins divided by total employees expected to check in that week, read straight from 15Five each Friday.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.