Alert staff to clear slides on a lightning lockout
Every few minutes during operating hours, WebRun checks the lightning status feed, and when a strike lands inside your lockout radius it alerts the lifeguard and ops team in Slack to clear the slides, logs the lockout with its time and distance to a Telegram ops channel, and drafts a guest-facing pause notice in Parker for a manager to approve before it is published.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I alert staff and log a lightning lockout at a water park?
Every few minutes, WebRun checks the lightning feed, and on a strike inside your lockout radius it alerts the lifeguard team in Slack to clear the slides, logs the time and distance to a Telegram ops channel, and drafts a guest pause notice in Parker. The staff alerts post at once. The guest notice waits for a manager.
- Staff get a clear-the-slides alert within minutes of a strike
- Every lockout and all-clear is timestamped in one ops log
- Guest-facing closures wait for a manager rather than posting on their own
Built for water park operators · lifeguard teams · aquatics supervisors · park operations
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
parkerticketing.comin a real browser with your saved login - no setup, no API keys. -
1
Slack - alert staff to clear the slides
WebRun alerts staff to clear the slides in Slack. - Read the lightning status feed for a strike inside your lockout radius
- When one lands, immediately post the lifeguard and ops channel a clear-the-slides alert
- State the strike distance, the time, and the required all-clear wait
- @-mention the on-duty lead so the alert is not missed
Done when The lifeguard and ops team have an immediate clear-the-slides alert in Slack.
-
2
Telegram - log the lockout timeline
WebRun logs the lockout timeline in Telegram. - Post the ops Telegram channel a timestamped entry for the lockout
- Record the strike time, distance, and the earliest all-clear time
- Update the same thread when the wait resets on a fresh strike
- Post the all-clear when the lockout window has fully elapsed
Done when The lockout and its all-clear are logged with times in Telegram.
-
3
Parker - draft a guest-facing pause notice
WebRun drafts a guest-facing pause notice in Parker. - Open Parker and prepare a short guest-facing pause notice for the affected attractions
- State that slides are paused for weather and that entry resumes after the all-clear
- Save the notice as a draft and do not publish it
- Leave it for a manager to approve and post once the situation is confirmed
Done when A guest-facing pause notice is drafted in Parker, unpublished, awaiting a manager.
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 publish a closure to guests on its own?
No. The guest-facing pause notice is drafted in Parker and left unpublished. A manager approves and posts it once the situation is confirmed. Only the internal staff alert in Slack and the ops log in Telegram post automatically.
How fast does the staff alert go out?
Within the same few-minute check cycle. WebRun watches the lightning feed on a short loop during operating hours and posts the clear-the-slides Slack alert as soon as a strike lands inside your lockout radius.
Does it handle the all-clear too?
Yes. It tracks the lockout wait in the Telegram log, resets the timer on any fresh strike, and posts the all-clear once the full weather-hold window has elapsed with no new strikes.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.