Start with accurate booking details, a clear confirmation, a helpful reminder and an easy cancellation route. Apply any deposit or cancellation rules transparently, and track no-shows separately from late cancellations.
A table for eight stays empty during a busy service. Another group called earlier, but the team could not offer them that table. The problem is not just the booking that disappeared; it is the opportunity the venue could not recover.
A useful no-show process starts well before a cancellation fee. It helps guests understand their booking, makes changes straightforward and gives the team time to refill a table. This guide offers a practical workflow for Irish restaurants, food-led pubs and hotel dining rooms, without claiming that one policy works for every venue.
Define what you are measuring
Distinguish a no-show from a late cancellation, a reduced party size and a guest who arrives after the agreed time. Use the same definitions across the booking system, host desk and end-of-service report.
For example, define a no-show booking as one that remains expected for service but does not arrive or cancel by your documented no-show cut-off. Define late cancellation separately using your venue’s clearly communicated deadline. Do not count one booking in both categories.
Choose whether you measure bookings or covers. A missing table of two and a missing table of twelve are one booking each, but they have different operational effects. Keep both views when useful, and keep walk-ins separate from reservation performance.
Make the confirmation do the basic work
Send the correct venue, date, local time and party size, with a booking reference and a clear way to contact the team. For a hotel with several restaurants or a group with multiple sites, identify the exact location. State any agreed seating duration or arrival instructions before a misunderstanding reaches the door.
Check that a phone or email booking is actually entered into the live diary before sending “confirmed”. An AI-written reply can be well phrased and still promise a table that has not been allocated. A request, a provisional hold and a confirmed reservation should have different messages.
Hello {guest_name}, your table for {party_size} is confirmed at {venue} on {date} at {time}. Your reference is {reference}. To change or cancel, use {manage_booking_link} or call {venue_phone}. We look forward to welcoming you.
These templates are drafts for your own verified booking fields. Replace the fields and add only policies the guest actually accepted. Do not paste a new fee into a reminder and treat it as an agreed term.
Send a reminder that helps the guest act
Test a reminder schedule that leaves your team a realistic chance to refill a table. A reminder on the previous day is a reasonable pilot setting, not a guaranteed optimum. For larger parties or special events, a separate confirmation call may be appropriate.
Make the main action obvious: confirm, change or cancel. A reply that says “we cannot make it” should reach someone who can release the table. Avoid sending reminders from an unattended channel without giving a workable alternative.
Hello {guest_name}, a reminder about your table for {party_size} at {venue} on {date} at {time}. Plans changed? Please update your booking here: {manage_booking_link}, or call {venue_phone}. Thank you for letting us know.
Track undelivered messages and duplicate reminders. More contact is not automatically better. A guest who already cancelled should not receive another message asking them to attend.
Make cancellation easier than silence
Provide a direct route from the confirmation to the booking. Avoid forcing guests to create a new account just to tell you they cannot attend. Where a link is not practical, offer a monitored phone number or reply address and state when the team is available.
When a cancellation is received, update the diary, send an acknowledgement and offer the table to the waiting list under your normal process. Keep the released table and any replacement booking linked for measurement, without promising the same slot to several people at once.
For a busy match day or bank-holiday service, decide who owns the waiting list and how long an offer remains open. Local demand is useful only when the team can turn it into a confirmed booking.
Use deposits and cancellation charges carefully
A deposit, a prepayment and a card guarantee are different arrangements. Explain which one the venue uses, how much is collected or may be charged, when it applies and how it affects the final bill. State the cancellation deadline and the circumstances in which money is returned.
The CCPC explains that paying a deposit creates a contract and highlights the importance of written deposit and cancellation conditions. Its business guidance also requires transparent terms and explains that unfair terms may not be binding. A blanket “non-refundable in all circumstances” statement is not a substitute for a properly reviewed policy. [1] [2]
Have your terms reviewed for your venue and payment process before using them. This article is operational guidance, not a legal opinion on a specific charge. Do not assume that requesting a card permits any later debit.
Consider a focused pilot for bookings where you can explain the operational need, such as a large group or a set-menu event. Measure the effect on completed bookings and guest complaints as well as attendance. A policy that deters many genuine guests is not automatically successful because recorded no-shows fall.
Keep card information out of reservation notes
Use an appropriate payment provider to collect payments or manage an authorised card guarantee. Do not ask staff to write full card details into a diary, email thread or free-text guest note. Confirm the provider’s requirements and the payment flow with your acquirer.
PCI Security Standards Council guidance prohibits retaining card verification codes after authorisation, including for future card-on-file transactions. Guest permission does not override that requirement. [3]
Keep a record of the booking terms accepted and the relevant payment reference, with access restricted to the staff who need it. Let the payment service handle the sensitive payment data rather than creating an improvised storage process.
Separate a service reminder from marketing
A booking reminder should help the guest manage that booking. Adding an offer for next month’s event changes the purpose of the message. The Data Protection Commission sets specific rules for electronic direct marketing, including consent requirements and a limited existing-customer exception with conditions. A reservation is not a reason to add everyone automatically to a promotional list. [4]
Keep guest records relevant, accurate and subject to a justified retention period. Restrict access and avoid subjective labels such as “bad guest”. A factual note about a reviewed incident is different from an unsupported accusation. These practices reflect the DPC’s principles of minimisation, accuracy, storage limitation and confidentiality. [5]
Measure no-shows without confusing the denominator
Choose a fixed reporting definition and keep it consistent. One useful measure is:
In a fictional week, 200 bookings remain expected at the cut-off. Eight do not arrive and are classified as no-shows: 8 ÷ 200 × 100 = 4%. Report cancellations made before that cut-off separately. Also track late cancellations, missing covers, released tables refilled and booking completion rates.
This is a suggested measurement method, not an industry-wide benchmark. Compare like-for-like services and note holidays, weather, events or changes in booking mix. A before-and-after result does not by itself prove that a reminder or deposit caused the difference.
Handle the missed booking without an argument
Check the diary and contact history before marking the guest absent. Was a cancellation received elsewhere? Was the booking at another venue? Did staff already move the time? Correct an internal mistake before starting a payment process or recording a guest-history flag.
Hello {guest_name}, we were expecting your party at {venue} on {date} at {time} and could not mark you as arrived. Please let us know if your plans changed or if we have recorded the booking incorrectly. You can reach us at {venue_phone}.
Use a person to review disputed charges and sensitive situations. The objective is a reliable booking process and an informed team, not an automated confrontation.
Questions about restaurant no-shows
Should every table require a deposit?
Not necessarily. Test a policy that fits your venue, service and booking mix. Keep the terms transparent and review effects on conversion, attendance and guest experience.
Is there one best reminder time?
No universal timing is established by this guide. Start with a schedule that allows guests to act and gives your team time to recover the table, then measure the result.
Can we send marketing to everyone who booked?
Do not assume so. Electronic marketing has separate requirements. Keep operational messages focused on the booking and check the DPC guidance before sending promotions.
Can AI decide that a guest is a no-show?
A system can flag an overdue arrival for review, but the record should be checked against cancellations, time changes and host-desk information before consequential action is taken.
Sources and editorial notes
Primary guidance checked on 26 October 2026. Operational routines and worked examples are Inntally’s editorial recommendations; adapt them to your venue.
- CCPC — deposits for goods and services
- CCPC — guidance for businesses on unfair contract terms
- PCI Security Standards Council — card codes and future transactions
- Data Protection Commission — electronic direct marketing
- Data Protection Commission — principles of data protection
All numerical examples are fictional and explain the method; they are not customer results or savings claims. Booking terms and payment policies need review for your venue; this is not legal advice. Images are illustrations, not photographs of identified customers or evidence of product outcomes.
Read next
- How to compare restaurant supplier prices — and find the real cost
- A pub stocktake template that helps you explain the difference
- Three-way invoice matching for restaurants: ordered, received, invoiced
- Restaurant bookkeeping in Ireland: a weekly routine that keeps the records together
- The best restaurant reservation systems in Ireland — which systems carry deposits and reminders.
- Inntally Reservations — the product page.