The reservation book: what to replace the paper one with

A paper reservation book is worth replacing with an electronic one when it stops being the only place where bookings live: some are in messengers, some in the manager's head, and some on a sticky note. A good electronic replacement does three things: it won't let a table be taken twice, it keeps the guest's history, and the whole shift can reach it from a phone. Below we look at how the book works, where it breaks, and what to check before switching.

How a reservation book works

The classic book is simple. A page has the date, rows for times and columns for tables or rooms. The manager or host writes in the guest's name, the number of people, the phone number and a note like “birthday” or “by the window”. In the morning the shift opens today's page and sees whom to expect. In the evening they cross out those who came.

This format has real merits, and they mustn't be lost in the switch:

• Everything is visible at once. One spread: the whole evening in front of you.
• Nothing needs to be switched on. No password, battery or connection.
• Quick to write. A pen and a line are faster than any form while the guest is standing at the desk.
• Familiar. A newcomer doesn't need to be told how it works.

So the question isn't “the book is bad” but “at what point does it stop coping with the way the venue takes bookings today”.

Where the book lets you down

Problems almost always arise where the book meets real life.

There's a booking, but it isn't in the book. A guest wrote in a messenger at 23:40, the manager answered “yes, of course” and meant to write it in the book in the morning. In the morning the shift knows nothing about it. We wrote more about this problem in the article about WhatsApp chaos at the front desk.

A double booking. Two people pick up the phone or write in different chats and promise the same table. The book won't stop them: a pen will write anything. How this mistake arises and how to close it off is covered in the article about a double-booked table.

No history. Last month's book is in a drawer. Remembering that a guest likes the window table, or didn't come last time, is possible only if the manager remembers it personally. When that person leaves, the memory leaves too.

Handwriting and corrections. Moving a booking turns into crossed-out lines and arrows. Two hours later even the author isn't sure which entry is current.

One copy. The book lies on the desk. The owner is at home, the manager is in the next room, a second person takes requests from home: none of them can see it.

No trail. Who wrote it in, who crossed it out, who moved it: unknown. There's nothing to settle an “I didn't cancel that” argument with.

No-shows. A “didn't come” mark in the book exists at most as a cross. Putting together a picture of who doesn't come and how often from that is almost impossible. There's a separate article on this: restaurant no-shows.

What you need from an electronic book

Not every replacement is better than paper. A spreadsheet shared by everyone solves the “one copy” problem but solves neither double bookings nor history. Here's a checklist to judge any option by.

1. Overlap control. The system itself won't let you assign a table for a time that's already taken. Not “highlights it in red”, but actually won't allow it.
2. One place for all channels. A booking that came from a messenger, a call or a person at the door goes into one list.
3. A guest card. Name, phone number, past visits, wishes, staff notes.
4. Statuses. Expected, seated, left, didn't come, cancelled. Not just a line, but a state.
5. Access from a phone. The owner and the manager see the evening without coming to the venue.
6. Roles. The host writes bookings in and seats guests but doesn't erase the guest database; the owner sees everything.
7. An activity log. Who did what, and when.
8. A sign-in that doesn't slow the shift down. The shared tablet at the desk shouldn't need long passwords.
9. Data protection. Guests' phone numbers shouldn't sit in a shared document that everyone has a link to.

If an option lacks the first two points, it's more like pretty paper than a replacement. A more general list of criteria, taking channels, languages and pricing into account, is in the article how to choose a table booking system.

The double booking: the main test

If you need to check an electronic book in five minutes, run one test. Create a booking for a table from 20:00 to 22:00. Then try to create a second one for the same table at 21:00. A good system will refuse. A bad one will save both, and you'll find out on the floor when two parties arrive on the same evening.

The second test: what happens if the guests are already seated. Cancelling or moving such a booking by mistake is very easy: you tapped the wrong line. It makes sense when the system simply doesn't allow a booking to be changed once the guests have been seated.

How it's done in GuestKeepr

In short, here's how GuestKeepr covers the list above. It's the GuestKeepr virtual front desk: a bot takes requests in Telegram and WhatsApp, and the staff dashboard serves as the electronic book.

• A double booking of one table for overlapping times is impossible: this is checked at the database level, not just on the screen.
• A booking whose guests are already seated can't be cancelled or moved.
• The Bookings section has every day, the history, moving, cancelling and a “didn't come” mark. The booking card shows the guest's wishes.
• The Tables section shows the live floor: seated guests, walk-ins without a booking, table turnovers and the next booking at each table.
• Guests keeps the cards: the regular-guest mark, favourite table, preferences, staff remarks and visits by day of the week.
• The Log shows who did what.
• Permissions are set by role, staff are invited by email, and people can sign in on the shared tablet with a PIN.
• The dashboard works on a phone as an app (PWA).
• Each venue's data is isolated from the others.

Honest limits: GuestKeepr doesn't take payments or prepayments. It's a bot in messengers plus a dashboard, not an all-in-one machine. If that's exactly what you need, the product will fit. If not, you can still bring order to your book using the checklist above.

Switching without stress

The most common mistake is to throw the book away on launch day. It's better to go in stages.

1. A week of working in parallel. New bookings go into both the system and the book. The manager gets used to it, and you see the discrepancies.
2. Move the future bookings. Everything already written down for the coming dates, enter into the system by hand. There's no need to move the past: the history will begin from day one.
3. Set up tables and zones the way the staff call them. If everyone says “window two”, don't name the table “T-14”.
4. Hand out roles. Host, manager, general manager, owner. Don't make everyone an owner “to keep it simple”.
5. Agree on a rule. Whoever takes a booking enters it in the system at once, not “later”. Without this, any system becomes a second book.
6. Close the book. When there have been no discrepancies for two weeks in a row, take the paper off the desk. Two parallel books are needed only during the switch; after that they do harm.

And finally: don't try to copy the paper one to one. The charm of the book is its simplicity, and that has to be kept: writing in a booking should be no harder than a line in the book. If entering one takes more than a minute, the staff will go back to sticky notes.

Frequently asked questions