Room service that bills itself.
No phone call.
It bills itself. Guests scan the code by the bed, order, and charge it to their room. The ticket reaches your kitchen with the room number on it, and the amount lands on the folioThe running bill attached to a room. Everything a guest charges lands there and settles at checkout..
The reason in-room dining underperforms
It is not the food. It is that ordering means picking up a phone, speaking to someone, and hoping they heard you correctly. Meanwhile the guest is holding the device they use to order everything else in their life.
Ordering room service is the only thing a guest does all week that requires phoning a stranger in the same building.
Which is why most of them do not, and why your F&B revenue looks the way it does.
What happens now
The printed menu is out of date. The guest calls reception. Reception writes it on paper and walks it to the kitchen. Something is wrong with the order. At night auditThe nightly close-off, where the desk reconciles the day’s charges. It is where retyped orders go wrong, at the hour nobody wants to be careful., someone keys it into the PMS by hand and hopes the room number is right.
What happens with Roomchime
The guest scans, browses in their own language, adds a note about the capers, and confirms. The kitchen screen shows the ticket with the room, the guest name and the note. The charge posts to the folio. Nobody retypes anything.
Three moving parts, and you own none of them
A code in every room
One printed card per room, on the nightstand or the desk. Each code knows which room it belongs to, so the guest never types a room number.
They order in their browser
Food, drinks, breakfast for tomorrow, extra towels, laundry, a taxi, a fault report. It opens instantly, in their phone’s language, with nothing to download.
You see it and it bills
The ticket routes to the right team with a response targetThe time you tell us that team should answer in. Miss it and the ticket goes amber on the dashboard.. The amount goes onto the room bill and settles at checkout like any other charge.
- Day 1You sign
- Day 3Menu, prices and photos loaded
- Day 5Codes placed, staff trained
- Day 7Live in every room
That week is the guest app and your dashboard, which do not need your PMS to work. The folio connection runs on your PMS provider’s approval and your own IT sign-off, so budget two to four weeks for the first property. Until it lands you run in manual mode: the order still arrives with the amount ready to post in one tap, and the dashboard tracks every charge that has not hit a bill yet.
housekeeping and the desk
The same order, on the pass
No new hardware: this is a browser tab on whatever is already back there. Confirm an order in the guest view above and watch the ticket land in New, with the room, the note and the amount on it. Accept it here and the guest’s phone updates while you are still reading this sentence.
Bestellingen
Alle teams · 0 of 0 todayNiets in de wacht. Bestel hierboven in het gastbeeld en het komt hier binnen.
Niets hier.
Niets hier.
Everything a guest asks reception for
Room service is the revenue. The rest is why they keep the page open all week, and why your phone stops ringing at 23:00.
You decide when each thing is on
Every menu and every service keeps its own days and hours. Outside them the guest sees it closed, with the time it opens again, so nothing lands in a kitchen nobody is standing in. Move them in the demo above and the phone follows at once.
The part the cheap tools skip
Anyone can put a menu behind a QR code. The question to ask any vendor is what happens to the money. If the answer is a WhatsApp message or a card payment, your F&B revenue now lives outside your PMSProperty management system: the software holding your reservations, rooms and folios. Mews, Apaleo and RoomRaccoon are the common ones here. and somebody reconciles it by hand.
| Approach | Where the order lands | Where the money lands |
|---|---|---|
| Free QR menu tools | A staff WhatsApp, as plain text | Retyped at the desk |
| Guest messaging platforms | A shared inbox | Usually not on the folio |
| POS-based ordering | The till | The folio, via a table, not a guest |
| Roomchime | Your kitchen screen, routed by team | The guest’s folio |
Works with no PMS at all
The printed card carries the room number, so towels, housekeeping, a taxi, a wake-up call and a broken shower all reach the right team without anything being connected to anything. That is most of what reception fields in a day.
What the connection adds
Only your PMS knows who is checked in. Connect it and the guest is greeted by name, sees their real checkout time and a live room bill, and the charge posts itself. Flip the demo above to No PMS to see which lines go quiet.
We connect to your PMS rather than asking you to change it, and we will tell you on the call exactly where that stands for yours rather than putting logos here. Until it is connected, and for anyone running nothing at all, manual mode works from day one: the order arrives with the amount ready to post in one tap, and the dashboard tracks every charge that has not hit a bill so nothing closes unposted.
Who can charge to a room
Every hotelier asks this in the first ten minutes, so here it is up front, including the part that is not airtight.
- 1The scanA long random code on the card in room 412. Not a room number, so there is nothing to guess.
- 2The sessionYour PMSProperty management system: the software holding your reservations, rooms and folios. says who is in 412 right now. No reservation, no folio, nothing to charge.
- 3AskingTowels, housekeeping, a fault: straight through. There is nothing there to steal.
- 4MoneyThe first time something reaches the folio: the surname on the booking. Once per stay.
- Towels and pillows
- Housekeeping and turndown
- Reporting a fault
- Wake-up call and do not disturb
- Room service
- Bar
- Breakfast in bed
- Late checkout with a fee
Ten pillows to 301 at 03:00 gets capped. An order that has not passed the name check arrives flagged on your screen, so someone can refuse it before the kitchen starts. After five wrong attempts the session is over.
What it does not do
A card can be photographed. The session expiring limits how long that is worth anything and closes access after checkout, and those are the realistic problems. It is not proof that the person holding the phone is standing in the room, and we do not sell it to you as such.
The last check is the one you already have
Someone knocks with a tray and sees who opens the door. That is just as true of the phone system you are replacing, which asks nobody anything.
You are the controller, we are the processor. Every property signs a verwerkersovereenkomstThe Dutch data processing agreement between a controller and a processor. The GDPR requires one before any guest data changes hands. before go-live.
Hosting and database in the EU, with the subprocessors named in the agreement.
No analytics and no advertising scripts on the guest page, so no cookie banner between your guest and their dinner. The session cookie is strictly necessary.
Surname, checkout date and folio id purged 30 days after checkout. The allergy note purged when the ticket closes. Order lines kept seven years, for your books.
One price, per room, per month
Minimum €75 a month. Each room above 50 is €2,50.
A 70-room hotel pays €225 a month, which is thirteen club sandwiches off the menu in the demo above. Tablet systems run about €6 per room plus the hardware, and several guest apps want a four-figure setup fee before month one.
€3,50 a room to 50, €2,50 above. About 13 club sandwiches off your own menu, for the whole building.
Founding rate: the next three properties pay half for twelve months, in exchange for a testimonial we can put your name on. Cancel any month.
Scanning it, and opening it from somewhere else
Almost every question we get is some version of “what happens when the code leaves the room”. These are the answers, including the ones that are only as strong as a key card.
Does the guest need an app, or an account?
Neither. The phone camera reads the code and opens a web page, the same way a menu QR in a café does. No download, no login, no password to reset at 23:00.
What if their camera does not read codes?
The card also prints the short link and the room, so it can be typed instead. It is the token in the link that identifies the room, not the camera, so typing it works exactly like scanning it.
Does it need the hotel Wi-Fi?
No. The code carries a web address, not a network. It works on mobile data, on your Wi-Fi, or on the neighbour's. This matters for the guest who never gets past your captive portal.
Does the guest ever type a room number?
Never, and they cannot. The card carries a long random token that we resolve to a room on our side. There is no field to type 301 into, which is precisely why there is no way to type your way into 301.
What if someone opens the bare address without a code?
They get a page that says to scan the code in their room. No hotel picker, no room list, no menu. Every session starts from a token or it does not start.
A guest photographs the card and orders from the train home. Then what?
The session dies on the checkout date your PMS gives us, so after the stay the link is dead. During the stay, they can indeed order from the train, to their own room, at their own expense, with a tray arriving at a door they are not behind. The exposure is a key card left on a café table, and it is capped the same way.
Can a stranger in the lobby scan a card and charge a room?
They can see a menu. Before anything reaches a bill we ask for the surname on the booking, once per stay, and five wrong attempts ends the session. Towels and fault reports never ask, because a wrong towel costs you a towel.
A guest sends the link to a friend in another room.
The friend orders to the first guest's room and onto the first guest's folio, past the same name check. It behaves like lending someone your key: it works, and it works against you, so people do not do it twice.
Two guests in the room, two phones.
Both scan the same card and both get the same room. They see the same live order and the same running total, so nobody orders the club sandwich twice.
The guest is in the bar and orders to the room.
Fine by design. The tray goes to the room, not to the person holding the phone. Ordering the nightcap on the way up is the behaviour we are trying to cause.
A card goes missing from a vacant room.
A room with nobody checked into it has no folio to charge, so the app can show a menu and nothing else. Tell us and that room gets a fresh code, which kills the old one on the spot.
Anything here you want tested against your own property, ask on the call and we will try it live on your code rather than describe it.
Try it before you decide anything
We set the demo up with your own menu and your own branding, free, and send you a code you can scan from your desk. If it does not feel obviously better than the phone, tell us and we will go away.
Founding rate: the next three properties pay half for twelve months, in exchange for a testimonial we can put your name on. Cancel any month.