Automated Livestorm Registrant Reminders
Every afternoon, WebRun opens Livestorm, lists the sessions running tomorrow, pulls each confirmed registrant and their join link, queues a short SMS reminder in Twilio for you to approve, and posts the host a headcount and readiness note in Slack.
How do I remind Livestorm registrants the day before a webinar?
WebRun opens Livestorm every afternoon, pulls the registrant list for every session running in the next 24 hours, and queues a personal SMS reminder in Twilio with the start time and join link. You approve the batch, and WebRun posts the host a per-session headcount in Slack.
- Every registrant gets a reminder with their join link the day before
- Hosts see tomorrow's headcount before the session, not after
- No SMS leaves Twilio until a human approves the batch
Built for marketing teams · webinar hosts · demand generation · training providers
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
livestorm.coin a real browser with your saved login - no setup, no API keys. -
1
Livestorm - list tomorrow's registrants
WebRun opens Livestorm to list tomorrow's registrants. - Open Livestorm and filter events to sessions starting in the next 24 hours
- Open each session's registrant list and capture name, phone number, and join link
- Skip registrants who already attended a previous run of the same session
Done when Every registrant for tomorrow's sessions is listed with a join link.
-
2
Twilio - queue SMS reminders
WebRun opens Twilio to queue SMS reminders for approval. - Draft one short SMS per registrant with the session name, the start time in their time zone, and the join link
- Queue every message in Twilio and leave it unsent for your approval
- Hold back any number that has opted out or bounced on a previous send
Done when A reminder is queued and waiting for approval for every registrant.
-
3
Slack - brief the host on headcount
WebRun opens Slack to brief the host on headcount. - Post the host a per-session headcount with confirmed registrants and how many reminders are queued
- Flag any session sitting below its usual registration count
- Link straight to the Livestorm session page and the queued Twilio batch
Done when The host has tomorrow's headcount and the queued reminder count 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
Will it text registrants without my approval?
No. WebRun drafts and queues every SMS in Twilio and leaves it unsent. Nothing reaches a registrant until you approve the batch, so a wrong time or a wrong link is caught before it goes out.
What does the reminder message say?
A short line with the session name, the start time in the registrant's time zone, and their personal join link. Give WebRun a sample message and it will match your wording.
Does it handle people who registered late?
Yes. It reads the live registrant list in Livestorm on every run, so anyone who signed up since the last run is picked up in the next batch.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.