Catch key location mismatches before they become lost keys
Every few minutes, WebRun checks every key logged in O-Valet's key board against the slot its ticket expects, and the moment one does not match, posts an alert to Slack and texts the on-duty supervisor with the ticket, expected slot, and actual slot, so it gets corrected before a driver goes looking for a key that is not where the system says.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch valet key location mismatches before a key goes missing?
WebRun checks every key logged in O-Valet's key board against the slot its ticket expects, every few minutes. The moment a key is logged into the wrong slot, it posts an alert to Slack and texts the on-duty supervisor with the ticket number, expected slot, and actual slot, so the mismatch gets corrected right away instead of turning into a lost key search when a guest asks for their car.
- Key mismatches get caught within minutes, not when a guest is waiting
- Supervisors are texted once per mismatch, never spammed
- Lost key searches drop because slots get corrected early
Built for hotel valet operations · valet parking companies · valet shift supervisors · parking garage operators
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 logged key locations against tickets
WebRun opens O-Valet to check logged key locations against tickets. - Open O-Valet and check every key's logged slot against the slot its ticket expects
- Flag any ticket where the logged location and expected location do not match
- Note the ticket number, expected slot, and actual logged slot for each mismatch
Done when Every logged key location has been checked against its expected slot.
-
2
Slack - alert the on-duty supervisor
WebRun opens Slack to alert the on-duty supervisor. - Post an alert to the valet channel naming the ticket, expected slot, and actual slot
- Skip mismatches already posted in the last 10 minutes
Done when The valet channel has an alert for every current key location mismatch.
-
3
Twilio - text the supervisor directly
WebRun opens Twilio to text the supervisor directly. - Text the on-duty supervisor the ticket number and slot mismatch directly
- Only text once per mismatch, not again while it remains uncorrected
Done when The on-duty supervisor has been texted about every current mismatch.
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 move or relog the key itself?
No. WebRun only flags the mismatch between the logged slot and the expected slot. Physically finding and correcting the key stays with your team.
What counts as a mismatch?
A key logged into a different slot in O-Valet's key board than the slot its ticket expects, whether from the wrong hook or a scan error.
Will the supervisor get texted repeatedly about the same key?
No. Each mismatch is texted once. It will not text again about that same ticket while the mismatch remains uncorrected.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.