Automated O-Valet Damage Photo Compliance
Every few minutes, WebRun checks every ticket flagged for damage in O-Valet, confirms the required before and after photos are attached, pings the attendant in Slack to complete any missing photos while the guest is still on site, and logs each flagged incident to a running damage sheet.
How do I make sure valet damage tickets have complete photo documentation?
WebRun checks every damage flagged ticket in O-Valet for the required before and after photos every few minutes. If either is missing, it pings the attendant who logged the ticket in Slack, naming the ticket and which photo is missing, and logs the incident to a running damage sheet, so documentation gets completed while the guest is still on site.
- Missing damage photos get caught while the guest is still on site
- Every flagged ticket lands in a running damage log automatically
- Attendants get pinged once, not repeatedly, for the same gap
Built for hotel valet operations · valet parking companies · valet shift supervisors · risk and claims managers
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 damage flagged tickets for photos
o-valet.com
WebRun opens O-Valet to check damage flagged tickets for photos. - Open O-Valet and pull tickets flagged for damage in the last check interval
- Confirm each has the required before and after photos attached
- Note the ticket number, attendant, and which photos are missing, if any
Done when Every damage flagged ticket has been checked for complete photos.
-
2
Slack - chase the attendant for missing photos
slack.com
WebRun opens Slack to chase the attendant for missing photos. - If photos are missing, ping the attendant who logged the ticket in the valet channel
- Name the ticket number and which photo, before or after, is missing
- Skip tickets already complete or already pinged in the last 15 minutes
Done when The attendant has been pinged for every ticket missing a required photo.
-
3
Google Sheets - log the flagged incident
google.com
WebRun opens Google Sheets to log the flagged incident. - Append each damage flagged ticket to the damage log with the date, space, attendant, and photo status
- Mark the row complete once both photos are confirmed attached
Done when The damage log reflects every flagged ticket and its current photo status.
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 contact the guest about the damage?
No. WebRun only chases your own attendant to complete the photo documentation. Any conversation with the guest about damage stays with your team.
What counts as a complete damage record?
A before photo from intake and an after photo from return, both attached to the ticket in O-Valet. Missing either one triggers a Slack ping.
Will the same missing photo trigger repeated pings?
No. Once an attendant has been pinged for a ticket, it will not ping again for 15 minutes, and stops entirely once both photos are attached.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.