Automated accesso Virtual Queue Wait Time Alerts
Every 15 minutes during operating hours, WebRun checks each attraction's virtual queue wait time in accesso, logs a snapshot to Google Sheets so you have a full day trend line, and pings your ops team on Telegram the instant a queue crosses your posted wait time target.
How do I get alerted when virtual queue wait times spike above target?
WebRun checks every attraction's virtual queue wait time in accesso every 15 minutes, logs a snapshot to Google Sheets for a full day trend line, and messages your ops team on Telegram the instant a queue crosses its posted wait time target, so a spike gets a fast response instead of showing up only in an end of day report.
- Ops hears about a queue spike within 15 minutes, not at the next walk through
- Every attraction's wait time is logged all day for the shift report
- Shift leads see the day's pattern at a glance instead of checking each queue by hand
Built for theme park operations teams · virtual queue managers · guest experience leads · water park ride 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
www.accesso.comin a real browser with your saved login - no setup, no API keys. -
1
accesso - track virtual queue wait times
accesso.com
WebRun opens accesso to track virtual queue wait times. - Pull the current posted wait time for every attraction's virtual queue in accesso
- Compare each one against its posted wait time target
- Note the return time window currently being issued for each queue
Done when Current wait times for every virtual queue are known against their targets.
-
2
Google Sheets - log the wait time snapshot
google.com
WebRun opens Google Sheets to log the wait time snapshot. - Add a new row with the timestamp and each attraction's wait time
- Keep a running column for the day's peak wait time per attraction
- Build the trend so shift leads can see the day's pattern at a glance
Done when Today's wait time snapshot is logged for every attraction.
-
3
Telegram - ping ops on a spike
telegram.org
WebRun opens Telegram to ping ops on a spike. - Message the ops team the moment any queue crosses its posted target
- Name the attraction, the current wait, and how far over target it is
- Send a follow up once that queue's wait drops back under target
Done when Ops has an immediate Telegram alert for every queue that spiked.
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 open more return time slots automatically when a queue spikes?
No. It only alerts your ops team on Telegram and logs the trend to Sheets. Opening additional return windows or capping virtual queue entry stays a decision your team makes in accesso.
What counts as a spike worth alerting on?
Any attraction's virtual queue wait crossing the target you set for it, commonly a set number of minutes over the posted time. You can set a different target per attraction.
Can I see the whole day's wait time pattern, not just the spikes?
Yes. Every check, spike or not, gets logged to the Google Sheet, so shift leads have a full trend line of every attraction's wait time through the day.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.