Platform for hotels and guest houses
Rooms and bookings, guest messages, calls, the POS with receipts and your hotel website run on the same data. Guest, room and bill are shared by every module: a call from the room, a restaurant order and a request from the QR code land where reception manages the stay.
No card to register. Start with one room and a test stay.
On cenaly.ru, nightly charges, inbound iCal import and self-service paid plans are unavailable. OTA channels are in a test environment.
Usually five separate services
Here: one workspace, one set of data
In-room app by QR code
The guest scans the card in the room and the hotel’s remote control opens in the browser. One QR code inside the room — on the wall by the entrance, at the desk or on the nightstand — replaces calling reception, the paper room-service menu and the note for housekeeping.
The QR code lives inside the room — that’s the safeguard
The code is linked to the room and opens its bill, charge-to-room orders and requests, so the plaque goes inside the room, not on the door in the corridor: only someone in the room can see it. On top of that, the server accepts orders and requests only while the room is occupied, and a charge-to-room order goes to the current stay’s folio — guests can’t pick someone else’s bill. QR codes for every room are created on the room board in one click.
Message the hotel
liveAn AI assistant answers from the hotel’s knowledge base; a live operator picks up the conversation in the team chat.
Service requests
liveTowels, cleaning, do not disturb, wake-up, repairs. The guest sees the status of each request.
Order to the room
liveRestaurant, bar and room service charged to the room: the server checks that the room is occupied.
Call-me-back and browser calls
liveGuests don’t need the reception number. Auto-dialling a callback request needs your own PBX; without it the request goes to staff.
Talk to reception in your own language
betaAI translator: the guest speaks or types in their language, staff see the translation, and the guest’s request becomes a service request.
Pre-arrival form and self-service booking
with limitsFrom the link in an email or from reception, guests fill in the form, change dates or cancel under the rate’s terms.
AI concierge in chat
coming soonWill answer about free rooms and prices from the hotel’s published data and call a human.
Room requests
Room service
Contact the hotel
One system — one guest, one room, one folio. Nothing is re-keyed by hand.
Every step runs on a module of the same system, and the data carries forward on its own.
The hotel website on your own domain, or the hotel storefront right after sign-up; SEO and Yandex Webmaster.
Messages from the website and Telegram in one inbox. Calls land on your own PBX with a voice menu; the website offers call-me-back.
Room booking on the hotel website: dates, room type, rate, deposit or prepayment, email confirmation. Or reception puts the booking on the grid.
Pre-arrival form by link; check-in as one operation covering booking, room and folio. The guest receives the room QR code and a link to their bill.
The in-room QR app: chat with the hotel, requests, orders to the room. The room phone: wake-up call *41, outside calls posted to the bill.
Nights, restaurant, bar, services and calls on one folio; check-out closes it and the guest gets one 54-FZ receipt through a cloud cash register or an on-site one.
A thank-you email after departure in the booking language; reviews and newsletters from one guest database.
Each module works on its own, but together they share the guest, the room and the bill.
Maturity follows our product map as of 2 October 2026. “With limits” works with the restrictions listed under limits; “coming soon” carries no promised date.
Room inventory, bookings, guest folios and the reception shift in one place.
Every guest message lands in the team chat, next to the room and the booking.
The hotel’s own PBX, with a room phone that knows the guest, the PMS and the bill.
Stay folio
Check-out → one receipt
One bill per stay, the POS and the receipt — no amounts copied by hand.
Run your whole website: the hotel site on your own domain — or our widgets on any site you already have, with one line of code. Chat, calls and bookings from the website arrive in the same places as everything else.
The hotel restaurant and bar work with the same guest folio.
Reception, housekeeping and maintenance share one team chat and one task board.
Links that separate services don’t have without an integrator.
A call from the room posts itself to the bill
The PBX knows who is staying in the room and adds a “Phone: number, minutes” line using the hotel’s destination rates.
*42 from the room phone sets the PMS status
Housekeeping dials the code and a digit; the room board shows the new status with “phone 101, housekeeper 305” as the author. “Out of order” becomes a repair request.
Reception sees “101 · Surname”
A call from a room arrives with the guest’s name from the PMS, not a bare extension.
Restaurant and bar charge to the room
An order from the QR app or the restaurant POS goes to the stay folio; the POS sees the guest’s bill.
A QR request becomes a team task
The guest’s request lands in the team chat, cleaning and repairs become tasks on the board, and the guest sees the status.
One receipt at check-out
Nights, orders, services and calls close with one receipt; check-out itself closes the stay folio.
Module maturity is checked against our product map; this page is updated with it.
No. The QR code in the room opens a page in the phone’s browser — no app store, no sign-up and no reception phone number needed. Orders and requests are accepted only while the room is occupied.
Inside the room: on the wall by the entrance on the inside, at the desk, on the nightstand or in the guest folder — not on the door in the corridor. The code opens the room’s bill, charge-to-room orders and requests, so only someone in the room should see it. And the server accepts a charge-to-room order only while the room is occupied anyway.
No. Start with the room board and one test stay, then add QR codes in rooms, the phone system, the POS or the website. Modules share the same data, so nothing needs to be migrated between them.
External PMS links are planned. You can run room-service orders or chats on their own, but folios, guests and statuses are not transferred automatically to another PMS — agree on reconciliation first.
On a dedicated Cenaly PBX, each room phone is linked to its room in the PMS. Guests set wake-up calls with *41, housekeeping changes cleaning status with *42, and outside calls are posted to the bill using rates the hotel sets.
The channel manager is in a test environment. Today each room has an iCal occupancy feed: it shares only “booked” and dates, without rates.
One receipt for the whole stay at check-out, under 54-FZ, through a cloud cash register (a paid add-on per register) or an on-site register connected via the bridge.
Your account plan unlocks the modules and sets the room limit per location: Free 5, Basic 20, Premium 100, Enterprise unlimited. Phone numbers, payment providers, hardware and AI usage are billed separately.
Create a hotel account, add a room, check in a test guest and follow the path from a QR request to the receipt at check-out.
Create a hotel accountNo card to register. Start with one room and a test stay.
