Automated Crowdcast Replay View Digest
Every night, WebRun checks Crowdcast for the current replay's view activity, posts a digest to Telegram naming how many registrants have watched versus not, and drafts a short reminder text through Twilio for registrants who have not watched yet, left unsent for a human to review before it goes out.
How do I follow up with Crowdcast registrants who missed the replay?
WebRun checks Crowdcast every night for who has watched the current replay, posts a digest to Telegram, and drafts a reminder text through Twilio for registrants who have not watched after 3 days, left for a human to approve, so replay views keep climbing without an unreviewed message going out.
- Replay progress is visible every night without checking Crowdcast
- Reminder drafts wait a full 3 days before going out
- Every reminder text is reviewed before a registrant sees it
Built for webinar hosts · online educators · community managers · course creators
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
crowdcast.ioin a real browser with your saved login - no setup, no API keys. -
1
Crowdcast - check replay view activity
crowdcast.io
WebRun opens Crowdcast to check replay view activity. - Open Crowdcast and load the current replay's view report
- Count registrants who have watched versus not
- List registrants who have not watched after 3 days
Done when Replay view activity is known against the full registrant list.
-
2
Telegram - post the daily digest
telegram.org
WebRun opens Telegram to post the daily digest. - Post how many registrants have watched the replay so far
- Note how many have not watched after 3 days
- Keep the digest to one short message
Done when The host has today's replay view digest in Telegram.
-
3
Twilio - draft a reminder text
twilio.com
WebRun opens Twilio to draft a reminder text. - Draft a short reminder text for registrants who have not watched
- Leave the draft unsent for a human to review and approve
- Include the replay link in the draft
Done when An unsent reminder text draft exists for each unwatched registrant.
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 the reminder texts send without me?
No. WebRun only drafts them through Twilio for registrants who have not watched. A human has to review and approve each one before it reaches anyone.
How long does WebRun wait before drafting a reminder?
3 days after the event, so registrants get a genuine chance to watch on their own before a reminder is even drafted.
What happens once someone watches the replay?
They drop off the unwatched list on the next check, so a reminder draft is never sent for someone who already watched.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.