Valet operations, built at an airport.
The full reservation lifecycle, flight-aware returns, photo-documented intake, two-way SMS in one inbox, and a complete audit trail. Ready for any venue.
Live in production at a Canadian regional airport, and improving every month with the teams who use it.
A walk through Valet
| Ref | Customer | Status | Return |
|---|---|---|---|
| VC-4F2A91 | Sarah M. | Returning | Flight WS 3568 14:35 |
| VC-7B3D04 | James L. | In lot | Hotel checkout 11:00 |
| VC-9A1F22 | Maria R. | In lot | Flight AC 8123 15:10 |
| VC-2C8E55 | David K. | Awaiting drop-off | Stadium 21:30 |
| VC-5D4G77 | Lena T. | Returning | Hospital discharge |
The lot, at a glance
Every vehicle in the lot on one board, with its status and what triggers its return. No calling around to find a car.
Intake, photographed and labeled
Six labeled photos, plus odometer, fuel and condition, captured at handover. A dispute meets documentation, not a memory.
On my way down
Your vehicle will be brought to the arrivals curb. Ref VC-4F2A91.
Running late? We can hold the stall 10 min. Reply here.
Two-way SMS, one inbox
Customer messages and automated replies sit in the same thread, tied to the reservation. A dispatcher can step in any time.
An audit trail with before and after
Every field change is recorded with the old value, the new value, who made it, and from where. Nothing edits silently.
One lifecycle, end to end
Every vehicle moves through the same six states. Staff see where a car is; the customer gets SMS at the moments that matter.
One lifecycle, any venue
Airports trigger on flight arrival, hotels on checkout, stadiums on the final whistle, hospitals on discharge. Same workflow, different return trigger.
Intake that holds up in a dispute
Labeled photos, odometer, fuel and condition at handover. When a customer disputes damage, the record is already there.
Messaging that answers the where's-my-car call
Two-way SMS in one inbox, with automated replies tied to the reservation. Most status questions answer themselves before the call.
Roles and security
Five roles, TOTP MFA, lockout after 5 failed attempts, and masked secrets. Access is least-privilege by default.
Three ways to start
Pricing scales with venues and volume, not per message. Talk to us for a number that fits your operation.
Pilot
For a single venue or a small team getting started.
- One venue
- Reservation lifecycle
- Photo intake
- Two-way SMS
Operations
For a busy airport or multi-venue operator.
- Multiple venues
- Flight-aware and schedule-aware returns
- Per-message cost logging
- Audit trail with diffs
- Template engine
Enterprise
For operators that need scale, roles and support.
- All venues and roles
- Five roles with TOTP MFA and lockout
- Custom integrations
- Priority support and onboarding
Help shape Vectro Valet
We are working with a small number of regional airports, hotels, stadiums and hospitals as design partners. It is a scoped pilot on your own operation, and what you learn with us shapes the product.
What you get
- Hands-on setup and onboarding, done with your team
- Direct access to the people who build Vectro Valet
- A real say in what we build next
What we ask
- A live operation willing to run a scoped pilot
- Honest feedback, including what does not work
- One named contact for check-ins
The five products share one data layer
Each product stands on its own and gets more useful alongside the others. The rest of the family is below.
Questions we hear
See Vectro Valet running
A 30 minute walkthrough in a real airport context, specific to your operation. No slides.