Zenit is the hotel platform behind the stay link. Front desk checks a guest in, issues a token for that room, and every department — food, laundry, spa, cabs, concierge — publishes straight onto that screen.
Open a desk for the full picture: what staff publish, what the guest sees, and the fields on each request. The house can still add the next one.
Stay card & desk services
Check guests in, assign a room, and issue a stay link scoped to that room.
Food service
Menus and room-service orders, saved on the food desk and shown on the guest screen.
Laundry
Catalog, pickup, and delivery tracked from the laundry desk to the guest's room.
Spa
Treatments and appointment times the guest books from the room.
Fitness
Gym hours, classes, and facility notes kept current on every stay screen.
Cab booking
Rates and categories on the guest screen. Vendors and drivers work from the partner app.
City guide
Neighbourhood notes and local plans the concierge can refresh any time.
Forex
Buy and sell rates plus desk hours, published straight to the room.
Concierge
Request categories the guest fills in with labeled fields, not a blank note.
Banquet
Halls and add-ons configured per property and shown to the guest.
Tickets
Attractions and tours the guest books without calling the desk.
In-room bar
A house list the guest orders from the room, the same way they order from the food desk.
Pool & beach
Hours, towel service, and cabana times published onto the stay screen.
Family
Sessions and ages the family books without calling the desk.
Housekeeping, wake-up, medical, and the service the property adds next. Each one publishes the same way.
Staff publish a module from their desk. The guest stay screen for that room shows the same services, plus the forms the desk already knows how to read.
Treatments and appointment times the guest books from the room.
Spa desk → Spa
Full guest fields, an available room, and a stay token with a link the guest can open.
Phone, email, stay dates, ID, room reassignment, checkout, and desk notes.
Available, occupied, cleaning, or maintenance — visible before anyone is assigned.
Every service arrives with its fields. Accept and Done notify the guest.
Replies land in the guest's stay thread, on the same screen as their orders.
The guest opens /stay/{room}?token=… and sees the assigned room, dates, and the services that desk just published. Housekeeping, wake-up, car, concierge, and medical forms each ask for the fields the desk needs.
When the desk accepts a request or marks it done, the guest stay screen shows that update in the same thread as the order.
Full house: rooms, stays, every desk, and staff access.
Check-in, in-house guests, room status, and stay links.
Menu, hours, and room-service orders for the food desk.
Catalog and pickup orders for the laundry desk.
Transport vendors and drivers sign in on their own accounts, separate from hotel staff.
Transport partner login for the cab company.
Assigned trips on the partner mobile app.
A department updates its module — menu, rates, classes, city notes — and saves once.
The API stores that module and pushes a live update to every open staff and guest screen.
The guest stay screen pulls the new module and redraws it. Same path for requests, chat, and notifications.
Signed-in desks. Each role sees the work it owns.
A token bound to one room and one stay. The link is the login.
Module content, requests, chat, and notifications stay with the property and sync live.