Reopen timed slots as cancellations free capacity
Every hour during sales, WebRun opens Parker, compares each timed-entry window's booked count against its cap, and when cancellations or no-shows free up a previously sold-out window it logs the freed slots to a Google Sheet, posts the box office in Telegram, and drafts a slot-release for a manager to approve before those slots return to public sale.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I reopen sold-out timed slots when capacity frees up?
Every hour, WebRun compares each timed-entry window's booked count against its cap in Parker, and when cancellations free a sold-out window it logs the freed slots to a Google Sheet, posts the box office in Telegram, and drafts a slot-release. A manager approves before slots return to sale, so capacity reopens deliberately, never on its own.
- Freed capacity is spotted within the hour instead of sitting unsold
- Every release is drafted and logged, so nothing reopens unnoticed
- Slots only return to sale once a manager approves, avoiding oversell
Built for water park operators · box office teams · revenue managers · capacity planners
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 - find windows with freed capacity
WebRun finds the windows with freed capacity in Parker. - Open Parker and read the booked count and cap for each timed-entry window
- Identify windows that were sold out but now have freed capacity
- Capture how many slots freed up and what caused it, such as a cancellation
- Prepare a slot-release for each affected window but do not publish it
Done when Every window with newly freed capacity is identified with the count of open slots.
-
2
Google Sheets - log the freed slots
WebRun logs the freed slots in Google Sheets. - Open the capacity tracking sheet in Google Sheets
- Write a row for each window with freed slots, the count, and the time
- Record whether the release is still pending or already approved
- Keep a running log so patterns across the day are visible
Done when The sheet records every window with freed capacity and its release status.
-
3
Telegram - post the box office and draft the release
WebRun posts the box office and flags the drafted release in Telegram. - Post the box office Telegram channel a note of which windows have freed capacity
- State the freed slot count for each window and that a release is drafted
- Ask a manager to approve the release before the slots go back on sale
- Confirm in the thread once a manager has approved and published a release
Done when The box office has a Telegram note of freed slots with the drafted release flagged for approval.
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 put slots back on sale on its own?
No. WebRun drafts the slot-release and flags it for a manager in Telegram, but the slots only return to public sale once a manager approves and publishes the release. The capacity log and the Telegram note are internal and post automatically.
How does it know capacity has actually freed up?
It compares each window's live booked count against its cap in Parker every hour and only flags a window that was sold out and now has open slots, so a release is only drafted when real capacity has genuinely opened.
What if the window fills again before approval?
It rereads Parker each hour, so if bookings refill a window before the release is approved, that window drops off the pending list and the sheet is updated, avoiding an oversell.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.