A guide to taking a room service order by messaging without room number mistakes

A guest texts from the room: they want a burger and a beer. Ten minutes later, someone in the hotel restaurant reads the message, writes the order in a notebook, asks for the room number, jots it down by hand and shouts it to the kitchen. All of that works until the night when 312 becomes 321, the burger knocks on the wrong door and the charge lands on the folio of someone who never ordered anything.

The room number is the most fragile piece of data in the order

In a street restaurant, the order is tied to a table the server can see. In your hotel restaurant, a room service order is tied to a room nobody is looking at. That number travels through many hands: the guest dictates it, the person taking the order hears or reads it, someone writes it, someone else copies it onto the ticket and the server carrying the tray interprets it. Every hand is a chance to get it wrong.

When the order arrives by messaging, the problem changes shape but does not go away. The guest writes from a phone number the hotel does not know, or one it knows from a previous stay. Sometimes they include the room number and sometimes they do not. Sometimes they give the room of the person they are traveling with. And whoever handles the message has to sort all of that out while answering three other conversations.

The consequence shows up in three places: the wrong guest receiving something they did not order, the right guest still waiting, and the front desk at check-out, when a charge appears that the folio does not recognize. The third is the most expensive, because it almost always ends in a forced comp and an argument in the lobby.

The three mistakes that repeat when the order comes by message

Before proposing the procedure it helps to name the mistakes, because the procedure exists to close them one by one.

• Taking the room number as truth. The guest says 312 and 312 gets written down, without checking that 312 is occupied, that it is occupied by this person and that the stay is still active tonight.
• Confirming verbally instead of in writing. Someone replies “on its way” without repeating what is going, where it is going and what it costs. If there was a misunderstanding, nobody sees it until the tray arrives.
• Transcribing the order twice. Once into a notebook or an internal chat, once onto the kitchen ticket. Every transcription changes a quantity, drops an allergy note or confuses a room.

The three mistakes share a root: the message order is treated as a conversation and not as a transaction. The conversation is friendly, but the transaction is what gets charged. The procedure below turns the conversation into a transaction without the guest feeling it.

Step 1: verify the stay before taking the order

The first move is not asking what the guest wants. It is knowing who they are. Before accepting any dish, whoever handles the message has to confirm that the room exists, that it is occupied today and that the person writing is the one registered in it or someone authorized on the same folio.

1. Ask for the room number and the last name on the reservation. Two pieces of data, not one. A room number gets mixed up; a room number plus a last name almost never does.
2. Check both against the list of active stays the front desk keeps current. If the last name does not match the room, stop and ask, without accusing: “Could you confirm the last name the room is registered under?”.
3. Verify that the stay covers tonight. A guest who checked out this morning and is still in the lobby can order, but their consumption can no longer go to a closed folio: that order is paid on the spot.
4. Confirm that the folio accepts charges. If the front desk flagged the room as cash only, or as a group account with no consumption authorized, the person taking the order has to know before promising anything.
5. Only then ask what the guest would like.

This step sounds slow and in practice takes seconds if the list of stays is at hand for the person taking the order. If that list lives on a screen only the front desk has, the step becomes an internal call, and internal calls at ten at night are the ones that get skipped. The room charge page (Room charge) explains why a free text field for the room number is the root of almost every charge nobody later recognizes.

When the person writing is not the account holder

It happens all the time: the partner writes, the son writes, the colleague sharing the room writes. The practical rule is that anyone registered on the folio can charge, and anyone who is not pays on delivery. The front desk decides who is on the folio; the restaurant only consults it. If the restaurant starts deciding on its own, the argument at check-out is guaranteed.

Step 2: confirm the order to the guest in writing

Once the stay is verified, the whole order is repeated in a single message: dishes with quantities, special notes, estimated delivery time, total with tax and the closing line: “charged to room 312, folio under Ramírez”. The guest replies with a yes. That yes is the document.

The written confirmation does two jobs. Toward the guest, it removes the surprise: they know what they will receive, when and how much will be charged. Toward the hotel, it leaves a trail: if at check-out the guest says they never ordered that, the front desk has the message with their confirmation and the discussion lasts thirty seconds instead of ten minutes.

A fixed rule helps here: nothing goes to the kitchen until the guest confirms. It sounds obvious and it is the first thing skipped when there is a rush. The rush is the reason the burger for 312 ended up in 321.

What the confirmation message must include

• Each dish with its quantity and its note (no onion, medium, no ice).
• The total with tax and, where it applies, the in-room service charge explained as a separate line.
• The estimated delivery time in minutes, not “soon”.
• The room and the last name of the folio it will be charged to.
• A single question at the end: “Shall I confirm it like this?”.

Step 3: the ticket goes straight to the kitchen, never rewritten

The third mistake on the list, the double transcription, is removed by one design decision: the order the guest confirmed is the same object the kitchen receives. No intermediate notebook, no shouting, no group chat where someone copies and pastes. The order is captured once, with the room already verified, and from there the ticket goes to the kitchen screen or printer and the charge goes to the folio.

That changes what the cook sees. Instead of a slip in hurried handwriting, they get a ticket with the time it came in, a verified room, dishes with notes and a clear mark that it is room service, not a table. The kitchen page (Kitchen display) shows how that screen is organized when dining room tickets and room tickets share it.

And it changes what the server going upstairs sees. The tray leaves with a printed slip that says room, last name and contents. If they knock and the last name does not match whoever opens, they have a concrete reason to pause before handing it over.

The messaging assistant as the first filter

Many hotels already receive the order through an automated attention assistant that asks the step 1 questions before a person gets involved: room, last name, check against active stays. When the assistant cannot resolve something, it hands the conversation to a person with the context already gathered. The automated attention page (Automated messaging) describes which part of this flow can be handled without hands and which part stays human, which is the judgment part.

An illustrative example: what a room mistake costs

The figures below are made up to show the calculation. They are not market data and they are not from any property. Picture a 60-room hotel whose restaurant receives about 600 room service orders a month through messaging, and that today does not verify the stay before writing the order down.

The number that weighs most is not in the table: the time of the server who went up twice, the front desk agent who argued at check-out and the review that guest left afterward. But even with the cold arithmetic, in the example a mistake on three of every hundred orders costs per year what an employee would cost for several months. And it is fixed with two questions and one check.

A message script that actually works

Tone matters as much as procedure. The guest does not want to feel interrogated; they want to feel looked after. These lines follow the procedure without the procedure showing.

• Opening: “Gladly. Could you share your room number and the last name on the reservation so I can prepare the order?”.
• If something does not match: “I have the room registered under a different last name. Could you confirm so I do not get the charge wrong?”.
• Confirmation: “Perfect. One classic burger, medium, and one lager, total with tax 310, in about 30 minutes, charged to room 312 under Ramírez. Shall I confirm it like this?”.
• Closing on delivery: “I will sign the slip on your behalf and it stays on your folio. Enjoy”.
• If the stay is already closed: “Your room account is already closed, so we will collect this order on delivery. Cash or card?”.

Notice the room and the last name together in the confirmation. It is the one line the guest reads carefully, because it says how much and to whom. If it is wrong, the guest corrects it before the ticket leaves. That is a control that costs nothing.

How to know whether the procedure is being followed

A procedure nobody measures is abandoned in the second week. Three things can be reviewed every Monday: how many room service orders went to the kitchen without a verified room, how many room service charges were questioned at check-out and how many dishes were remade because of a wrong delivery. If the three numbers fall together, the procedure is alive. If one rises, find out which shift is skipping it.

The front desk plays a part in that review. It sees the questioned charge, and it can tell whether the problem was the room, the amount or a guest who simply did not remember. The front desk page (Front desk) explains which restaurant information the desk should have in view to close every check-out without calling anyone.

What to do this week

1. Review the last thirty days of room service charges questioned at check-out and sort them: wrong room, wrong amount or order not remembered.
2. Put the list of active stays in front of whoever handles the messages, on the same screen where the order is captured, not in another office.
3. Write the standard confirmation message and save it as a template: dishes, total, time, room and last name, one question at the end.
4. Set the golden rule with the kitchen: no room service ticket comes in without a verified room and the guest’s confirmation.
5. Remove the intermediate notebook. If today the order is written in one place and copied to another, decide which of the two disappears.
6. Measure the following Monday the three numbers: unverified tickets, questioned charges and remade dishes.

Inn Restaurant receives the order by messaging, checks room and last name against the hotel’s active stays and sends the ticket to the kitchen from the same order the guest confirmed, with the charge already tied to the folio. The room service page (Room service) shows the full flow, and in a 15-minute demo (contact) you can watch it with a test order from your own phone.