No-Show Rate

No-show rate looks like a simple number and is not, because what counts as a no-show depends on the reservation platform reporting it. Comparing the figure across venues, or across two platforms inside one group, is where most operators go wrong.

Why do no-show rates differ between reservation platforms?

Reservation platforms do not agree on how a no-show is established, and the difference is not cosmetic. Resy, OpenTable, and SevenRooms all expose a guest-confirmation signal, so a booking can be known to be confirmed, known to be unconfirmed, or unmarked. Tock does not deliver a confirmation signal at all.

That matters because of what an absent signal means. On a platform that reports confirmation, unconfirmed genuinely means the guest did not confirm. On a platform that never reports it, the same blank field means nothing was ever asked. A group running two platforms and comparing no-show rates between them is often comparing a measurement against an absence of measurement.

The second variable is who marks the no-show. Some venues mark them diligently at the end of service and some never do, so a low reported rate can mean a well-run book or an unattended one.

What does a no-show actually cost?

A no-show costs twice. The first cost is the empty table, which is obvious. The second is the walk-in turned away to hold it, which is invisible and usually larger, because that guest also would have ordered and might have come back.

At group scale the compounding cost is planning. Covers on the book drive prep, ordering, and rostering, so a systematically overstated book means food bought and staff scheduled against demand that was never real.

Can guest history reduce no-shows?

Yes, and this is where a guest profile changes the policy rather than just the reporting. A first-time booker holding a Saturday prime-time table and a regular of five years present very different risks, and treating them identically is what makes confirmation policies feel heavy-handed to the guests who least deserve it.

A restaurant with visit history attached to the booking can tier its approach. Reconfirm the bookings that warrant it, ask for payment up front on high-risk parties and buyouts, and leave known regulars alone. Loyalist takes prepayments through Stripe and surfaces the guest’s history on the reservation, so whoever works the book sees who they are dealing with before deciding.

One practical note on messaging. A confirmation request about an existing booking is a transactional message rather than a marketing one, but consent rules still govern how a restaurant texts guests, so confirmation flows belong in the same consent framework as everything else.