Book parent conference slots without chasing every family
Each term, WebRun opens Prenda, pulls the current enrolled roster, opens a matching round of conference booking slots in Calendly with one per family, and every Monday posts the guide a Slack digest of which families have booked and which have not yet.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I schedule parent conferences for every enrolled microschool family?
Each term, WebRun pulls the current enrolled roster from Prenda and opens a matching round of 15 minute conference slots in Calendly, one per family. Every Monday it posts the guide a Slack digest of who has booked and who has not yet, sorted by the soonest conference date, so filling the term's conference schedule does not mean chasing every family by hand.
- The guide sees who has not booked days before the conference window closes
- Booking slots always match the live roster instead of a stale headcount
- No family gets left off the list because they enrolled after the last round opened
Built for microschool guides · Prenda guides · learning pod founders · enrollment coordinators
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
app.prenda.comin a real browser with your saved login - no setup, no API keys. - 1
-
2
Calendly - open one booking slot per family
WebRun opens Calendly to open one booking slot per family. - Open a fresh round of conference booking slots sized to the roster, one 15 minute slot per family
- Share the booking link
Done when Enough slots exist in Calendly for every enrolled family to book one.
-
3
Slack - report who has and hasn't booked
WebRun opens Slack to report who has and hasn't booked. - Post a weekly digest to the guide listing which families have booked their slot and which have not yet
- Sort soonest conference first
Done when The guide has this week's booked and not yet booked list in Slack.
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 message families who have not booked yet?
No. It only reports who has not booked in a Slack list for the guide. Reaching out to a family directly stays a human message.
How does it know how many slots to open?
It reads the current enrolled roster from Prenda, so the booking round always matches how many families are actually active in the pod.
Can a withdrawn family still book a slot?
No. Prenda's roster excludes anyone marked withdrawn before the booking round opens, so slots only go to currently enrolled families.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.