All templates

Automatic O-Valet Retrieval Wait Alerts

Every few minutes, WebRun checks every dispatched retrieval in O-Valet against your wait limit, and the moment one runs long, texts the assigned driver a nudge, and if it is still not resolved a few minutes later, alerts the shift lead in Slack with the ticket and how long it has been waiting.

Deploy this workflow Browse all templates
Runs on WebRun · Strict Lockdown policy
Every 5 minutes, all day WebRunorchestrates each step
1 O-Valet time each dispatched retrieval
2 Twilio nudge the assigned driver
3 Slack escalate to the shift lead
In short

How do I get alerted when a valet retrieval is taking too long?

WebRun times every dispatched retrieval in O-Valet, and the moment one runs past your wait limit, typically 8 minutes, it texts the assigned driver a one line nudge. If the ticket is still open 5 minutes later, it escalates to the shift lead in Slack with the ticket number, driver, and total wait, so slow retrievals get caught before a guest starts asking at the podium.

  • Slow retrievals get a driver nudge within minutes of crossing your limit
  • Shift leads only hear about the ones still unresolved after the nudge
  • Guests get their car back before a wait becomes a complaint

Built for hotel valet operations · valet parking companies · valet shift leads · event valet teams

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens o-valet.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    O-Valet - time each dispatched retrieval
    o-valet.com
    WebRun in O-Valet: time each dispatched retrieval
    WebRun opens O-Valet to time each dispatched retrieval.
    • Open O-Valet and check every dispatched retrieval against your wait limit, typically 8 minutes from dispatch
    • Note the ticket number, assigned driver, and space or level for each one running long
    • Track whether a ticket has already been nudged once

    Done when Every dispatched retrieval has been checked against the wait limit.

  3. 2
    Twilio - nudge the assigned driver
    twilio.com
    WebRun in Twilio: nudge the assigned driver
    WebRun opens Twilio to nudge the assigned driver.
    • Text the assigned driver a one line nudge with the ticket number once it crosses the wait limit
    • Only send this first nudge once per ticket

    Done when The assigned driver has been texted once for each retrieval running long.

  4. 3
    Slack - escalate to the shift lead
    slack.com
    WebRun in Slack: escalate to the shift lead
    WebRun opens Slack to escalate to the shift lead.
    • If a nudged ticket is still open 5 minutes later, post it to the shift lead in Slack with the ticket, driver, and total wait
    • Do not escalate tickets that resolved after the first nudge

    Done when The shift lead has every still unresolved retrieval flagged in Slack.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
o-valet.com
ScheduleRuns automatically on this cadence
Every 5 minutes, all day
DeliveryHow each run's result reaches you
Wait time escalation · SMS & Slack
OutputWhat each run produces - A nudge text to the assigned driver, then a Slack escalation naming the ticket, driver, and wait time if it is still unresolved.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does it reassign the ticket to another driver?

No. WebRun only nudges the assigned driver by text, then escalates to the shift lead in Slack. Reassigning a retrieval stays a call your lead makes.

How long before a slow retrieval gets flagged?

Whatever wait limit you set, typically 8 minutes from dispatch for the first nudge, then 5 more minutes before it reaches the shift lead.

Will one slow car trigger multiple texts to the driver?

No. Each ticket gets one nudge. Any further follow up goes to the shift lead in Slack, not repeated texts to the driver.

Keep going

Related templates

Automated O-Valet Daily Cars Parked Report
Every night, WebRun totals how many vehicles were parked in O-Valet that day, breaks the count down by hour and by level, logs it to a running sheet, and posts your manager a Slack digest.
O-Valet›Google Sheets›Slack
Automated O-Valet Damage Claim Status Drafts
WebRun compiles the latest photos, notes, and repair estimate from an open O-Valet damage record, drafts a plain language claim status update, and posts it to Slack for your manager to review, edit, and send. It never contacts the guest or insurer on its own.
O-Valet›Google Sheets›Slack
Automated O-Valet Driver Tip Payout Drafts
Every night, WebRun tallies the digital tips each driver received in O-Valet, drafts a payout summary by driver, and posts it to Slack for your manager to review and approve. It never disburses funds on its own.
O-Valet›Google Sheets›Slack

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.

Deploy this workflow Talk to us