Turn checkout height answers into a ride roster
Every morning, WebRun opens Parker, reads the height and age details guests provided at checkout for today's bookings, works out which rides each guest meets the requirements for, writes an internal ride-eligibility roster to a Google Sheet, and posts guest services a Slack note of the groups with under-height guests so staff can steer them to suitable attractions.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I turn checkout height answers into a staff ride-eligibility roster?
Every morning, WebRun reads the height answers guests gave at Parker checkout for today's bookings, matches each guest to the slides they can ride, and builds a staff roster in a Google Sheet. It then posts guest services a Slack note of groups with under-height guests, so staff can steer them to suitable attractions. No guest is contacted.
- Staff see each group's ride eligibility before the gates open
- Under-height guests are guided to suitable attractions, not turned away at the slide
- The roster stays internal, so no guest is messaged about height
Built for water park operators · guest services · lifeguard teams · ride attendants
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 - read height and age answers
WebRun reads the height and age answers in Parker. - Open Parker and list today's bookings
- Read the height and age details each guest entered at checkout
- Match each guest against the height requirement for each major slide
- Capture the group, guest, height, and the rides they are eligible for
Done when Every guest arriving today has their height answers and eligible rides recorded.
-
2
Google Sheets - build the ride-eligibility roster
WebRun builds the ride-eligibility roster in Google Sheets. - Open the ride-eligibility roster sheet in Google Sheets
- Write a row per group showing each guest's height and eligible rides
- Highlight guests who fall under the requirement for a given slide
- Keep the roster internal for staff reference only
Done when The sheet holds today's ride-eligibility roster grouped by booking.
-
3
Slack - flag groups with under-height guests
WebRun flags the groups with under-height guests in Slack. - Post guest services a short note of today's groups that include under-height guests
- Note which slides each affected guest cannot ride
- Suggest the family-friendly attractions staff can point them to
- Link the roster so staff can check any guest at the gate
Done when Guest services has today's under-height heads-up in Slack with the roster 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 message guests about their height?
No. This workflow is internal only. It builds a staff roster in a Google Sheet and posts guest services a heads-up in Slack. It never contacts a guest about their height or a child's eligibility.
Where do the height answers come from?
From the details guests enter themselves at Parker checkout. WebRun reads those answers and matches each guest against the posted height requirement for every major slide, so the roster reflects what guests already provided.
How does it help staff at the gate?
It links the roster in Slack so a lifeguard or host can check any guest's eligible rides in seconds, and it suggests family-friendly attractions for under-height guests, so staff can guide groups kindly and quickly.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.