Product
ValoPal is an app the attendant runs on a phone, a web pass the guest opens by scanning a code on that phone, and a console the manager watches. All three write to the same ticket record.
Attendant app
A PIN ties the attendant to the device they are holding. A dead battery, a lost phone or an early finish is handled by the manager: a temporary PIN, tickets moved across, or a remote sign-out that clears the app's data from the device.
Guest web pass
The guest scans a code shown on the attendant's screen and gets a pass in their browser. Nothing to download. Terms are accepted on the guest's own phone, live status shows there, and the receipt arrives there too.
Manager console
Routine cars can be confirmed in bulk. Exceptions — walk-in tickets, recorded booth payments, damage findings — sit in a separate channel that stays visible until someone deals with it.
The record
Where the car is, how it was paid for, and whether a manager has checked it are tracked separately. A car can be ready, paid at the booth, and still waiting on verification — and the record says exactly that.
At the car
Photos and key tags are the parts of a valet shift that people improvise. ValoPal takes both out of the attendant's hands.
A filmstrip with add-another always in reach, so an attendant can shoot the whole car or one bumper without leaving the ticket.
Findings are written to the ticket with the time and a confidence score. The absence of a finding is not a statement that a vehicle was undamaged.
AI-detected — not an inspection
The tag is assigned when the ticket is created and read-only from then on. The attendant reads the tag the app gives them instead of choosing a hook.
Money
Card payments are taken on the pass or on the attendant's device and the receipt goes to the guest's phone. Cash, Venmo and Zelle are recorded booth payments: the attendant logs the amount and a manager verifies it at the booth before the shift closes. Nothing is settled on memory.
Taken against the open ticket. The amount, the method and the time close the ticket together, and tips use the location's presets.
A guest-to-operator payment entered against the ticket and left in the exception channel until a manager confirms it at the booth.
Exception paths
Operations people do not buy the good day. These are the paths that decide whether a stand can actually run on the system.
Look the ticket up by plate or by name, then confirm identity before the keys move. The lookup and who ran it stay on the ticket.
An override sits behind a manager PIN and requires a reason, so a correction is recorded as a correction rather than a silent edit.
The stand is warned before the rack runs out, while there is still time to move cars, rather than at the moment there is nowhere to hang a set of keys.
Pick-up photos attach to the intake photos on the same ticket, so a claim is reviewed as one before-and-after set with times on both halves.
AI-detected — not an inspection
Intake, retrieval and payment recording keep working with a queued banner, and the queue drains in order once the phone reconnects.
A name-based walk-in path keeps the same photos, the same key tag and the same record, marked as the exception it is.