Do guests need the Turnli app?
No. Public join, reservation, and private status experiences are browser-based.
Reservations, walk-ins, arrivals, seating, guest updates, and manager attention stay connected so the host team can run the room without jumping between disconnected tools.
Each step stays connected so the host can move from demand to arrival to seating without losing the party’s context.
Review reservations, queue settings, floor readiness, and the day’s operating context.
Bookings remain owned by Reservations while becoming visible to the broader shift.
Queue owns the live wait, party order, readiness, and return state.
Arrival attaches to the right reservation or queue context instead of creating a disconnected record.
Floor owns table state and seating decisions.
Open, seated, and turning tables inform—not replace—the host decision.
Customer status and messages stay separate from internal operations.
Today surfaces what matters and routes back to Reservations, Queue, or Floor.
Reservations, Queue, and Floor stay connected while each screen remains focused on the job the team is doing there.
Bookings, arrival context, reservation lifecycle
Wait order, readiness, return state
Tables, seating, floor state
Private status and communication keep people informed while internal capacity, notes, resources, and management controls remain staff-only.
Enough information to begin the journey without exposing operational internals.
Place, time, and updates are tied to the customer’s own ticket or reservation context.
Staff can understand the connected history without creating a second mutation owner.
Today surfaces wait pressure, arrival issues, capacity signals, and failures so managers can quickly open the part of Turnli that needs attention.
See the workflow in the demo, then choose the plan that matches how much operating depth the host team needs.
No. Public join, reservation, and private status experiences are browser-based.
Yes. The restaurant queue can operate without turning on digital table assignment; Floor can be used when the workflow needs it.
When the applicable reservation and Floor capabilities are available, Turnli carries booking and arrival context into the host workflow instead of creating a separate list.
Yes. Free is a smaller complete Turnli product. Plus and Pro add deeper operating systems as the business needs them.
These capability pages explain the product behavior and boundaries in more detail.