Visit record
Keep the plate, make, model, color, guest details, key tag, space, condition notes and photographs with the visit. Changes use the current record version; conflicts or occupied spaces require attention.
Check-in · keys · retrieval · handover
The guest wants their car.
The team knows what is next.
Connect vehicle check-in, parking space, key tag, pickup request and release in one history. SABSUS Valet helps staff run valet operations and hand over shifts without scattered lists.
Working data requires an account, permissions and relevant connections.
- 01Check-inVehicle · space · key
- 02RequestIndividual guest ticket
- 03RetrievalRetrieving → ready
- 04ReleaseVerification and recorded result
One visit history
Vehicle, space, key and stages stay together
A guest request
An individual ticket with status and pickup request
A clear handover
Remaining vehicles, keys and the shift log
01 / A clear workflow
From arrival to recorded release
A restaurant, hotel or venue with valet service needs shared context. Who accepted the car, where is it parked, who has the key and what is happening with pickup?
- 01
Check in the vehicle
Check the plate and vehicle details, record its condition, key tag and an available space. Add photographs when needed.
- 02
Give the guest a ticket
Prepare an individual QR or link. The guest can see their vehicle's status and request pickup or concierge assistance.
- 03
Manage retrieval
The team sees the request and records retrieval and readiness. Changes remain in the visit history.
- 04
Verify and release
Staff check the ticket, vehicle and presented PIN, then record release. Remaining vehicles and keys are included in shift handover.
02 / Working tools
Tools for the people receiving and returning cars
Parking map
Multiple levels, spaces, zones, lanes and labels help staff navigate. The map represents occupied, blocked and reserved spaces. Drawn entrances and exits are map elements, not connected barriers.
Retrieval queue
Guest requests move through understandable stages: requested, retrieving, ready and released. Staff update the status while history records events and times. This supports human operations, not a fixed-minute pickup guarantee.
Keys and shifts
Open a shift, review remaining vehicles and tags, and hand responsibility to an existing employee. Outstanding vehicles and keys must be resolved before an ordinary shift close. The log helps reconstruct the sequence of actions.
Photos and AI assistance
With OpenAI connected, a front-view vehicle photo can suggest values for empty plate, make, model and color fields. Staff check the suggestions before saving. This is not autonomous entry recognition or damage assessment.
Tickets, labels and history
Print through the available system dialog or a configured supported printing route. A key label does not authorize vehicle release. Review and export history to CSV; metrics depend on the loaded period and records.
The individual guest page shows vehicle status and lets the guest request pickup or concierge help. Operational actions remain with staff. Real ticket links and PINs should not be published or shared with unrelated people.
- Viewing status does not replace release checks
- SMS is prepared for manual sending from a device
- A queued print job does not yet mean a printed ticket
03 / Illustrative scenarios
Three moments when shared context matters
Welcoming a guest
Check vehicle details, record its initial condition and link the key and space. Give the guest a ticket after saving the visit; compare AI suggestions with the actual car first.
A busy departure
Guests request pickup from their tickets while staff manage the queue and readiness. Checking the vehicle, ticket and PIN remains a human step before recording release.
Shift handover
Review remaining vehicles and keys, then hand responsibility to the next employee. For an unclear status, revisit the visit events rather than relying on memory.
These are workflow examples, not customer case studies or promised outcomes.
Requirements and boundaries
Valet organizes the process, not the people
Valet or manager access, a location, map and open shift are required. Automatic parking charges, order or booking linkage from a note, gate control and server SMS delivery are not claimed here. Photo AI and printing require separate setup. A PIN and log do not guarantee fraud prevention, insurance coverage or compliance with all vehicle-custody requirements.
FAQ
The important
questions.
Is this a paid-parking system with barrier control?
No. This page describes a valet staff workflow: check-in, spaces, keys, retrieval, release and shifts. Barrier integration, automatic entry recognition and payment collection are not claimed.
What can the guest do?
Open an individual ticket, view their vehicle's status and request pickup or concierge help. That page does not grant access to the staff parking workspace.
Does AI automatically save the plate and vehicle condition?
No. With a separate OpenAI connection, a photo helps suggest empty plate, make, model and color fields. Staff review them before saving; automatic damage assessment is not claimed.
Is SMS sent automatically?
No. The current workflow prepares a message in the employee's device messaging app for manual sending after guest consent. It is not server SMS delivery or a delivery confirmation.
What printing is available?
The system print dialog and separately configured supported routes, including a compatible native receiver or CloudPRNT. Appropriate device, printer and company setup are required. Queue status does not prove physical output.
Start with your task.
Not another interface.
Explore the right workflow, required connections and access boundaries for your scenario.