No-shows, deposits and cancellations

Naming no-shows on social media: is it wise?

Should a restaurant name no-show guests on social media? The defamation and UK GDPR risks, why it backfires, and posts that work without naming anyone.

Ava research teamPublished 6 min read

On this page
  1. The temptation
  2. The defamation risk
  3. The data protection risk
  4. Who else reads the post
  5. What about posts without names?
  6. Posts that actually reduce no-shows
  7. Say it to the guest, not to the internet
  8. If a guest posts about you
  9. Repeat no-shows need a process, not a post
  10. Give staff a simple social media rule
  11. A better story to tell
  12. Frequently asked questions
  13. References

Key takeaways

  • Naming a no-show guest publicly risks a defamation claim if you get any detail wrong and almost certainly misuses booking data under UK GDPR.
  • The booking name and number were collected to manage the booking; publishing them is a different purpose the guest never agreed to.
  • Prospective guests research venues online, and a post attacking a customer is read by them as well as by your fans.
  • Posts about the cost of empty tables, thanks to guests who cancel and a clear policy explainer work better, with none of the risk.

The temptation

After a Saturday with three empty tables, a photo of the unused place settings and the name on the booking can feel like justice. Some of these posts get shared widely, and a few venues have become briefly famous for them. What the shares do not show is the follow-up: the guest who says they cancelled by phone, the person with the same name who gets abuse, the complaint about personal data, and the reviews from people who have never visited.

There are better ways to make the point. First, the risks.

The defamation risk

In England and Wales, a statement is not defamatory unless its publication has caused, or is likely to cause, serious harm to the reputation of the person it is about[1]. Calling a named guest a no-show, or implying they are rude or dishonest, could cross that line if it is wrong or exaggerated, particularly if it spreads. Scotland has its own defamation statute with a similar serious harm threshold.

You might be confident you are right. But bookings are messier than they look: a platform error, a cancellation call that went to an unattended phone, an assistant who booked under their manager's name, a guest who arrived at a different branch. Proving every detail is costly, and the guest only needs to raise doubt for your post to look like a mistake.

The same law cuts both ways. For a business that trades for profit, harm to reputation is not serious harm unless it has caused or is likely to cause serious financial loss[1]. An angry post about your venue from a guest is usually best answered calmly, not with a counter-attack.

The data protection risk

Guests give their name and phone number to make a booking. UK GDPR requires personal data to be collected for specified, explicit and legitimate purposes and not further processed in a way incompatible with those purposes, and to be limited to what is necessary[2]. Publishing a guest's name to criticise them is not what the data was collected for.

Nor is there an obvious lawful basis. Legitimate interests applies only where those interests are not overridden by the individual's interests or rights[3], and a business's wish to shame a customer publicly is unlikely to outweigh that person's interest in not being named online. A complaint to the ICO is a real possibility, and a distraction you do not need.

Who else reads the post

Your posts reach people deciding whether to book with you. Guests do their homework: 91% of consumers in England, Wales and Northern Ireland had heard of the food hygiene rating scheme and 55% had checked a business's rating in the previous 12 months[4]. People who check a hygiene rating before choosing will also read your social media.

How consumers engage with food hygiene ratings, 2025Consumers in England, Wales and Northern Ireland. Guests look you up before they book.
How consumers engage with food hygiene ratings, 2025Comparison. Have heard of the rating scheme: 91%; Checked a business's rating in the past 12 months: 55%.91%Have heard of the rating schemeHave heard of the rating scheme: 91%55%Checked a business's rating in the past 12monthsChecked a business's rating in the past 12 months: 55%How consumers engage with food hygiene ratings, 2025Comparison. Have heard of the rating scheme: 91%; Checked a business's rating in the past 12 months: 55%.91%Have heard of the rating schemeHave heard of the rating scheme: 91%55%Checked a business's rating in thepast 12 monthsChecked a business's rating in the past 12 months: 55%

Source: Food Standards Agency, 2025[4]

Show the data
ItemValue
Have heard of the rating scheme91%
Checked a business's rating in the past 12 months55%

A post naming a customer tells those readers how you might treat them if something goes wrong. Many will choose somewhere else without ever saying why.

What about posts without names?

Posts that describe a no-show without identifying anyone carry far less legal risk. But identification is broader than a name. A photo of the booking sheet, the time and size of the table plus "the birthday party for Jen", or a screenshot with a partly blurred phone number can all point to a real person. If anyone who knows the guest could work out who it was, treat the post as naming them.

How different no-show posts compare on risk.
Post typeRiskBetter alternative
Name and photo of the bookingHigh: defamation and data protectionDo not post
Description that identifies the partyMedium to highRemove identifying details
General: "three tables didn't show last night"LowPair it with how easy cancelling is
Cost explainer with your own figuresLowGood: explains why you hold cards
Thank-you post for guests who cancelNoneGood: rewards the behaviour you want

Posts that actually reduce no-shows

  • The cost story: what an empty table of six means for the kitchen and the team, with your own figures and no guest details.
  • The thank-you: "Thanks to everyone who let us know about changes this weekend. We rebooked every table."
  • The how-to: a 15-second video showing how to cancel from the confirmation text.
  • The waitlist: "Tables free up every Saturday. Join the waitlist and we'll text you."
  • The policy explainer: your notice period and charge in friendly words, pinned to your profile.
  • The people: a member of staff explaining what the prep for a party of ten involves.

Each of these makes cancelling easier or more visible as the normal thing to do. That is what changes behaviour, rather than the fear of being named.

Keep these posts occasional. A venue that complains about no-shows every weekend starts to sound defensive, and regulars begin to wonder whether they are being judged too. One clear explainer pinned to your profile, plus the odd thank-you after a busy weekend, is usually enough.

Say it to the guest, not to the internet

The urge to post usually comes from wanting the guest to know what they did. The direct route does that better. A short, private message the next day reaches the right person, invites an explanation and leaves room for the booking that went wrong for a reason you did not know about.

Example message: "Hi Sam, we had your table for six ready at 8pm last night and were sorry not to see you. If something came up, we understand; next time a quick reply to your confirmation text lets us offer the table to someone else. We'd love to welcome you another evening."

Most guests reply, many apologise, and a few rebook. None of them will be writing about you online the following morning.

If a guest posts about you

Sometimes the post comes the other way, after a charge. Reply once, briefly and politely, and never disclose booking details, card information or the guest's history in public. Example reply: "Sorry to read this. We'd like to look into it properly; please message us with your booking details and we'll get back to you today." Then sort it out privately. For the evidence to check before deciding, see winning disputes on no-show fees.

Repeat no-shows need a process, not a post

For the small number of guests who fail to arrive again and again, publicity is still the wrong tool. A recorded, private process works better: a note after the first no-show, a card hold or deposit requirement after the second, and phone-only bookings if it continues. It protects your tables, it treats the guest fairly and it leaves you with a record you would be happy to show anyone who asked.

Give staff a simple social media rule

  1. No guest details, ever

    Nobody posts names, photos, booking details or descriptions that could identify a guest, on the venue's accounts or their own.

  2. Frustration goes to the manager

    Staff who are angry about a no-show tell the manager, who decides on any follow-up with the guest privately.

  3. One person replies to complaints

    Only a named manager replies to public posts about charges or bookings.

  4. Delete and report mistakes

    If something identifying is posted, take it down straight away and tell the manager.

A better story to tell

Example: a small Italian restaurant posts a short reel of the chef prepping for a party of twelve that later fails to arrive, with the caption "This is what a no-show looks like from our side. Plans change, just tell us. Reply to your confirmation text and we'll rebook you." No names, no booking details. The post is shared locally, cancellations by text rise over the next month, and the restaurant receives no complaints.

For the measures that do the heavy lifting behind a post like that, see a no-show plan for small independents and repeat no-shows: can you refuse future bookings.

Frequently asked questions

Can a restaurant name a no-show guest on social media?

It is unwise. Naming a guest risks a defamation claim if any detail is wrong and is very likely to misuse their booking data under UK GDPR. General posts without identifying details are far safer.

Is it defamatory to say someone did not turn up?

Only if it causes or is likely to cause serious harm to their reputation, but you would have to defend every detail if challenged, and bookings often turn out to be more complicated than they looked.

Can we post about no-shows without naming anyone?

Yes, as long as nothing in the post could identify the guest, including photos of booking sheets, descriptions of the party or partial contact details.

What should we do if a guest complains about us online?

Reply once, politely, without sharing any booking or personal details, and invite them to contact you privately to resolve it.

References

  1. legislation.gov.uk (The National Archives) (2013). Defamation Act 2013, section 1: serious harm (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 5: principles relating to processing of personal data (opens in a new tab) ↑

  3. legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 6: lawfulness of processing (opens in a new tab) ↑

  4. Food Standards Agency (2025). Food Hygiene Rating Scheme (FHRS) Food and You 2 report: wave 11 (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo