AI Guides / Restaurants

AI and automation for restaurants

Restaurant margin dies in two places: the Saturday four-top that never shows, and the booking call that rings out mid-service and lands next door. Both fixes already exist in the reservation platform you likely run — card holds that make no-shows collapse, reminders that give honest cancellers a way out, and waitlist alerts that refill the table the moment it opens.

Start at step one. Stop whenever you like — nothing below is needed for anything above it to work.

Start at step one Done this before? Jump to all 11 jobs

Prices checked by hand 27 July 2026 · nobody pays to be listed here

The whole page, in order

Week 1 · free$0

Switch on booking confirmations and same-day reminders with an easy still-coming reply — the free no-show reducer that also frees tables early enough to rebook them.

Software: OpenTable, SevenRooms, or your reservation platform

Week 2$0

Add card holds to prime slots and large parties, and paid deposits to event nights and set menus. Policy in the booking flow, stated plainly — the card is the commitment, the fee is the rarity.

Software: OpenTable or SevenRooms booking policies

Week 3$0

Turn on the cancelled-table refill: waitlist and priority alerts offering the slot the moment it opens, before the host stand even notices.

Software: OpenTable waitlist or SevenRooms Priority Alerts

Week 4 · measure$0

Watch four numbers: no-show rate on protected versus unprotected bookings, tables refilled from cancellations, calls missed during service, and bookings through your own link. Only then decide whether anything needs building.

Software: Reservation-platform reports

Step one · start here

What your current restaurants software may already include

On OpenTable, SevenRooms, Your reservation platform, these are settings, not another subscription — check your plan includes them. On something else, search its help centre for the same feature name.

Extra software cost

$0*

if included in your plan

Features ready

Task 1

OpenTable → Booking policies — credit-card holds and deposits

saves protects prime-night covers

Why it matters

Card holds and paid deposits built into the booking flow (Stripe required), with automatic reminder texts — OpenTable's own data has card-hold bookings up to 16% less likely to no-show. Configured under Policies, and most venues never set one.

What to do

Open the official guide below. In OpenTable, find “Booking policies — credit-card holds and deposits”. Follow the guide once, switch it on for one real job or customer first, and check that it did exactly what you expected before using it everywhere.

Open the official setup guide ↗

2 hours · $0 extra if included in your current plan

Task 2

SevenRooms → Priority alerts and automatic cancellation fees

saves refills cancelled covers

Why it matters

A cancelled table alerts the waitlist instantly, VIPs and regulars first, so the slot refills without a phone call. Card-on-file also enforces your no-show and late-cancel fees automatically.

What to do

Open the official guide below. In SevenRooms, find “Priority alerts and automatic cancellation fees”. Follow the guide once, switch it on for one real job or customer first, and check that it did exactly what you expected before using it everywhere.

Open the official product page ↗

Half a day · $0 extra if included in your current plan

Task 3

Your reservation platform → Automated confirmations and same-day reminders

saves ≈4 hrs/mo of chasing

Why it matters

Confirmation at booking and a same-day reminder with an easy cancel path — the forgetful guest either shows or frees the table while it can still be resold. Included everywhere, half-configured almost everywhere.

What to do

Open the official guide below. In Your reservation platform, find “Automated confirmations and same-day reminders”. Follow the guide once, switch it on for one real job or customer first, and check that it did exactly what you expected before using it everywhere.

Open the official setup guide ↗

1 hour · $0 extra if included in your current plan

Different software? The same switch usually exists under another name.

Step two · first workflow to implement

OpenTable or SevenRooms booking policies: Put a card behind the prime slots.

A hold on Friday and Saturday nights and any party of six-plus makes no-shows collapse — operators report them going effectively to zero — while the fee itself is rarely charged. The card is the commitment device; the policy in the booking flow does the awkward conversation for you.

Do this in order

1. In OpenTable or SevenRooms, open reservation or booking policies and choose the exact prime services, large-party sizes, and event nights that need protection.
2. Use a card hold for prime bookings and large parties; use a paid deposit only for scarce events or set menus where the fee is justified.
3. Write the cancellation window and fee in plain language inside the booking flow, confirmation, and reminder.
4. Make and cancel a test booking from a customer’s phone. Confirm the policy is visible before confirmation and the host stand sees the correct status.

Typical size

prime-night covers protected

Setup

2 hours

What to use

OpenTable or SevenRooms booking policies

OpenTable · Tiered; per-cover fees on network bookings ↗SevenRooms · On quote ↗

Buy or build: Already paid for

How you know it worked

Count it in week one, then count the same thing again in week four. If the number did not move, stop spending.

Keep this implementation simple

Use the steps above with the software you already have. Test the workflow on your own phone before adding another product or paying someone to build around it.

Step three · keep going without adding complexity

Once step two works, take the next three jobs in this order.

One at a time. Finish it, test it on real work, then start the next.

OpenTable waitlist or SevenRooms Priority AlertsTypical size≈10 refills/mo

Refill the cancelled table before service notices

A 7:30 cancellation offered instantly to the waitlist — regulars first — turns a dead four-top into covers. The alert machinery exists in the platform; the craft is keeping a live waitlist worth alerting.

Setup effort: Half a day

OpenPhone, $19/userTypical size≈30 missed/mo

Catch the booking call that rings out mid-service

The 7pm caller wanting Thursday's table gets a busy signal and books next door. A missed call triggers an instant text with the booking link — the booking captured without a host leaving the pass.

Setup effort: 2 hours

OpenTable Experiences or SevenRooms upgradesTypical sizeper event night

Sell the event nights as prepaid

Set menus, wine dinners and holiday services sold as ticketed, prepaid bookings — revenue locked before a plate is fired, and the no-show problem deleted rather than managed for the nights that hurt most.

Setup effort: Half a day

Step four · only once the first three are running

These are useful, but they are not the place to begin.

The first point where paying for a build makes sense — once the earlier steps are running.

OpenTable or SevenRooms guest database and campaignsTypical size≈2,000+ guests on file

Work the guest book you already own

Visit history, spend and preferences sit in the platform for every guest you've seated. Birthday messages, a we-miss-you at ninety days, and first-alert invitations for regulars — through your own booking link, not the marketplace's — refill midweek from a list that cost nothing.

Setup effort: 1 day

Does this look familiar?

These are the problems the named tools above are meant to remove.

Put a card behind the prime slots

Refill the cancelled table before service notices

Catch the booking call that rings out mid-service

Sell the event nights as prepaid

Work the guest book you already own

Let the reminders do the confirming

After thirty days

Four numbers. If they have not moved, stop and do not spend another dollar.

Number one

Put a card behind the prime slots

Write down the current monthly number before you switch anything on. Compare it with the same number after thirty days.

Number two

Refill the cancelled table before service notices

Count it the same way in week one and week four. Do not change the definition halfway through.

Number three

Booking policies — credit-card holds and deposits

Use the history inside your existing software to count how often the automation actually ran.

Number four

Hours given back

Ask the person doing the work now. They will know before a dashboard does.

Every other figure here is a typical size. These four are yours.

Reference

All 11 jobs for restaurants, in order of what they return.Open ↓

Wins work

Put a card behind the prime slots with OpenTable / SevenRooms booking policies

Typical size: prime-night covers protected
Buy or build: Already paid for · OpenTable / SevenRooms booking policies
Effort: 2 hours

Refill the cancelled table before service notices with OpenTable waitlist or SevenRooms Priority Alerts

Typical size: ≈10 refills/mo
Buy or build: Already paid for · OpenTable waitlist or SevenRooms Priority Alerts
Effort: Half a day

Catch the booking call that rings out mid-service with OpenPhone

Typical size: ≈30 missed/mo
Buy or build: Buy · OpenPhone, $19/user
Effort: 2 hours

Sell the event nights as prepaid with OpenTable Experiences or SevenRooms upgrades

Typical size: per event night
Buy or build: Already paid for · OpenTable Experiences or SevenRooms upgrades
Effort: Half a day

Work the guest book you already own with OpenTable or SevenRooms guest database and campaigns

Typical size: ≈2,000+ guests on file
Buy or build: Already paid for · OpenTable or SevenRooms guest database and campaigns
Effort: 1 day

Saves hours

Let the reminders do the confirming

Automated confirmation and same-day still-coming texts replace the afternoon of confirmation calls — and every early cancellation they harvest is a table back on sale.

Typical size: 5 hrs/mo
Buy or build: Already paid for · Platform reminders
Effort: 1 hour

Stop typing supplier invoices with Xero + Hubdoc

Produce, meat and beverage invoices photographed or emailed in, line items extracted and coded automatically — the back-office hour a day that nobody costs into the food margin.

Typical size: 8 hrs/mo
Buy or build: Buy · Xero + Hubdoc (included)
Effort: Half a day

Watch the food cost weekly, not quarterly with Xero data + a simple report

With invoices captured digitally, price creep on your top twenty ingredients becomes a weekly glance instead of a quarterly shock — the chicken supplier's quiet 8% shows up while you can still act.

Typical size: 3 hrs/mo
Buy or build: Small build · Xero data + a simple report
Effort: 1 week

Ask for the review while the glow lasts

A next-morning message to last night's guests with the review link — the systematic version of the thing you only remember to ask your friendliest tables.

Typical size: ≈3x more reviews
Buy or build: Already paid for · Platform post-visit messaging
Effort: 1 hour

Answer the phone's five questions once with Google Business Profile + templates

Hours, parking, dietaries, corkage, group policy — the questions that interrupt service all night, answered by a current website, a complete Google profile, and a text-back that links both.

Typical size: 4 hrs/mo
Buy or build: Small build · Google Business Profile + templates
Effort: Half a day

Keep the roster off the group chat with Deputy

Shifts, swaps and availability in a rostering tool instead of a message thread — hospitality's most reinvented wheel, solved for a few dollars a user.

Typical size: 5 hrs/mo
Buy or build: Buy · Deputy, from $4.50/user
Effort: 1 day

The stack

The tools named, priced, and judged.

Tools named in this guide, what each one is for, its price, and the verdict.
Tool	What it is for	Price	Verdict
Reservations networkOpenTable	Bookings with the largest diner network, card holds, deposits and reminder flows.	Tiered; per-cover fees on network bookings ↗	The network brings genuine discovery — priced per cover, which is fair for strangers and expensive for regulars. Same rule as every marketplace in this library: discovery from the network, regulars through your own link.
White-label reservations & CRMSevenRooms	Bookings on your own site, deep guest profiles, priority alerts, automated fees and marketing.	On quote ↗	The data-ownership choice: no marketplace, no per-cover skim, your guest book is yours. The trade is discovery — you bring the demand, it manages it. Right for venues with a name; wrong for a venue that still needs finding.
Reservations alternativesNow Book It / Resy	The AU-local and the no-per-cover-fee network options respectively.	Tiered ↗	Both worth quoting against the incumbents — the deciding questions are per-cover fees at your volume, deposit support, and who owns the guest data. Get all three answers in writing.
Phone & messagingOpenPhone	The restaurant number with missed-call text-back and a shared inbox.	$19/user ↗	The mid-service missed call is this trade's cheapest fixed leak. Skip only if your booking platform's own phone tooling covers text-back.
Accounting & invoice captureXero + Hubdoc	The books, plus supplier-invoice extraction included in the subscription.	$35/mo ↗	Hubdoc comes with the plan most venues already pay for and almost none use — the rare case where the food-cost tooling is genuinely free. Start there before pricing dedicated food-cost platforms.
RosteringDeputy	Shifts, swaps, availability and timesheets for hospitality teams.	From $4.50/user ↗	Cheap, standard, and better than the group chat by a distance. The discipline is making it the only place the roster lives.
AutomationMake.com	The win-back sequences and food-cost report beyond platform built-ins.	$9/mo ↗	Check the reservation platform's own campaigns first — most guest messaging belongs there. One scenario for the food-cost report is the honest use here.
AssistantChatGPT Team	Team questions from your own documents — menu details, allergen matrix, policies, supplier contacts.	$25/user ↗	Loaded with your allergen matrix and policies it's genuinely useful at the pass and the phone. It never invents an allergen answer — if the matrix doesn't say, the kitchen decides.

Do not bother

Three things not to buy yet.

Fighting no-shows with blacklists instead of cards.

Banning past no-showers feels satisfying and fixes nothing — the next no-show is usually a first-timer. The card hold fixes the incentive for everyone, politely, in the booking flow, and the operators who've done it watch no-shows go to almost nothing.

Third-party delivery as a margin strategy.

Marketplace delivery commissions consume most of a restaurant margin and train guests to order through someone else's brand. Use it as paid awareness if you must; the money is in covers, your own pickup channel, and the guest book you own.

AI review responses on autopilot.

A templated apology under a genuine complaint reads as exactly what it is, publicly, forever. Draft with whatever tool you like — but the owner reads, edits and owns every reply to a bad review, because the reply is the marketing.

Sources