Service & Floor
Run the book. Run the floor.
Host Station is RAYN’s live operating surface. The reservation grid, service ledger and floor plan read the same booking and the same room, so the promise made to the guest can survive the moment service starts.
The operational promise
A reservation is not finished when it is confirmed. It has to survive service.
If a guest chose a specific table, the floor should know it. If tables are combined, the book should know it. If the service moves, the live state should move with it. RAYN keeps the reservation and the physical room connected instead of handing the host a second version of the truth.
01
Host Station
One service. Three live views.
The Host Station is where the reservation becomes an operation. Grid, ledger and floor are three views of the same live service — the same booking, the same table and the same status, without a second version of the room being rebuilt by the host.
- GridRead the service across time and tables — who is due, where the booking sits and what is still available.
- LedgerWork the reservation book as an operational log, moving bookings through the service state instead of treating confirmation as the end of the journey.
- FloorSee positioned tables and live table state on the room itself, then seat against the same inventory the guest booked.
Illustrative interface · one booking model underneath all three views
02
Table control
The booking is attached to the actual room.
RAYN does not stop at “two guests at 8pm”. The booking can carry a specific table, the host can control the room from the live floor, and the inventory model understands when tables belong together.
- Exact table assignmentThe reservation can carry the real table through to service, preserving the promise made during Pick Your Spot.
- Table combinationsConfigured table groups can be joined for larger parties instead of being managed as a note outside the booking system.
- Operator holdsA host can deliberately hold a table out of normal availability when the room needs operational control.
- Floor-plan editingTables and zones can be positioned and maintained so the operating floor reflects the venue rather than a generic list of table numbers.
Illustrative interface · exact assignment, combinations and operator holds
03
Service rhythm
Shifts and turn times keep the room moving.
The same floor behaves differently at lunch, dinner and late service. RAYN carries service periods and venue-level turn timing into the operating view so the host can read the room against the service that is actually running.
- Service periodsShifts define the operating day in the language the venue already uses — lunch, dinner, brunch or the late sitting.
- Turn-time contextVenue-level duration and booking-specific duration feed the live floor so seated tables can be read against the expected turn.
- Live state, not a static planReady, held, seated and service-state changes are reflected on the floor rather than living as an offline floor-plan diagram.
Illustrative interface · venue-level turn context with booking-specific duration where present
04
The guest reaches the floor
The context travels with the booking.
The point of connecting the guest journey to operations is that the information collected before arrival does not die at confirmation. The table, occasion, requests and relevant guest context can reach the team that is actually serving the visit.
- The chosen spot survives arrivalA booking that carries a specific table can remain attached to that table when the guest reaches the Host Station.
- Requirements stay visibleDietary and allergy requirements, special requests and the occasion can travel with the booking instead of being retyped into a separate service note.
- Guest context has somewhere to landGuest intelligence can surface inside the operating flow rather than living only in a CRM screen away from the floor.
Amira K.
2 guests · 20:00 · Terrace
Booking requirements and guest context stay attached to the visit as it reaches the floor.
Illustrative interface · no fabricated spend or behavioural score
05
Operational control
The right view for the person running it.
A reservation platform becomes operational software when access is controlled. RAYN scopes the venue and the role around the person using it, so owners, managers, hosts and analysts do not need the same privileges to work from the same system.
- Venue-scoped accessMembership and permissions are tied to the venue or group rather than exposing the whole estate to every user.
- Operational rolesOwner, group admin, manager, host and analyst roles provide a practical starting point for who can see and operate each surface.
- One platform, different jobsThe host can run service while the owner reads the business and the analyst works the numbers without creating separate copies of the venue.
Illustrative interface · venue and group access enforced by membership
Go deeper into service
Questions
Service & Floor, answered.
Is RAYN a complete reservation system or only a guest-facing layer?
RAYN can run the reservation book and the floor end to end. The Host Station uses RAYN’s own bookings, table assignments, live floor states and service transitions. If a venue is still under contract with SevenRooms or serVme, RAYN can also begin in layer mode and hand the guest to that system’s booking widget to complete the reservation.
What does the Host Station actually show?
Three operational views over the same service: a reservation grid, a service ledger and a live floor plan. Hosts can move between them without rebuilding the picture of the room in another system.
Can the team assign and combine tables?
Yes. A booking can carry a specific table, hosts can seat or reassign against the live floor, and configured table groups can be combined for larger parties. Operator holds can also take a table out of normal sale for a controlled period.
How does RAYN handle service timing?
Venues can define service periods and venue-level turn times. The Host Station reads the booking’s timing and live state so the floor can see what is seated, what is due and what is running beyond the expected turn.
Does every staff member see the same thing?
No. RAYN has venue-scoped roles and permissions for owners, group admins, managers, hosts and analysts, so operational access can be matched to the person using the system.
See the booking become the service.
Walk through the Host Station, the live floor and the operational path from reservation to seated table.
Book a 15-minute walkthrough