No-Shows, Deposits and Guest Policies

Repeat No-Show Guests: How to Flag and Respond

How to track repeat no-show guests fairly, when to require a card hold on their next booking, and polite wording for flags, warnings and policy notes.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing6 min read

On this page
  1. Why repeat no-shows deserve their own rule
  2. Define a repeat no-show
  3. Record it consistently
  4. A response ladder
  5. Wording that stays polite
  6. When a flagged guest books by phone
  7. Why it matters more when demand is high
  8. Fairness and privacy
  9. Clearing a flag
  10. Check that the rule is working
  11. Example: one guest, three steps
  12. Frequently asked questions
  13. References
No-Shows, Deposits and Guest Policies: Repeat No-Show Guests: How to Flag and RespondArticle coverNO-SHOWS, DEPOSITS AND GUEST POLICIESRepeat No-Show Guests:How to Flag and RespondAva for RestaurantsInsightsNo-Shows, Deposits and Guest Policies: Repeat No-Show Guests: How to Flag and RespondArticle coverNO-SHOWS, DEPOSITS AND GUEST POLICIESRepeat No-ShowGuests: How to Flagand RespondAva for Restaurants

Key takeaways

  • Flag on records, not memory: for example, two no-shows without notice within 12 months.
  • Respond in steps: a friendly note, then a card hold on future bookings, then a manager decision.
  • Diners accept card guarantees as fair[1], which makes a hold the natural response to a repeat no-show.
  • Apply the same rule to every guest, and keep only the booking facts you need.

Why repeat no-shows deserve their own rule

Most no-shows are one-offs: a forgotten booking, a sick child, a plan that changed and a cancel that never happened. A small number of guests, though, miss bookings again and again, often holding tables at several restaurants for the same night and choosing at the last minute. They cost more than their share, because they tend to book prime times and large tables, and the usual fixes, reminders and easy cancellation, do not change their habit.

Before you build a policy for them, check that your own process is not the cause. In Cornell's survey of 1,230 frequent diners, respondents often found it difficult to contact a restaurant when they needed to change a reservation[2]. Cornell's guidance tells restaurants to make it easy for guests to get in touch if they are running late or cannot make it[3]. A guest who tried to cancel twice and could not get through is not a repeat offender; they are a symptom of a phone that nobody answers.

Define a repeat no-show

Write the definition down so that every manager applies it the same way. A good definition is narrow, based on facts in the booking system, and easy to explain to the guest.

  • Count only no-shows: the whole party failed to arrive and gave no notice before the booking time.
  • Exclude late arrivals within your stated hold, which diners see as fair when it is typically 15 minutes[4].
  • Exclude cancellations made before your policy deadline, weather-day changes, and anything the restaurant changed.
  • Track short parties separately; a party that arrives one guest short is not a no-show.
  • Use a window, such as two no-shows within 12 months, so old history falls away.

Record it consistently

  1. Mark outcomes every night

    The closing host marks each booking seated, short, late cancel or no-show before leaving. Automatic no-show marking needs a human check, because walk-ins seated under another name often show up as no-shows.

  2. Match the guest carefully

    Link bookings by mobile number or email, not by name alone. Two different people called Chris Lee are not one repeat offender.

  3. Note what you know

    Record any contact attempt on the night and any explanation the guest gives later. Keep notes factual and short.

  4. Review weekly

    A manager looks at guests who reached the threshold that week and decides the next step. Hosts never flag guests on their own.

  5. Never flag on hearsay

    A rumor from another restaurant or a staff member's impression is not a record. Use only your own booking history.

A response ladder

A step-by-step response to repeat no-shows
LevelTriggerActionTone
1First no-showNo action beyond a short we-missed-you messageWarm; assume plans changed
2Second no-show within the windowFriendly note; future bookings need a card holdPolite and specific
3No-show while a card hold was in placeFee charged under the agreed policyFactual, with a receipt
4Pattern continuesManager decides: phone-only bookings, prepayment for prime nights, or declining future bookingsPersonal call or email from the manager

Diners in Cornell research rated credit card guarantees, together with table-holding policies, as the most acceptable and fairest of the reservation policies tested[1]. That makes a card hold the natural middle rung: it asks nothing of the guest who keeps the booking, and it changes the economics only for the one who does not.

Wording that stays polite

After a first no-show: “We missed you last night and hope everything is all right. If plans change next time, just reply to your reminder text or tap the cancel link, and we’ll pass the table on to someone on our waitlist.”

After a second no-show: “We noticed we’ve missed you twice recently without notice. We’d love to see you again. For future bookings we’ll ask for a card to hold the table. There’s no charge unless the booking is missed without notice. If something we did made it hard to cancel, please tell us.”

Phone script when a flagged guest calls: “I can book that for you. For this booking we just need a card to hold the table, with no charge unless it’s missed without notice. Shall I send you a secure link?” Hosts should never mention a list, a flag or past no-shows unless the guest asks, and then only the facts.

When a flagged guest books by phone

Phone bookings are where a flag is most likely to be missed or handled badly. Make sure the reservation system shows the card hold requirement on the booking screen as soon as the host enters the guest's number, so the host does not have to remember anyone. The host then follows the normal script for a card-hold booking and sends a secure link for the card, never taking numbers aloud at a busy stand.

If the guest pushes back, the host does not argue. “I understand. Let me ask the manager to call you back today.” The manager can explain the reason, listen to any explanation and decide. A guest who says they tried to cancel and could not get through deserves a check of the call log and the benefit of the doubt.

Why it matters more when demand is high

A repeat no-show costs little on a quiet Tuesday and a lot on a full Saturday. Restaurants with strong reputations feel it most. In a UC Berkeley study of San Francisco restaurants, moving from 3 to 3.5 stars on Yelp raised the chance of selling out at prime dining times from 13% to 34%[5]. The more often you sell out, the more likely it is that the table a repeat no-show held was one another guest wanted.

Chance of selling out at prime dining timesSan Francisco restaurants, UC Berkeley study, 2012
Chance of selling out at prime dining timesComparison. 3 Yelp stars: 13%; 3.5 Yelp stars: 34%.13%3 Yelp stars3 Yelp stars: 13%34%3.5 Yelp stars3.5 Yelp stars: 34%Chance of selling out at prime dining timesComparison. 3 Yelp stars: 13%; 3.5 Yelp stars: 34%.13%3 Yelp stars3 Yelp stars: 13%34%3.5 Yelp stars3.5 Yelp stars: 34%

Source: University of California, Berkeley, 2012[5]

Show the data
ItemValue
3 Yelp stars13%
3.5 Yelp stars34%

Fairness and privacy

A flag affects how a guest is treated, so it must be applied the same way to everyone. Federal law entitles all persons to the full and equal enjoyment of places of public accommodation, including restaurants, without discrimination on the ground of race, color, religion or national origin[6], and many state and local laws protect more groups. A rule based only on booking outcomes, reviewed by a manager and applied to every guest, keeps you on the right side of that line.

  • Keep only booking facts: dates, outcomes, contact attempts and the policy applied.
  • Never record opinions about a guest's character, appearance or background.
  • Limit who can see and change flags to managers.
  • Do not share guest records with other businesses; consumer privacy laws in several states cover customer data, so check with counsel before any sharing.
  • Tell a guest what you hold about their booking history if they ask.

Clearing a flag

Flags should expire. Set a rule such as: three completed visits in a row, or 12 months without a no-show, removes the card hold requirement. Clear it at once if the guest shows the misses were your fault, for example a cancellation that was sent but never processed. A guest who sees that the rule works both ways is far more likely to come back and stay.

Check that the rule is working

Review the rule every quarter. Count how many guests reached each level, how many later booked and kept their booking, how many disputes or complaints it caused, and how many flags were cleared. If almost nobody reaches level 2, your threshold may be too high to matter. If many flagged guests turn out to have had cancellation problems, fix the cancel path before tightening anything. The goal is fewer empty tables, not a longer list.

Example: one guest, three steps

Example: a fictional guest books Saturday tables for six twice in two months and misses both without notice. After the second miss the manager sends the polite note and tags the profile for card holds. The guest books again a month later, the host sends the secure card link, and the party arrives on time. After three completed visits the tag is removed automatically, and the guest never hears about it again.

Frequently asked questions

Can a restaurant refuse bookings from repeat no-shows?

Generally a restaurant can set booking conditions based on a guest's own booking behavior, such as requiring a card hold or prepayment, as long as the rule is applied the same way to everyone. Check state and local law with counsel before declining bookings outright.

Should we tell guests they have been flagged?

Tell them what the rule is and how it affects their next booking, politely and once. There is no need to use the word flag, and the record should be shared only with the guest if they ask.

How many no-shows before we act?

Two no-shows without notice within 12 months is a common, fair trigger. Exclude late arrivals within your hold, early cancellations and anything caused by the restaurant.

References

  1. Cornell University (Sheryl E. Kimes) (2011). Customer Attitudes towards Restaurant Reservations Policies (Kimes, Journal of Revenue and Pricing Management, 2011) (opens in a new tab) ↑

  2. Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, 2008) (opens in a new tab) ↑

  3. Cornell University (Sheryl E. Kimes) (2011). Customer Attitudes towards Restaurant Reservations Policies (Kimes, Journal of Revenue and Pricing Management, 2011) (opens in a new tab) ↑

  4. Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, 2008) (opens in a new tab) ↑

  5. University of California, Berkeley (2012). Yelp reviews boost restaurant business (Anderson and Magruder, Economic Journal) (opens in a new tab) ↑

  6. Legal Information Institute (Cornell Law School), US Code (2026). 42 U.S. Code § 2000a - Prohibition against discrimination or segregation in places of public accommodation (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