Automated O-Valet Folio Reconciliation
Every few minutes, WebRun compares completed tickets in O-Valet against the matching charge on the guest's hotel folio, flags any ticket whose folio charge is missing, duplicated, or for the wrong amount, logs the discrepancy to a running sheet, and texts the front desk supervisor so it gets fixed before the guest checks out.
How do I catch valet charges that never posted to the guest folio?
WebRun compares every completed ticket in O-Valet against the matching charge on the guest's hotel folio every few minutes. The moment a folio charge is missing, duplicated, or does not match the ticket amount, it logs the discrepancy to a running sheet and texts the front desk supervisor while the guest is still in house, so the charge gets corrected before checkout instead of becoming lost revenue.
- Missing folio charges get caught while the guest is still in house
- Every discrepancy is logged with the exact amount and room number
- Front desk gets texted once per issue, not repeatedly
Built for hotel valet operations · valet parking companies · front office managers · hotel revenue 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 - compare completed tickets to posted folio charges
o-valet.com
WebRun opens O-Valet to compare completed tickets to posted folio charges. - Open O-Valet and pull tickets marked completed in the last check interval
- Compare each ticket's charge against the corresponding line on the guest's hotel folio
- Flag any ticket where the folio charge is missing, duplicated, or does not match the ticket amount
Done when Every completed ticket has been checked against its folio charge.
-
2
Google Sheets - log each discrepancy
google.com
WebRun opens Google Sheets to log each discrepancy. - Append each discrepancy to the reconciliation log with the ticket number, room, expected amount, and what was found on the folio
- Mark a row resolved once the folio charge matches on a later check
Done when The reconciliation log reflects every open and resolved discrepancy.
-
3
Twilio - text the front desk supervisor
twilio.com
WebRun opens Twilio to text the front desk supervisor. - Text the front desk supervisor the room number and discrepancy for any guest not yet checked out
- Only text once per discrepancy, not again while it remains open
Done when The front desk supervisor has been texted about every unresolved discrepancy for a guest still in house.
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 post or correct the folio charge itself?
No. WebRun only flags the discrepancy and texts your front desk supervisor. Posting, adjusting, or removing any charge on the folio stays a front desk action.
What counts as a discrepancy?
A completed O-Valet ticket whose matching folio charge is missing entirely, posted twice, or posted for a different amount than the ticket.
Will it keep texting about the same issue?
No. Each discrepancy is texted once to the front desk supervisor. It will not text again about that same ticket while it remains open.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.