Reservations
Keep confirmed, arrived, late, and upcoming bookings in the canonical reservation workflow.
Restaurant capability
Bring reservations and the floor into one host workflow.
Turnli connects the booking the guest made with what the room can actually do now—arrival, assignment, table readiness, seating, and the next host decision.
Host workflow
Planned arrival meets live capacity.
Reservations stay reservations. Floor stays Floor. The handoff carries the exact booking and table context between them.
BeforeExpected arrivals
NowTable readiness
NextHost review
ConnectedExact customer and workflow handoffs
TruthfulLive, stale and fallback states stay distinct
PrivateGuest and staff context stay separated
Plan-awareAvailability follows real entitlements
What this capability owns
Built around the operational job, not a feature checklist.
Turnli keeps the system responsible for the work as the authoritative place to act, while related screens carry the exact context into the handoff.
Arrivals
Hand an arrived reservation into Floor without creating a duplicate walk-in record.
Table fit
Review assignment and table readiness with the reservation or waiting party still attached.
Turn context
Use live elapsed time and, when entitled, confidence-aware historical turn context as planning guidance—not a guest deadline.
How the flow works
One customer journey. Clear steps.
The specific workflow changes by business type, but the operating principle stays the same: preserve intent, preserve context, and hand off deliberately.
Plan
See expected arrivals and reservation pressure.
Arrive
Mark the booking arrived and keep the exact reservation in focus.
Assign
Choose the table when one has not already been assigned.
Seat
Seat through Floor with the booking and table handoff intact.
Product guardrails
Useful without pretending to know more than the system knows.
These boundaries are part of the product behavior, not just marketing language.
No auto-clearing
Historical timing never automatically clears a seated table or pressures a guest to leave.
Canonical ownership
Reservation changes remain in Reservations; table state remains in Floor.
Entitlement-safe
Advanced operating intelligence appears only when the workspace is actually entitled to it.
Buyer questions
What businesses usually need to know.
Availability and exact workflows can differ by plan and business type. The working demos are the fastest way to evaluate the current product behavior.
Can Turnli handle walk-ins and reservations together?
Yes. They remain distinct records, but the host workflow can review live queue pressure and reservation arrivals together so the team can make one operating decision.
Does Floor predict exactly when a table will open?
No. Turnli can show elapsed time and, on eligible plans, confidence-aware historical turn windows. Those are planning signals rather than guaranteed availability times.
Can a reservation be seated without a table assignment?
The host can review the arrived reservation, assign an appropriate table, and then seat it through the connected Floor workflow.
Keep evaluating
See how this capability connects to the rest of Turnli.
Turnli is designed as one operating system, so the highest-value proof is how the handoffs behave together.
Try Turnli
See the workflow before creating a workspace.
Open the browser-local demo, then start with the Free plan when you are ready to create a real workspace.