Flag passholders who still owe a signed waiver
Every morning, WebRun opens Parker, lists active season passholders, checks each one for a signed and current facility waiver, writes anyone missing a waiver to a Google Sheet with the pass details, and posts guest services the flagged list in Slack so the team can chase the waiver before the passholder next checks in.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I find season passholders missing a signed facility waiver?
Every morning, WebRun lists active season passholders in Parker, checks each for a signed and current facility waiver, and writes anyone missing one to a Google Sheet. It then posts guest services the flagged list in Slack, so the team can chase each waiver before that passholder next checks in. Nothing is sent to guests, it is an internal list.
- Every passholder missing a waiver is surfaced before their next visit
- Guest services opens Slack to a ready follow-up list each morning
- Partial group coverage is caught, not just fully missing waivers
Built for water park operators · guest services · compliance leads · membership teams
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
Parker - check passes for a signed waiver
WebRun checks each pass for a signed waiver in Parker. - Open Parker and list every active season pass
- For each passholder, check whether a signed facility waiver is on file
- Note any waiver that is missing, expired, or covers only part of the group
- Capture the passholder name, pass type, and expiry for each gap
Done when Every active passholder has been checked for a current signed waiver.
-
2
Google Sheets - log passholders missing a waiver
WebRun logs the passholders missing a waiver in Google Sheets. - Open the waiver tracking sheet in Google Sheets
- Write each passholder missing a current waiver as a row
- Record the pass type, expiry, waiver status, and any group members still unsigned
- Update the status of anyone who has since signed so the list stays current
Done when The sheet lists every passholder missing a current signed waiver.
-
3
Slack - post guest services the flagged list
WebRun posts guest services the flagged waiver list in Slack. - Post the guest services channel a short list of passholders missing a waiver
- Put anyone with an imminent booking at the top of the list
- Link the Google Sheet so the team can see full details and mark follow-ups
Done when Guest services has the flagged waiver list in Slack with the sheet linked.
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 this contact passholders directly?
No. This workflow only builds an internal list in a Google Sheet and posts it to Slack for your guest services team. It never messages a passholder. Pair it with a separate drafting workflow if you want to reach out.
How does it know a waiver is out of date?
It reads the waiver record for each pass in Parker and flags any that is missing, expired, or does not cover every named member of the group, so partial coverage is caught, not just fully absent waivers.
What happens once a passholder signs?
It rereads Parker each morning, so anyone who has since signed a current waiver is marked resolved on the sheet and drops off the next Slack list automatically.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.