WhatsApp chaos at the front desk: how to bring order

Conversations with guests come into order when every arrangement has one place where it's kept, seen by the whole team, and when it's clear who is leading a conversation right now. As long as bookings live in private chats, pinned messages and the manager's memory, losses are inevitable. Below we look at where exactly they arise, what is worth keeping, and how to set up a shared log and the handover of conversations between staff.

Where bookings get lost

The typical picture: the venue has a WhatsApp number, and it's used like a personal one. The manager chats with guests from the work phone, the owner answers regulars from their own, and someone else discusses something in Telegram. Bookings are written in a notepad, in notes on a phone, or stay only in the chat.

Where exactly the losses arise:

• The shift ended, and the phone left with the manager. All the arrangements only they knew about stayed with them.
• Two people lead the conversation. The guest gets “yes, of course” from the owner, the manager doesn't know about it and confirms the same table to another guest.
• A message sank. On a busy evening a request falls to the bottom of the list, and the answer comes a day later or not at all.
• The arrangement never reached the log. It was confirmed in the chat but not copied into the book.
• A detail got lost in a long conversation. The guest asked for a table by the window and a cake at nine. Finding that a week later in a stream of messages is almost impossible.

None of these reasons has to do with people being lazy. It's the consequence of using a tool for personal communication as a work log. The related problem of requests outside the shift is covered in the article about booking requests in the evening and at night.

What needs to be kept

Keeping the whole conversation word for word is pointless, but there's a set of details that is costly to lose. It can be laid out as a short checklist for each guest:

1. Who it is: name and phone number.
2. What was agreed: date, time, number of guests, table or specialist.
3. Special wishes: the occasion, a cake, flowers, a high chair, allergies.
4. The terms you stated: cancellation rules, how long the table is held, deposit terms if there are any.
5. History: whether they've been before, any no-shows, their favourite table.
6. Who answered: the member of staff, so details can be checked.

Some of this is best kept on the booking card, some on the guest card, and long conversations in the shared conversation log, where you can go back for the exact wording. What matters is that these three places don't contradict each other.

One honest caveat about data: keep what's needed for the work and no more. The less clutter on a card, the easier it is to keep order, and the fewer questions about personal data.

An example: what happens without a shared place

On Friday evening a guest writes to the owner: “Please confirm a table for Saturday, it's a birthday.” The owner answers “yes” and forgets to tell the manager. On Saturday the same table is promised to another group through an ordinary request. Nobody made a mistake out of malice: each acted on what they saw. There's only one way to fix this: the confirmation must be visible to everyone who takes bookings and be recorded at the moment it's given.

A shared conversation log

The solution lies on one plane: all conversations with guests must land in a shared place accessible to the team, rather than living on separate phones.

What you can do without special software:

• get a separate work number and don't answer from personal accounts;
• agree that a confirmed booking goes into the shared log at once;
• keep a short note on each booking: what was promised to the guest;
• keep standard answers (address, menu, cancellation rules) in one document, so that everyone answers the same way.

This approach has a limit: when there are many requests, copying by hand from the chat to the log starts to lag, and the losses return.

In the GuestKeepr virtual front desk the dashboard's Conversations section takes care of this. It holds all the guests' conversations with the bot from the connected channels, Telegram and WhatsApp, with search and filters. Any member of staff with the right permissions opens a conversation and sees what the guest has already been told. A booking the bot created goes into the dashboard at once, and there's no need to copy it from the chat by hand. Once the channels are connected, the team works with one list rather than several phones.

Handing a conversation between staff

Even with a shared log, a question remains: who is answering the guest right now? Until it's settled, the guest gets two different answers or none.

Simple handover rules:

1. A conversation has one lead. If you've joined a conversation, say so in the work chat or note it on the card.
2. When handing a conversation over, leave a note. Two lines: what was promised and what's left to do.
3. Don't discuss bookings in private messages between staff. Arrangements must end up where the shift will see them.
4. Assign someone for difficult cases. Holidays, large groups, complaints: these are decided by a manager or the owner, and the person on the front desk hands the whole conversation to them.

If you use a bot, one more participant joins the conversation, and the line between it and a person must be clear. In GuestKeepr it works like this: when a question goes beyond its limits, the bot hands the conversation to a person, and the staff get a notification in Telegram. A member of staff can take over the chat and answer from the dashboard. While a person leads the conversation, the bot stays quiet. If the member of staff is silent for 12 hours, the bot returns to the conversation. This way the guest doesn't get two answers at once, and the conversation doesn't hang without a lead. More on what to give the bot and what to leave to people in the article AI or human front desk.

The bot's limits should be named honestly: it doesn't take payments, doesn't handle phone calls and doesn't send booking reminders. Difficult and unusual cases stay with the staff.

How to bring order in a week

If everything lives in private chats now, don't try to change everything at once. A realistic plan:

1. In the first days, write down where requests arrive today: which numbers, which accounts, whose phones.
2. Choose one place that will become the main booking log, and agree that a confirmed booking goes there at once.
3. Put together a shared document with standard answers: address, opening hours, menu, cancellation rules.
4. Assign someone responsible for each shift and describe how a conversation is handed over.
5. A week later, look at which bookings still slipped past the log, and adjust the process.

Access rights

A shared log doesn't mean “everyone sees everything”. The same conversation doesn't have to be accessible to a waiter, a trainee and the accountant.

A sensible division looks like this:

• The owner sees everything, including the settings and the activity log.
• The manager works with bookings, guests and conversations.
• The host or front-desk person keeps bookings and answers guests.
• Other staff get only what they need on the shift.

In the GuestKeepr dashboard, permissions are assigned by role, staff are invited by email, sign-in with Google is possible, and PIN sign-in works on shared tablets. The log shows who did what, so the sequence can be reconstructed in a disputed situation. Venues' data are isolated from each other: your conversations aren't visible to other venues. And if a guest asks for their data to be deleted, the owner can erase it completely.

If you're building order by hand, the idea is the same: decide who may see and change what, and write it down in one document.

Frequently asked questions