Deleted WhatsApp Messages in Restaurants: Bookings, Allergies and Big Orders
Restaurants take a surprising amount of business over WhatsApp: table bookings, large-party deposits, catering orders, and — importantly — allergy and dietary information.
Three of those are commercial. One is a safety issue, and it's the one that makes deleted messages worth thinking about properly.
The allergy case
A customer books a table for eight and mentions a severe nut allergy in the chat. Later they send a correction — a different guest, a different allergen — and delete the first message.
Or they delete the allergy message entirely, having decided to mention it on arrival.
Your kitchen prepared against whichever version the front-of-house team read. If something goes wrong, the question is what you were told and when — and your record has a grey box in it.
This is the case where a deleted message stops being an admin annoyance.
The practical control is not technical: allergy information must be transcribed into your booking system or kitchen ticket at the moment it's received, with the source noted. WhatsApp is the channel; it should never be the allergy record.
But the conversation still needs to survive, because "what did the customer actually tell us" is the question that gets asked afterwards.
The big-order case
Catering and large-party orders are where the money is and where the disputes are.
- Headcount changes. "Make it 40" deleted and replaced with 30 — after you've bought for 40.
- Menu changes. Dish selections revised across a dozen messages with no canonical version.
- Deposit terms. Agreed by message, deleted, then disputed at cancellation.
- Timing. Arrival time revised and deleted, leaving the kitchen plating for the wrong hour.
Food bought for a party that shrinks is a direct loss, and catering margins don't absorb it.
The no-show and deposit case
A customer books a large table, agrees to a deposit or a cancellation policy by message, then no-shows and disputes the charge — with the agreement deleted.
For a restaurant holding a table on a Saturday night, that's the whole evening's revenue on that cover.
What to do
Transcribe anything safety-critical immediately. Allergies, dietary requirements and medical notes go into the booking system the moment they arrive, with a note of where they came from. This is the non-negotiable one.
Confirm every booking in one message.
BOOKING CONFIRMED — Sat 20 Sep, 19:30
Party: 8 guests
Notes: 1 severe nut allergy (guest: Priya), 2 vegetarian
Deposit: £80 received
Cancellation: 48 hours for full refund
Reply YES to confirm these details are correct.
One artefact, in your words, with the safety information restated so an error gets corrected before service rather than during it.
Confirm catering orders as versions. Headcount changes become numbered revisions, each confirmed, so "I said 30" has a timestamped answer. See WhatsApp order changes.
Store the conversation server-side. When the restaurant's number is connected to a platform that saves messages on arrival, a customer deleting their allergy note or their headcount doesn't remove your copy. In Tenashi it stays tagged "Deleted on WhatsApp".
Scope: chats with your own connected restaurant number, from the date you connect it.
Why a shared inbox matters here specifically
Restaurant WhatsApp is usually answered by whoever is near the phone — a manager, a host, someone on a split shift. That produces two problems beyond deletion:
- No handover. The person who took the booking isn't the person working the service.
- No attribution. Nobody can say who agreed to the deposit waiver.
A shared inbox with chat assignment and internal notes fixes the handover problem, which in a restaurant is arguably more valuable day to day than the deletion one.
Pricing is flat, from $18/mo.
Get started → · See every feature
FAQ
A customer deleted their allergy message — what should we do?
Treat it as a live safety issue: confirm the requirements directly with the customer before service rather than relying on the chat. Going forward, transcribe allergy information into your booking system the moment it arrives, since a messaging channel should never be the allergy record.
Should restaurants take allergy information over WhatsApp?
Customers will send it whether or not you invite it, so the practical answer is to accept it and transcribe it immediately into the booking system or kitchen ticket, noting the source. Confirm it back to the customer in writing so errors surface before service.
How do we handle catering headcount changes that get deleted?
Confirm each change as a numbered revision in your own message with the new total and cost, and ask for an explicit reply. That gives every version a timestamp, so a later "I said 30" has a documented answer.
Can we charge a deposit if the customer deleted the agreement?
It's far easier to defend when you can show what they agreed to. A stored record keeps their acceptance tagged as deleted; without one you're relying on your confirmation message and their silence, which is a weaker position.
Who should answer the restaurant WhatsApp?
Whoever is available, provided there's a handover — which is what a shared inbox with assignment and internal notes provides. The common failure is that the person who took the booking isn't working the service.
Does a booking confirmation need to restate the allergy?
Yes. Restating it gives the customer a chance to correct an error before service rather than during it, and it creates a record of what you understood. That's worth more than any recovery method.
Most deleted restaurant messages cost you a headcount. One of them costs more than that. Transcribe the safety-critical ones, confirm everything, keep the thread. Get started.