Feature Guide · Session History

What a ticket
becomes.

A finished ticket is more than a status: it is the times, people, stand, car, condition, money, and messages that explain one visit.

What it is

One durable, searchable record of a valet visit.

The live ticket accumulates facts as the operation acts. When it closes, the same session remains the source for review, receipts, support, and disputes.

Access is scoped, optional fields remain optional, and retention claims defer to Valletto's published Privacy Policy rather than a number remembered in a guide.

01

Who uses it

The record answers different questions without making every field available to everyone.

Operations

Find the visit and reconstruct the handoffs

Authorized company users search within their company and location scope, then open the same detail drawer used from the live board.

Guest and reviewer

See only the surface intended for that relationship

Guest links expose the guest journey; partner and company views remain separately scoped by authentication and rules.

02

The setup order

Most of the record is created by normal work, not by an administrator building a file.

1 · Intake

Car, stand, ticket, guest channel

Guided Check-In creates the session and attaches available vehicle, guest, ticket, condition, location, and stand facts.

2 · Operation

Statuses, assignments, notes, and messages

Each transition adds times and actors while notes and key-custody or parking-location context can be appended.

3 · Close

Payment and checkout complete the visit

The transaction, receipt context, pickup progression, and final state remain linked rather than becoming a separate orphaned record.

03

The daily loop

Search is a lens over the record, not a second copy of it.

Find

Search by the identifiers the operation already uses

Ticket, plate, vehicle, and available guest/session fields help an authorized user narrow the company-scoped history.

Open

Read overview, condition, payment, and timeline together

The session detail surface keeps the current state prominent and reveals the deeper sections only when needed.

Act

Corrective controls stay permission-bound

Seeing a session does not grant every mutation. Role and server-side checks still govern status, fees, refunds, and other actions.

04

The edge cases

Missing information is shown as missing rather than reconstructed.

No phone or name

The vehicle session still exists

Optional guest details can be absent without erasing the operational timeline, ticket, car, or stand.

Voided or canceled

Terminal states remain explainable

A void or cancellation does not masquerade as a normal checkout; the terminal status and recorded action remain part of the history.

Retention

The policy is the authority

Valletto does not publish a fixed retention promise in this guide. Current handling is governed by the Privacy Policy and applicable account controls.

05

What it deliberately does not do

A complete operating record is not permission to expose it broadly.

No public search

Ticket history is not an open directory

Company, partner, and guest surfaces use different access boundaries. A guessable URL is not treated as authorization.

No invented completeness

Blank fields stay blank

The record reflects what the operation captured; it does not infer a person, plate, payment, or condition fact that was never recorded.

06

What it connects to

The session is the join point for the product.

Live board

The same record while it is open

Status cards and dispatch are the current-state view of this history.

Transactions

The money points back to the visit

A transaction drawer can open the session that produced the charge.

Disputes

Evidence can be assembled from durable facts

Timeline, messages, payment, vehicle, and condition records can be gathered without asking the shift to remember the night.

Staged sanitized Valletto session record with tabs for overview, timeline, payment, and messages and synthetic vehicle, timeline, condition, and payment summaries.

→Staged from the current session detail and search surfaces. All identifiers and amounts are synthetic or masked.

Where Valletto changes the math

The ticket leaves the board. Its explanation does not.

The session record is the operational product left after the physical work is over.

Next: see the guest's three ways back into that same session.

In the productCheck-in, the live board and dispatch run on the phone your valets already carry. The valet app

Keep reading.

Feature GuidesOperations

Express Tickets: Check the Car In Now, Fill In the Rest Later

On a ramp that never stops moving there is no time to collect a plate, a photo and a phone number for every car. An Express ticket checks the car in with one scan and lets the details follow.

Nov 11, 2026 · 4 min readRead
Feature GuidesGuest-experience

The Guest's Ticket, On Their Phone

The page a guest opens from their text was redesigned: where the car is in its journey, how long it has been parked, what is owed, and one obvious way to ask for it back. The link works for the whole visit and for a day after.

Nov 6, 2026 · 4 min readRead
Feature GuidesTechnology

No Signal, No Problem: Working a Garage Offline

Valet happens in the places phones work worst: underground, behind concrete, at a curb crowded with devices. Here is what the Valletto app keeps doing when the connection drops, and what your team should do when it comes back.

Oct 31, 2026 · 6 min readRead

When reading is not enough

See it on your drive.

Twenty minutes on your own property, with your own volumes. We would rather show you the parts an article can only describe.

or keep reading the journal