Nobody publishes a US no-show rate, and it still costs you

Search for a US restaurant no-show rate and the same figure comes back: 5% to 7% of reservations on a normal night, attributed to an OpenTable report from 2023. We went looking for that report. It is not on OpenTable's press site, not on its blog, not on the newswires, and it is not linked from anywhere it gets quoted. Every appearance traces back to one blog post that cites no document. A number that only cites itself is not a number, and this one is especially tempting because it is the only one shaped like a rate.

What does exist, with methodology printed underneath it, is this: 28% of Americans said they had not shown up for a reservation in the past year. OpenTable commissioned that survey from YouGov on April 19 and 20, 2021, among 1,326 US adults aged 18 and over, weighted to be representative. Read the unit carefully, because the unit is the whole point. That 28% is the share of people who admit to missing a booking at some point in twelve months. It is not the share of bookings that get missed. Different denominators, people versus reservations. Treating one as the other would inflate the problem by an order of magnitude, and you will see it done.

It is also five years old and was fielded during the post-COVID reopening, when nobody's behavior was typical. So the honest position is the uncomfortable one: there is no benchmark. Which leaves the only rate that was ever going to change a decision, which is yours. One month of marking on the book how many confirmed covers never arrived gives you something no headline can. If your own measurement lands above 5%, treat it as a process problem before you treat it as a customer problem. That is our operating rule of thumb, not a published threshold, and we are labeling it as such.

How many US restaurants now take a card at the time of booking? Nobody publishes that either. The closest material we found came from vendor survey pages that do not declare sample size, field dates, or even whether the respondents were diners or operators, so we are not quoting it. If you have been told that adoption of card holds has doubled, or tripled, ask where the sample is.

One booking platform does publish no-show rates for its own customers broken out by guarantee type, in a clear gradient: prepayment lowest, deposit in the middle, card hold highest. We are deliberately not reproducing the figures. The page would not open to direct retrieval when we checked, and more importantly those restaurants are the ones already charging deposits, which means the ones with the most pricing power to begin with. That is a selection effect big enough to void the comparison. The direction is plausible. The numbers are not a market rate and should never be presented as one.

There is also a slice of no-shows that has nothing to do with forgetfulness. Resy measured its own platform between April 1 and October 23, 2024 and reported that no-show rates for bots and brokers run four times those of the general population, with late cancellations twice as high. Resy does not publish its baseline, so four times gives you no absolute number at all. What it does tell you is that resale and bot booking are a separate problem with a separate fix, and a reconfirmation message is not that fix.

The fourth row is the one almost nobody builds properly, and it is the only one that charges nothing in advance. Its value is not in convincing the person who was going to flake. It is that the guest who already knows they are not coming can say so in ten seconds, instead of calling a number where nobody picks up until 5 p.m.

One thing worth knowing before you design a fee. There is no federal disclosure rule covering restaurant no-show charges. The FTC rule on unfair or deceptive fees that took effect on May 12, 2025 covers live-event tickets and short-term lodging, and restaurants were left out of it. That negative statement is the only one we can make with confidence. Whether you may charge, how you would have to disclose it, and what your processor's rules allow are state-level and contract-level questions this article does not answer. Nothing here is legal advice.

A reminder informs: tomorrow at 8:30 p.m., table for four, here is the address. A reconfirmation asks for a decision and accepts all three possible answers: coming, coming but at a different time, not coming. The difference is architectural, not editorial. If the guest replies to your reminder and nobody reads the reply, you have made things worse: you have taught them that this channel is scenery.

Timing carries as much weight as wording. Resy defines a late cancellation as one landing within 24 hours of the reservation date and time, which is a useful operational line to borrow whatever platform you run. Inside that window you find out; outside it you can still resell. That is why 24 to 30 hours out is the slot: far enough ahead to put the table back on the floor, close enough that the guest already knows their own plans. Two hours out is not a reconfirmation, it is a notification of a loss.

The published evidence on reminders is more modest than it usually gets sold as. A 2024 review reports that at an Australian university clinic, SMS reminders cut missed appointments by 14% in relative terms. Different sector, different country, different channel, so do not carry it into your dining room. What it does give you is the order of magnitude: reminders help, they do not perform miracles. What changes the outcome is giving an easy exit to the person who already decided not to come.

This is the operational half, and it decides whether the system works or is decoration. One rule covers it: anything a guest might want to do with their reservation has to resolve inside the same conversation, with no link to open, no account to create and no phone call.

There is a WhatsApp mechanic worth understanding because it shapes the whole flow. The 24-hour customer service window opens when the user messages or calls you, and it is the user's message that restarts it, not your reply. So the reconfirmation you send outside that window has to be an approved template, but the moment the guest answers anything at all, the window opens and from there you can converse freely without templates. All the fine work, moving a time or changing a party size, happens after that first reply.

• Confirm with one wordNo link, no form, no confirmation code to dig out of an old email.
• Move the time within the same serviceOffer two or three real slots from the book, not a request to call back.
• Change the party sizeGoing from six to four is information worth money, and nobody volunteers it by phone.
• Cancel without friction and without being scoldedThis is the message that saves the most covers. Making it hard is what manufactures the no-show.
• Flag allergies or a late arrivalIt comes in on the same thread and kills the mid-service phone call.
• Reach a personLarge parties, celebrations and complaints: the handoff has to be one message away.

Everything above depends on one thing the flow either does or does not do: read real availability before it offers anything. If your agent confirms a slot that does not exist, the guest is not going to blame the software. Never let it improvise times.

On disclosure, keep it simple rather than clever. Have the assistant introduce itself as an automated assistant at the top of the conversation. It costs nothing, it removes a whole category of complaint, and it means you are not relying on a guest guessing correctly. We are not going to tell you what your state requires; we are telling you what has no downside.

Five situations where this build is money badly spent, and they are worth naming before you find them out yourself.

First: the room does not fill. We already did the math. Under scenario B you would need to recover more than 20 of the 36 covers a month just to pay for the tool, and that does not happen. Your problem is demand, not no-shows.

Second: fewer than a hundred reservations a month. At that volume, whoever answers the phone can reconfirm by hand in half an hour a week, and guests like it better. Automate when the task is the one that gets dropped for lack of time, not when it fits comfortably into the day.

Third: the book is not anywhere a system can read it. If reservations live in a paper binder or scattered across Instagram, the phone and a notepad, the agent cannot offer real slots and will promise tables that do not exist. Book first, automation second. That order, no exceptions.

Fourth: nobody is going to read the replies. A flow that opens a conversation and then leaves messages unanswered does more damage than having nothing. If there is no person with the inbox in front of them during service, do not turn it on.

Fifth: your volume is mostly walk-in. If 80% of your room arrives without booking, what you are missing is not reconfirmation, it is waitlist control, which is a different problem with a different answer.

Outside those five, the arithmetic usually works. The Starter plan at €79/month is covered by a little over three recovered covers a month in a service that fills, and the Growth plan at €297/month includes white-label, which is the relevant line if you are the agency building this for several restaurants rather than the restaurant using it. Enterprise is quoted case by case, and annual billing brings those two to €58 and €166/month. The first agent can be built free with no card, which for this specific case is the sensible way to test the math against your own numbers before signing anything. The solutions page has the detail on how the flow gets assembled channel by channel, and the WhatsApp AI chatbot page covers the channel itself.

The 28% figure and its methodology come from OpenTable's own announcement of its Show Up for Restaurants initiative, with the YouGov field dates and sample printed in the release. The 5% to 7% no-show rate attributed to a 2023 OpenTable report was discarded: we could not locate any primary document, and every instance we found traced to a single blog post with no link. If you see it elsewhere, that is where it came from. The bot and broker comparisons and the definition of a late cancellation are Resy's own platform data for April 1 to October 23, 2024, and they are relative, with no published baseline. One vendor's no-show rates by guarantee type were left out on purpose: the page did not open to direct retrieval, and the sample is that vendor's own deposit-taking customers.

The FTC point is deliberately negative and was triangulated through trade press and law-firm summaries because ftc.gov returned an access error to us; it says only that restaurants were excluded from the fee-disclosure rule effective May 12, 2025, and nothing about what you may charge. The WhatsApp rules, meaning the 24-hour window, template categories, recategorization and the October 1, 2026 change, are from Meta's official developer documentation. The 14% SMS reminder figure is from a 2024 review of an Australian university dental clinic, not from restaurants.

All checked on August 2, 2026. The dollar amounts in the calculation, including the 4% rate, are worked-example assumptions and not sector averages: replace them with yours. This content is informational and is not legal, tax or financial advice.