Product
The whole operation.
Four layers, one system: the guest, the runner, the ops room, and the owner. Each one sees the same live state of every car on the property.
01 · Guest layer
The guest never downloads anything.
The ticket lives on the guest's phone from the moment the car stops. Everything the guest needs, from handover to curb, happens in a browser.
- Digital ticket delivered by SMS, WhatsApp, or QR code
- Live retrieval countdown from request to curb
- Request the car from the phone, before leaving the table
Required in the UAE
Parking validation, built in
Outlets validate digitally, the guest pays only what remains, and every validation is logged per outlet. Validation is a first-class feature of the guest layer, not an add-on.
02 · Runner app
Dispatch without radios.
Runners work from their own phones. The system assigns runs, tracks keys, and captures the vehicle's condition at both ends of the journey.
- Live queue and system-assigned dispatch
- Key tracking: every movement logged to a person and a time
- Phone-based plate read and damage walkaround at handoff
03 · Ops console
The whole lot, live.
One screen shows every car, every runner, and every open request. The shift runs on what everyone can see instead of shouted updates.
- Live lot map and retrieval queue
- Staffing and load, visible in real time
- Incidents and retrieval ETAs on one screen
04 · Owner reporting
The night, on paper by morning.
Owners and operators see what actually happened: how many cars, how fast, what was validated, and what the operation earned.
- Volume and retrieval times, per night and per period
- Damage records with photo evidence
- Validation and revenue reporting per outlet
Operating model
A 200-car night, on paper and on Valparq.
The same evening, run two ways. The comparison describes how each model operates, not measured results from any customer.
| On paper | On Valparq | |
|---|---|---|
| Check-in | A hand-written ticket per car, one queue at the podium | Plate read on arrival, digital ticket sent automatically |
| Retrieval request | The guest walks to the podium or calls the desk | The guest requests from the phone and sees a live ETA |
| Dispatch | Radio calls across the ramp | System-assigned runs by position and load |
| Keys | A pegboard, memory, and goodwill | Every key movement logged to a person and a time |
| Condition disputes | Word against word, settled by the duty manager | Timestamped photo records from intake and handoff |
| End of night | Counting stubs and reconciling cash by hand | Volume, times, validations, and revenue already reported |
- 1.Assumes a single property handling roughly 200 vehicles across an evening peak, staffed with a typical runner team, using paper tickets and radio dispatch as the baseline. These are working assumptions for illustration, not customer data.