After-hours booking requests: how not to lose them

Booking requests don't get lost when they have a single place where they land at any hour and a clear rule about who handles them and when. Messages that arrive at night don't have to be answered the same minute, but they shouldn't wait until lunchtime without a single word either. Below: when requests come in, what you can set up so that the guest doesn't go elsewhere, and when it pays to bring in a bot.

When requests come in

A guest chooses where to go when it suits them, not when it suits you to answer. Typical scenarios, as an illustration:

• At 23:40 on a Friday someone writes: “We'd like Saturday at 20:00, there are six of us.” You closed an hour ago.
• At 8 a.m. on a weekday, a message: “Do you have a table tonight?” The manager comes in at lunchtime.
• In the afternoon, at the height of the shift, a request drowns among other messages: the staff are busy with the guests in front of them.
• On a weekend evening a guest asks about the VIP room, and the person in charge of such questions has the day off.

What all these cases have in common: the guest doesn't know you're closed. They wait for an answer and, when none comes, write to another venue. Bookings are lost here not through anyone's carelessness, but because of the gap between the guest's hours and the shift's.

It helps to write down, at least once, when your requests usually arrive. Scroll through two weeks of conversations: usually one or two “humps” outside the shift stand out, and you can organise taking requests around them.

The auto-reply and its limits

The simplest tool is an auto-reply in the messenger. It says that you've received the message and will answer at a certain time. That greatly reduces the guest's anxiety.

A good auto-reply is short and honest:

Hello! We've received your message. Our manager replies every day from 12:00 to 24:00 and will answer you at the start of the shift. If you need a booking for today, write the time and the number of guests, so that we can help you faster.

What an auto-reply can do: reassure, give your hours, collect the missing details (date, time, number of guests, phone).

What it can't do: check free tables, confirm a booking, agree on special terms. If the auto-reply promises more than the venue will deliver, the guest will be doubly offended. Don't write “booking accepted” if you haven't checked it yet.

Simple rules for an auto-reply:

1. Promise an answer, not a confirmation.
2. Give the exact time when you'll answer.
3. Ask for the main details straight away, so you don't have to ask again in the morning.
4. Don't use the same text for every case. A request for today and a request for next month can have different replies.

The morning sweep of the queue

So that night requests don't pile up, agree on a ritual. For example: at the start of the shift, the manager spends ten minutes going through all the night's messages in order of urgency.

The order:

1. Requests for today and tomorrow first. For them, time costs the most.
2. Then large groups and VIPs. They need details clarified, so better not to put them off.
3. The rest in the order they arrived.
4. Each request gets one of three answers: confirmed, another time offered, information needed from the guest.

Make sure every request has an owner. If two managers answer the same guest at once, the guest gets two different answers. If nobody answers because “someone probably already did”, the request is lost. One line in the work chat is enough: “I'm taking requests from 12 to 14.”

A separate practice: don't leave handled requests in the messenger as the only place they're kept. A confirmed booking must end up in the booking log; otherwise you set the stage for double bookings and confusion.

What to say when there's no room

A separate skill: saying no without losing the guest. If everything is taken at the requested time, don't stop at “we're full”. Offer the nearest free time, another table or another day, and ask whether that would suit. A guest who got an honest answer and an alternative will remember you next time. A guest who got a curt “no” will find another venue. It's worth keeping such prepared answers in a shared document, so that the morning shift answers in the same way.

One inbox instead of private chats

The most common cause of losses is not the night but fragmentation. One request comes to the owner's personal WhatsApp, another to the venue's account, a third to the comments or to the manager's Telegram. Everyone looks at their own.

The solution is simple in principle: all the channels for taking requests are brought into one place where everything can be seen. Once a request is in the shared log, it doesn't matter who is on shift or who has their phone with them.

What a single inbox gives you:

• one list of requests that the whole team sees;
• a shared history of the conversation with each guest;
• the ability to hand a guest to a colleague without retelling the story;
• less chance that someone left without getting an answer.

How to gather the conversations and share out access is described in detail in the article about WhatsApp chaos at the front desk.

When you need a bot

An auto-reply and a morning sweep work well with a small flow. If there are many requests, or they arrive at the most awkward hours, you can't cover them by hand. That's when a booking bot fits.

In the GuestKeepr virtual front desk, evening and night requests are handled like this.

• The bot answers the guest in Telegram and WhatsApp around the clock: it checks free times or places, shows tables or specialists and creates the booking. If the guest sends a voice message, the bot turns it into text (the platform uses speech recognition for this).
• The bot always asks for a name, a phone number, and the place and time. It doesn't confirm a booking it didn't create itself.
• The booking appears in the dashboard at once. The system won't allow a double booking of one table for overlapping times.
• The bot knows the menu and the venue profile: the description, deposit and cancellation terms, dress code, age restrictions, ready answers. It states the terms as text and doesn't take payments.
• If a question is beyond it (special terms, a complaint, an unusual event), the bot hands the conversation to a person. A member of staff gets a notification in Telegram and can take over the chat from the dashboard. The bot stays quiet while a person leads the conversation and comes back after 12 hours of the staff member's silence.
• In the morning the manager opens the dashboard and sees the bookings made overnight, and in the Conversations section can find any conversation by searching.

Honest limits: the bot doesn't make calls, doesn't take payments and doesn't send booking reminders. Everything out of the ordinary stays with a person, while the bot takes on the routine requests that need no discussion. You can read more about what it can do in the article about a booking bot for a restaurant.

If you're not sure whether you need a bot, check one simple sign: how many requests a week you handle outside the shift, and how many of them stay unanswered until the next day. If the answer is “almost all” or “we don't count”, the first step is counting, not buying.

Frequently asked questions