A double-booked table: how to rule it out

A double booking happens when two people take requests for the same table and can't see each other. You can rule it out in two ways: agree on rules so that the mistake has nowhere to arise, or hand the check over to a system that simply won't let overlapping bookings through. Both ways together work best.

Why double bookings happen

The cause is almost always the same: information about availability sits in several places. The manager writes a booking in the notebook, the host takes a call, and someone else answers a guest in a personal messenger. Each looks at their own source and is sure the table is free.

Typical scenarios:

• Two points of entry. A booking was taken in one place and didn't reach the other.
• Writing it down late. It was agreed verbally, to be written “later”, and forgotten.
• A change of people. One manager left, and the next doesn't know about the arrangements in their chats.
• A change without an update. The booking was moved to another time, the old slot wasn't freed, and nobody checked the new one.
• Different ideas about duration. One person thinks guests stay two hours; another assumes three.

The last point is often missed. A double booking can be not only for the same time but also an overlap: the first group is still sitting, and the second is already expected at the same table.

Manual records and mistakes

A paper book and a shared spreadsheet work while there are few requests and one person takes them. As soon as a second manager, a messenger and night messages are added, the chance of a mistake grows.

The weak points of manual records:

1. The check depends on attentiveness. On a peak evening a person gets distracted, and the check is skipped.
2. There's no single view. To understand whether a table is free at 21:00, you have to put several records together in your head.
3. There's no lock. Nothing stops a second booking being written over the first.
4. The mistake surfaces late. It's seen on the day of the visit, when two groups are standing at one table.

We wrote about the general drawbacks of paper logs in the article about replacing the reservation book. And about how requests get lost in private chats, in the piece about WhatsApp chaos at the front desk.

Rules that help without any system

Even without software you can reduce the risk:

• One log for everyone. All bookings are written in one place; personal notes don't count.
• Write it down before confirming. First enter the booking, then answer the guest “confirmed”.
• A standard duration. Agree how long a standard visit takes the table, and spell out exceptions for large groups.
• A buffer between bookings. Leave time for clearing and resetting the table.
• A check before the shift. Five minutes to look through all of the evening's bookings, especially the changes.

These rules don't make a mistake impossible, but they reduce the occasions for one.

A quick check of your process

Answer a few questions about your venue. Every “no” shows a place where a double booking can arise.

• Do all bookings, from any channel, go into the same log?
• Can you see in five seconds whether a particular table is free at a particular time?
• Does every member of staff know how long a table is taken by default?
• Are changes and cancellations recorded as carefully as new bookings?
• Does the shift have a shared view of the evening before opening, rather than a set of personal notes?
• What happens when a booking is taken at night, when nobody is on shift?

The last question is especially unpleasant. Night messages are usually handled in the morning, and it's in the morning that the manager writes in a booking from memory without checking what was recorded during the day. That's why the overlap check shouldn't depend on one particular person's tiredness and memory.

Controlling overlaps

It's most reliable when the check doesn't depend on a person. The rule is simple: if a table is taken for some period, a second booking for an overlapping time isn't created, whoever tries to enter it.

What such a check must be able to do:

• look at the interval, not the exact start time: a booking at 20:00 and a booking at 21:00 overlap if a visit lasts longer than an hour;
• work the same for all sources: the manager in the dashboard, the host on the tablet, the bot in the messenger;
• refuse clearly: the person or the bot must get a clear “this table is taken at this time” and offer another option;
• check when moving a booking, not only when creating one.

An example. A guest writes at 23:40 that they want a table by the window tomorrow at 20:00. The window table is already taken from 19:30 to 21:30. The right reaction: say that this table is taken and offer another time or another table, rather than creating a second booking “just in case”.

A booking whose guests are already seated

A separate case: the booking is under way. The guests have come and been seated, and at that moment someone in the system presses “move” or “cancel”, for example by mistake or because of another guest's call.

Protection is needed here: a booking whose guests are already seated shouldn't be as easy to change as a future one. If a booking can be cancelled by accident in the middle of dinner, the table becomes “free” on paper and taken in reality again, and that's a direct path to new confusion.

A rule worth adopting even when working by hand: a seated group is protected. Any changes to it are made by the responsible manager, and only deliberately. How to make it visible who is at which table right now is covered in the article about seating guests and the live floor.

Changes without confusion

Changes are what most often lead to duplicates, because moving a booking changes two slots at once: the old one is freed and the new one is taken.

A checklist for moving a booking:

1. First check the new time for the table.
2. If it's free, move the whole booking rather than creating a new one on top of the old one.
3. Make sure the old time has been freed.
4. Tell the guest the new date and time.

The last step is mandatory. If the manager moved a booking and the guest doesn't know about it, you'll get a no-show and a conflict. Tell the guest in writing, in the same messenger where you were talking, so that there's a record.

What to tell the guest if the table is taken

A refusal is also part of the service. A bad answer: “Unfortunately, we're full.” A good answer gives a choice:

The window table is already taken at that time. I can offer the same table at 18:00 or another table in the room at 20:00. Which suits you better?

A short three-step template: name the reason, offer two alternatives, ask which one suits. It works both in conversation and in writing. The guest hears that they haven't been turned away but are being helped to find a solution.

How it's done in GuestKeepr

In the GuestKeepr virtual front desk, a double booking of one table for overlapping times is impossible: the control sits at the database level, not in a member of staff's attentiveness. This applies both to bookings the bot creates and to those entered in the dashboard.

A booking whose guests are already seated can't be cancelled or moved. When the staff cancel or move a future booking, the guest gets a message in their messenger if they have written to the bot. In WhatsApp this is possible within the 24-hour message window.

The limits are worth naming directly. GuestKeepr doesn't send guests reminders of an upcoming booking and doesn't take prepayments. It doesn't guarantee that guests will come; it only guarantees that one table won't be given to two groups for the same time. The length of a visit and the buffer between bookings are set by the venue.

Frequently asked questions