What the workspace holds
Status, party size, start and end times, service date and source provider for every reservation, plus a guest profile linked to the venue when the role allows it.
Bookings arrive from providers, phones and inboxes, then get retyped onto the floor. NexTable keeps one reservation list per venue, with the guest context the host is allowed to see.

Teams that take bookings from a provider or by hand, and want guest notes to stay permissioned, venue-scoped and available at the right moment.
Status, party size, start and end times, service date and source provider for every reservation, plus a guest profile linked to the venue when the role allows it.
A reservation belongs to one venue. Provider imports and manual entries land in the same list.
Party size, timing and notes carry into service preparation instead of a printed sheet.
Profiles open in their own workspace and stay behind the permissions that protect them.
Reservations persist per venue and open for anyone holding the reservation permission. Guest profiles live in a linked, permissioned workspace.
StatusReservations persist; guest profiles remain a linked workspace.
Sensitive guest detail stays behind its own permission. A visual floor plan and channel-manager style automations are not part of this service today.
Every service shares the same account, venues and permissions. Open any of them and the context comes along.
We will walk through your reservation flow, the guest notes you keep today, and where the retyping stops.