Restaurant Reservation and No-Show Automation

A Two-Top Sitting Empty on a Saturday Costs More Than It Looks Like

A table booked for 7pm on a Saturday that never shows up carries a real cost beyond the one missed reservation. That table could've turned twice more that night, a server planned their whole section around it, and a walk-in couple got turned away an hour earlier because the book showed full. Multiply that by however many no-shows a busy weekend brings and the number gets uncomfortable fast.

From what we've seen, restaurant no-show rates typically run somewhere around 10-20% for reservations that don't require a deposit or card on file, and it climbs from there for large parties and holiday weekends. Most independent restaurants we've talked to don't track the number precisely, they just know Saturdays feel worse than they should given how full the book looked at 4pm.

The usual fix is a single confirmation text sent by whatever reservation software the restaurant already uses. That helps some. It doesn't touch the other two problems sitting right next to it: nobody's automatically texting the waitlist when a table frees up, and almost nobody's asking for a review at the right moment after a good visit. Confirmations, waitlist fill, and review requests are really one connected system when they're built right. Most restaurants are running none of them properly, or they're paying a reservation platform a few hundred dollars a month for a version that's more rigid than what they actually need.

Why the Built-In Reminder Isn't the Whole Job

A confirmation text sent once, hours or days before the reservation, assumes the guest reads it, remembers it, and shows up anyway if their plans changed. Restaurants that rely on just that one touch usually find out who's not coming at 7:05pm, which is exactly the moment there's nothing left to do about it.

A fancier reminder alone doesn't solve that. What works is separating guests into confirmed and unconfirmed early enough that the unconfirmed group can be nudged again, and if they still don't respond, their table gets flagged as at-risk before the seat actually goes empty. That's the same staged-confirmation logic behind cutting no-shows at dental and medical practices and salons, just tuned for a much shorter runway since most restaurant bookings happen same-day or a day or two out rather than weeks in advance.

What the Full Sequence Looks Like

This is roughly the build we put together for restaurant clients, split into the three pieces that matter: confirmation and reminders, waitlist text-back, and post-visit review requests. It's the same logic driving gym membership renewal and check-in reminders elsewhere, just tuned to a dinner service instead of a monthly billing cycle.

Step 1: Instant Booking Confirmation

The second a reservation lands, whether through an online widget, a phone call logged by the host stand, or a walk-in added for later that night, a text goes out within a couple minutes.

Hi [Name], you're booked for [time] tonight, party of [size]. Reply YES to confirm or call us if plans change.

Step 2: Same-Day Confirmation Push

A few hours before the reservation (timing depends on how far out it was booked), anyone who hasn't replied YES gets a direct ask.

Hi [Name], quick check: still good for [time] tonight? Reply YES to confirm or let us know if you need to cancel.

Anyone who confirms drops out of the sequence. Anyone who doesn't gets one more nudge closer to the reservation time, then their table gets marked at-risk in the tracking sheet.

Step 3: Waitlist Text-Back on Cancellation or No-Show

This is the piece that most reservation platforms either charge extra for or don't do well. The moment a table is marked at-risk, cancelled, or actually no-shows, the workflow pulls the next name off the walk-in waitlist and texts them directly.

Hi [Name], a table for [size] just opened up for [time]. First to reply YES gets it.

First reply wins the table, and everyone after that gets an automatic reply letting them know it's taken and that they're still first in line for the next opening, so nobody's left checking their phone wondering if they got it.

Step 4: Post-Visit Review Request

Timed roughly an hour or two after the reservation slot ends (not immediately when they walk out, and not the next morning when the memory's already faded), a short message goes out asking for a review.

Hi [Name], thanks for dining with us tonight! If you had a good experience, a quick Google review would mean a lot: [link]

Guests flagged with a complaint or a comped item during service get excluded from this step automatically, and that matters more than it sounds like it would, since asking someone who just had a bad table for five stars is about the fastest way to tank a review request campaign.

Building This in n8n or Make

Most restaurant reservation systems (Resy, OpenTable, Tock, or a plain Google Form and phone log for smaller places) either don't expose an easy webhook or lock it behind a pricier tier. In practice the cleanest build usually routes through Google Sheets as the shared source of truth, even for restaurants that already use a booking platform.

The typical setup:

1. Reservations, whether captured through the platform's export, a Zapier connection, or manual entry at the host stand, land in a Google Sheet with columns for name, phone, party size, time, and a status field.
2. An n8n or Make scenario runs on a short interval, every 10-15 minutes covers most dinner services, and checks for rows that have crossed a send threshold for confirmation, reminder, or waitlist trigger.
3. Twilio handles the two-way SMS since reply-keyword logic (YES, CANCEL) is simple to wire up without needing a WhatsApp Business API provider. WhatsApp is worth adding for markets where guests already default to it, response rates tend to be a bit higher there, but Twilio SMS covers most US restaurant traffic without extra setup.
4. Replies come back through a webhook and update the same sheet, which is what decides whether the next message in the sequence fires or gets skipped.
5. The waitlist logic runs as its own small scenario watching for any row marked at-risk or cancelled, matching it against the top unmatched name on a separate waitlist tab, and sending the offer.
6. Review requests fire from a time-based trigger checking for reservations that ended 60-90 minutes ago and weren't flagged with a service issue.

For a restaurant doing 150-250 covers a week, this typically lands around 10-14 modules split across two or three scenarios. First build usually takes half a day once the booking export format is mapped out, since every platform structures its data a little differently and that's usually where the time actually goes.

If the restaurant runs a loyalty program or gift card promotions through HubSpot or an email tool, syncing that confirmed visit history over lets those campaigns target actual repeat guests instead of guessing from a spreadsheet nobody updates.

"Doesn't OpenTable Already Do This?"

Fair question, and worth answering directly instead of dodging it. Reservation platforms like OpenTable, Resy, and Tock do send confirmations and reminders, and some tiers include a basic waitlist feature. What they typically don't do well is the review request timing (most either skip it or send something generic through their own review widget instead of pushing straight to Google) and they charge per-cover or per-month fees that scale with how busy you get, which is a strange incentive structure for software that's supposed to help you get busier.

The DIY version built on Twilio, n8n or Make, and a Google Sheet costs a flat rate regardless of covers. It also isn't locked to one reservation platform, so if the restaurant ever switches booking software, the automation layer doesn't need to be rebuilt from scratch, only the connection point at the top does.

The other objection that comes up is guests feeling over-texted. In practice nobody in this sequence gets more than three or four messages total, and every message past the first only fires because the guest hasn't responded yet. A guest who confirms right away gets exactly one text and nothing else until the review request. The sequences that feel spammy are almost always ones where every guest gets every message regardless of what they already answered. That's a build mistake we see a lot, honestly, usually because whoever built it copied the same sequence for every guest instead of stopping it once someone confirms.

What This Actually Costs

For a restaurant running around 200 covers a week, most reservations only need one or two messages since a good chunk of guests confirm on the first ask. A smaller share, maybe a quarter of bookings, needs the fuller three or four message sequence including the at-risk nudge. Averaged out that lands somewhere around 500-700 messages a month across confirmations, waitlist offers, and review requests.

Twilio SMS runs about $0.0079 per message segment in the US, so messaging cost alone sits somewhere between $4 and $6 a month for that volume. An n8n or Make plan adds $9-30/month depending on how many executions the scenarios run. Total automation spend usually stays under $40/month, which is less than a single month of the entry-level tier most reservation platforms charge before per-cover fees even get added in.

If recovering even a handful of no-show tables a week, plus picking up a steady trickle of new Google reviews, moves the needle on weekend bookings, the cost usually gets covered within the first week or two most months, and it stays flat whether the restaurant does 100 covers a week or 400, unlike most reservation platforms.

Getting This Set Up

None of this requires custom software or a rebuild of whatever booking system is already in place. It's a shared tracking sheet, Twilio or WhatsApp for the messaging, and an n8n or Make scenario tying the confirmation, waitlist, and review steps together so they run without anyone at the host stand having to remember to send anything.

We build this exact setup for restaurant and hospitality clients as part of our free automation audit. Book a free 60-minute call and we'll walk through your current reservation flow, show you where no-shows and empty tables are actually costing you, and map out what the full system looks like for your restaurant specifically.