Automatic O-Valet Request Queue Alerts
Every few minutes, WebRun checks the open vehicle request queue in O-Valet, and the moment the count crosses your threshold, posts an alert to the valet Slack channel and texts the on-duty lead, so extra drivers get pulled onto the stand before guests start piling up at the podium.
How do I get alerted before the valet request queue backs up?
WebRun checks the open vehicle request queue in O-Valet every few minutes, and the moment open requests cross your threshold, typically 5 at once, it posts an alert to Slack naming the count and longest wait, then texts the on-duty lead so extra drivers get pulled onto the stand before guests start piling up at the podium.
- Backed up queues get flagged within 5 minutes of crossing your threshold
- On duty leads are texted once per rush, never spammed
- Extra drivers get pulled in before guests wait at the podium
Built for hotel valet operations · valet parking companies · valet shift managers · event valet 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
o-valet.comin a real browser with your saved login - no setup, no API keys. -
1
O-Valet - check the open request queue
o-valet.com
WebRun opens O-Valet to check the open request queue. - Open O-Valet and count requests currently open, meaning requested but not yet retrieved
- Compare the open count against your threshold, typically 5 or more at once
- Note how long the oldest open request has been waiting
Done when The current open request count and the oldest wait time have been checked against your threshold.
-
2
Slack - alert the valet team
slack.com
WebRun opens Slack to alert the valet team. - Post an alert to the valet operations channel naming the open request count and the longest wait
- Skip posting again if the queue was already flagged in the last 10 minutes
Done when The valet channel has the current queue alert, if the threshold was crossed.
-
3
Twilio - text the on-duty lead
twilio.com
WebRun opens Twilio to text the on-duty lead. - Text the on-duty lead the open request count so extra drivers can be pulled in
- Only text again once the queue has cleared and then backs up a second time
Done when The on-duty lead has been texted about the backed up queue.
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 pull in extra drivers on its own?
No. WebRun only alerts your on-duty lead by Slack and text. Calling in an extra driver or reassigning staff stays a decision your team makes.
What counts as the queue backing up?
Whatever threshold you set, typically 5 or more open requests waiting at once. Below that, nothing gets posted.
Will the same backup trigger repeated alerts?
No. It only alerts again once the queue has cleared and then backs up a second time, so your team is not spammed during one long rush.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.