Restaurant bookings from the hotel booking: the cross-sell almost no hotel makes

There is a moment in the life of every booking when the guest has already decided to trust your hotel: they just confirmed the room. They have dates, they have a card, they want the trip to go well. At that instant, offering a table at the hotel restaurant costs one sentence. And almost nobody says it, because the dinner booking has no record to live in and everyone is afraid of promising something the kitchen will never hear about.

The moment the guest has already said yes

Think about how a booking reaches your front desk. By phone, by messaging, through the booking engine on your site or through an agency. In every case there is a confirmation: a message, an email, a call back. That confirmation is the warmest conversation you will have with that guest before they walk through the door.

After that moment, everything costs more. When the guest is already in the lobby, they are tired and want the key. When they are already in the room, they have the phone in hand looking for somewhere to eat outside. When they have left, the sale left with them. Cross-selling is not a marketing trick: it is using the one conversation in which the guest is thinking about the whole stay and not only about the bed.

And the question is simple: “You arrive Friday at seven. Shall I book you a table for dinner that night at the hotel restaurant?” Nothing more. You do not need a sales script. You need the answer to have somewhere to be recorded.

Why almost no hotel does it

It is not for lack of will. It is for three operational reasons that repeat in almost every hotel with a restaurant, and none of them has anything to do with the guest.

• The front desk cannot see the restaurant. The rooms system and the restaurant point of sale are two separate worlds, and the person confirming the room does not know whether there is a table Friday at eight, whether the kitchen closes at ten or whether a group has taken the dining room.
• The dinner booking has no record. It gets written in a notebook, sent as a message to the restaurant manager or kept in the memory of whoever answered. And what has no record gets lost, duplicated or arrives late.
• Fear of promising. If the front desk promises a table and the restaurant does not know, the guest shows up and there is no seat. After one night like that, the front desk stops offering. It is a healthy reaction to a broken system.

Notice that all three reasons are solved by the same thing: the restaurant booking living in the same place as the room booking, tied to the guest folio, visible to the front desk, the restaurant and the kitchen at the same time.

What exactly to offer

Not every offer works the same way. What is worth offering depends on the arrival time, the kind of guest and what your restaurant does well. These are the three formats that fit best at room confirmation.

Dinner on the night of arrival

It is the most natural one. The guest arriving at night does not know the city, is tired and is grateful not to have to search. Offer the table with a time, and if your menu allows it, offer an arrival dish or a fixed-price arrival menu too. The decision takes seconds because it solves a real problem.

Breakfast when it is not included

If your rate does not include breakfast, confirmation is the moment to offer it as an add-on with a price per person per night. It posts to the folio from day one and the guest never thinks about it again. If you offer it in the lobby on arrival, you are already competing with the coffee shop across the street.

The stay package with dinner

For weekends, anniversaries or stays of two nights or more, build a package: room plus a dinner for two with a set menu. The price is presented as a single number, the food portion is split internally for the controller’s report, and the restaurant knows from confirmation how many package dinners it has that week.

Where the booking lives: the guest record, not the notebook

This is the difference between a nice idea and an operation that works. The table booking has to be recorded in the guest record, next to the room booking, with date, time, number of people, revenue center and a note if there is anything special. And from that moment it must appear in the restaurant’s table view (Tables and floor) for that day, without anyone typing it again.

When the booking is tied to the folio, good things happen in a chain. The front desk sees at check-in that the guest has a table at eight and reminds them. The restaurant sees that the eight o’clock table belongs to room 214 and not to the street, so the room charge is already prepared (Room charge). The kitchen sees the night with twenty confirmed covers instead of guessing. And the controller, at close, can say how many of the month’s dinners were born from a room booking.

When the booking is in the notebook, the opposite happens. Nobody sees it until the guest reaches the restaurant door and says they were promised a table. If there is room, the problem does not exist. If there is not, the hotel’s promise breaks in front of the guest, and that is the kind of mistake a review does not forgive.

An illustrative example with numbers

The figures below are invented to show the calculation. They are not market data and not from any particular hotel. They help you see the size of the opportunity with your own assumptions.

In the example, incremental sales are 18,000 a month, and the cost of getting them was one sentence per confirmation and a record to write the answer in. Look at the row of dinners you would have sold anyway: it is the one most people forget. Be honest with it, because some of the guests who accept were going to eat with you even without the offer. Even after subtracting it, what remains is revenue that used to walk out to the street.

Now change the assumptions. If your acceptance rate is 1 in 12, new sales drop to 33 dinners. If your average sale per dinner is 450, the total changes. What matters is not guessing the number before you start: it is measuring it after a month with the booking recorded, which is the only thing that lets you know how many dinners were born from a room confirmation.

What each role sees when the system is one

Cross-selling works when every role in the hotel sees its part without asking anyone for anything. This is how it splits.

The most forgotten point is the controller’s. If the dinner booking is tied to the folio, the food and beverage per occupied room report (How food and beverage revenue per occupied room is calculated, and what a good number looks like) can separate what came from the cross-sell from what came from the street. Without that link, you have a total and no way of knowing whether the initiative worked.

The mistakes that turn cross-selling into a problem

• Offering without seeing availability. If the front desk cannot see restaurant tables in real time, it will overpromise on the busiest night and underpromise on the empty Tuesday.
• Recording the dinner outside the folio. A booking in a group chat never reaches the shift close, the kitchen or the controller.
• Offering at the wrong moment. The offer belongs at confirmation, not at check-in. In the lobby the guest wants the key, not one more decision.
• Charging dinner separately from the folio when the guest wanted it on the room. If they accepted dinner together with the room, they expect one bill at check-out.
• Not measuring. If after thirty days you do not know how many dinners were born from a confirmation, the initiative lives on the opinion of whoever proposed it.

What to do this week

1. Write the exact sentence the front desk will say when confirming a room, with time and revenue center, and pin it next to the phone and in the messaging template.
2. Define the three offers: arrival dinner, non-included breakfast and stay package with dinner, each with a fixed price.
3. Agree with the restaurant how the front desk will see table availability by date and time, even if at first it is a block of tables held for guests.
4. Record every acceptance in the guest record, tied to the folio, with date, time and party size. Nothing in a notebook.
5. At the close of thirty days, count how many dinners were born from a confirmation and how much they sold, and compare it with the previous month.

In Inn Restaurant the restaurant booking is recorded in the guest record and shows up in the day’s tables with room and folio, ready to be charged. If you want to see how dinner is offered from the room confirmation, book a 15-minute demo (contact).