No-shows, deposits and cancellations

Repeat no-shows: can you refuse future bookings?

Can a restaurant refuse bookings from repeat no-shows? Fair rules for flagging guests, UK GDPR limits on what you record, and a ladder of responses.

Ava research teamPublished 7 min read

On this page
  1. Can you refuse a booking at all?
  2. Define a repeat no-show in writing
  3. A flag is personal data
  4. What to record, and what not to
  5. Keep the list secure
  6. Shared numbers, group organisers and other traps
  7. Do not swap lists with other venues
  8. A ladder of responses
  9. What to say to the guest
  10. Never use the list for anything else
  11. Review the decisions you make
  12. A worked example
  13. Frequently asked questions
  14. References

Key takeaways

  • You can generally decline future bookings from repeat no-shows, as long as the reason is the no-shows and never a protected characteristic.
  • A no-show flag is personal data: record facts, not opinions, keep it accurate and delete it after a set period.
  • Use a ladder: a friendly note, then a card hold, then deposits or phone-only bookings, before refusing outright.
  • Keep the list inside your booking system, not in a notebook or group chat, and never use it for marketing.

Can you refuse a booking at all?

A restaurant or pub is generally free to decide whom it takes bookings from. A guest who has booked and failed to appear several times has given you a legitimate business reason to treat their next booking differently, or to decline it.

The limit is discrimination. Under the Equality Act 2010, which covers England, Wales and Scotland (Northern Ireland has its own equality laws), a service provider must not discriminate against a person requiring the service by not providing it[1]. Declining a booking because of repeated no-shows is lawful; declining it because of a guest's race, religion, disability, age, sex, sexual orientation or another protected characteristic is not. Your process should make it obvious which one you are doing.

Define a repeat no-show in writing

Decide the rule before you need it, write it down and apply it to everyone. A rule that depends on how annoyed the manager was that night will be inconsistent, and inconsistency is what makes a decision look personal.

  • Count only true no-shows: no arrival and no contact by a set time after the booking.
  • Do not count late cancellations, which are a different behaviour with a different fix.
  • Exclude any no-show where the venue may have been at fault, such as a wrong date in the system or an unanswered phone.
  • Use a window: for example, two no-shows within 12 months.
  • Reset the count after the window passes.

A flag is personal data

Any note linked to a named guest, a phone number or an email address is personal data, and UK GDPR applies. Three of its principles matter most here: data must be adequate, relevant and limited to what is necessary; accurate and kept up to date; and kept in an identifiable form for no longer than necessary[2].

You also need a lawful basis. For a no-show flag that is usually legitimate interests: processing necessary for your legitimate interests, except where those interests are overridden by the guest's interests or rights[3]. Protecting tables and staff from repeated no-shows is a reasonable interest; keeping a permanent, opinion-laden record of a guest is harder to justify. Say in your privacy notice that you keep booking history, including no-shows, and why.

What to record, and what not to

Record facts that justify the decision and the date it ends. Leave out opinions, guesses and anything about health or background.
Good noteNote to avoid
No-show 14 March 2026, table for 4, no contact, reminder sent 13 MarchTime waster, do not book
Second no-show 2 August 2026; card hold required from nowRude on the phone, probably drunk
Flag expires 2 August 2027Flag kept forever
Booking under same mobile as the flagged guestLooks like the same family, refuse them all

A good test: would you be comfortable if the guest asked for a copy of everything you hold about them and read this note? Guests can make that request, and the note should read as a fair record, not an accusation.

Keep the list secure

A no-show list kept in a shared notebook, a spreadsheet emailed between managers or a staff group chat is easy to leak and hard to correct. Keep flags inside your booking system, where access can be limited and changes are logged.

Hospitality is not immune to security problems: 30% of food and hospitality businesses identified a cyber breach or attack in the 12 months covered by the government's 2025 survey, against 43% of businesses overall[4]. Lower than average is not the same as low.

Businesses that identified a cyber breach or attack in the last 12 months, 2025
Businesses that identified a cyber breach or attack in the last 12 months, 2025Comparison. Food or hospitality businesses: 30%; All businesses: 43%.30%Food or hospitality businessesFood or hospitality businesses: 30%43%All businessesAll businesses: 43%Businesses that identified a cyber breach or attack in the last 12 months, 2025Comparison. Food or hospitality businesses: 30%; All businesses: 43%.30%Food or hospitality businessesFood or hospitality businesses: 30%43%All businessesAll businesses: 43%

Source: Department for Science, Innovation and Technology, 2025[4]

Show the data
ItemValue
Food or hospitality businesses30%
All businesses43%

Shared numbers, group organisers and other traps

Flags attach to contact details, and contact details are messier than people. A family may share one landline; an office manager may book for a dozen different colleagues; a couple may split bookings between two mobiles. Before applying a restriction, check that the no-shows really belong to the same person.

  • A booking under a flagged number but a different name: ask, do not assume.
  • A company organiser whose colleagues failed to turn up: deal with the company, not the individual's personal bookings.
  • A guest who says the earlier no-show was not them: give them the benefit of the doubt and correct the record if needed.
  • A booking made through a third-party platform: check whether the no-show was actually a platform error before counting it.

Correcting a wrong flag quickly is part of keeping data accurate, and it is also simply good manners.

Do not swap lists with other venues

It can be tempting to share names with the restaurant down the road. Sharing a list of individuals with other businesses is a different use of the data from managing your own bookings, it spreads errors beyond your control, and it can harm a person who never had a chance to explain. If you are part of a group and want a shared rule across sites, take advice first and tell guests clearly in your privacy notice.

A ladder of responses

  1. First no-show: a friendly note

    Send a short message the next day: sorry we missed you, hope all is well, here is how to cancel next time. Record the no-show.

  2. Second no-show in the window: card hold

    Future bookings need a card hold with the usual stated charge. Tell the guest this in writing.

  3. Third no-show: deposit or phone-only

    Future bookings need a deposit, or must be made by phone so staff can confirm directly.

  4. Persistent pattern: decline online bookings

    Offer walk-ins or phone bookings only, and say so politely. Keep the decision under review.

  5. Expiry

    When the window passes without another no-show, remove the flag and any restriction.

Most guests never get past the first step. A friendly, specific message often fixes the problem on its own, because many repeat no-shows simply did not realise how easy cancelling was.

What to say to the guest

Keep it factual, private and forward-looking. A message for the second step might read: "Hi Alex, we missed you on 2 August and on 14 March. We know plans change, so from now on we'll ask for a card to hold your bookings, with no charge as long as you let us know 24 hours ahead. We'd love to see you soon." Never reference the decision in public, on social media or in reply to a review.

On the phone, the same tone works: "I can see a couple of bookings didn't go ahead, so we'll just need a card to hold this one. Nothing's taken unless it's a no-show." Most guests accept that without fuss.

Never use the list for anything else

Booking history collected to run reservations should not be turned into a marketing list or a scoring system. Under PECR, marketing emails and texts to individuals need their prior consent[5], and a guest who has been flagged for no-shows will not appreciate an offer timed to their absence. Keep the flag for one purpose: deciding how to take their next booking.

Review the decisions you make

Once a quarter, look at every active flag and restriction. Remove any that have passed their expiry, check that each one rests on the recorded facts, and look for patterns that might suggest unfairness, such as flags concentrated on one booking channel where your own reminders are failing. If one channel produces most of your flags, the problem may be your process rather than your guests.

A worked example

Example: a 50-cover restaurant adopts a rule of two no-shows in 12 months. Over a year it flags nine guests. Seven get a friendly note after the first no-show and never miss again. Two reach the card-hold step; one of those books twice more without problems and the flag expires; the other stops booking. Nobody is banned outright, and the owner has a record of every decision that she would be happy to show the guest.

For the next step in the same cluster, see should you call guests to confirm bookings and what to do when only half the party turns up.

Frequently asked questions

Is it legal to stop a guest booking with us?

Generally yes, if the reason is their booking behaviour, such as repeated no-shows, and the rule is applied consistently. Refusing service because of a protected characteristic is unlawful discrimination.

Can we share our no-show list with other restaurants?

It is best avoided. Sharing a list of individuals with other businesses is a separate use of personal data that needs its own justification and transparency. Take advice before doing anything like it.

How long should we keep a no-show flag?

Only as long as it serves its purpose. Set an expiry, such as 12 months after the last no-show, and remove the flag and any restriction when it passes.

Do we have to tell guests we keep no-show records?

Yes. Explain in your privacy notice that you keep booking history, including no-shows, why you keep it and for how long. Tell an individual guest directly if a restriction is placed on their bookings.

References

  1. legislation.gov.uk (The National Archives) (2010). Equality Act 2010, section 29: provision of services (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. Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑

  5. legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (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