Fixed quote after a free call

Restaurant no-show reminders, confirmations and waitlist automation

An empty table for eight on a Saturday is revenue the kitchen prepped for and never sees. We build a workflow on top of your reservation platform that sends a confirm-or-cancel message at the time you choose, puts unconfirmed and large parties on a short call list, offers released tables to the waitlist and gives the floor a pre-service list of who has confirmed. A typical build costs $1,000 to $2,500 and takes about three to four weeks.

The problem

What restaurant no-shows really cost a small venue

No-shows hurt small venues hardest. A table held for a party that never arrives cannot be resold at short notice, and staff and food were planned around those covers.

Most reservation platforms send a reminder, but the follow-through is missing: nobody calls the large parties who ignored it, cancellations do not reach the waitlist fast enough, and the manager walks into service without knowing which bookings are solid. Deposits and card holds help, but they need a clear, published policy and careful wording.

What we build

What our restaurant reservation reminder workflow includes

Confirm-or-cancel message

A text or email at the time you choose, with one-tap confirm, change or cancel, using your platform's links where available.

Large-party call list

Unconfirmed bookings over a party size you set go on a short list for the host to call before service.

Waitlist release

Cancellations trigger an offer to the next guests on the waitlist, first to reply gets the table.

Pre-service list

A list before each service of confirmed, unconfirmed and cancelled bookings for the floor manager.

Policy wording

Clear deposit or card-hold wording in every message, taken from the policy you publish; payment itself stays in your reservation platform.

No-show log

A record of no-shows by day and party size, so the manager can adjust policy with real figures.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Bookings read

    Upcoming reservations are read from the reservation platform or its reports.

  2. 02 Automated

    Confirmation sent

    Guests get an approved confirm-or-cancel message at the set time.

  3. 03 Automated

    Waitlist offered

    Cancelled tables are offered to waitlisted guests automatically.

  4. 04 Team review

    Host calls

    The host calls unconfirmed large parties and updates the book.

  5. 05 Manager or chef decides

    Policy and charges

    Whether to charge a no-show fee or waive it is decided by the manager.

How it behaves

How the waitlist and reminders behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the guest sees

  • One confirm-or-cancel message at a sensible time
  • An easy way to change or cancel
  • A call from the host for a large party
  • A waitlist offer when a table opens

What the team sees

  • A large-party call list before service
  • A pre-service list of confirmed covers
  • A no-show log by day and party size

What the automation does

  • Reads upcoming bookings on schedule
  • Sends confirmations and waitlist offers
  • Updates lists as guests reply

Edge cases and fallbacks

Guest replies with a question
Goes to the host list instead of being guessed at.
Booking made on the day
Gets a short confirmation only; no reminder is sent.
Two waitlisted guests reply together
First reply gets the table; the second is told politely and stays on the list.
Reservation platform or Twilio is down
The platform's own reminders still run, and the manager gets an alert.

Architecture

No-show reminders and waitlist for a restaurant at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Reservation book Platform or report n8n schedule Timing rules Confirm or cancel Text or email Waitlist offer First to reply Host Large-party calls Pre-service list Confirmed covers
  • Input
  • Logic and services
  • Output
  • People
  • Data

How it flows

  1. 1 Upcoming reservations are read from the platform on a schedule you set.
  2. 2 Each guest gets an approved confirm-or-cancel message, with your policy wording.
  3. 3 Cancellations go to the waitlist; unconfirmed large parties go to the host to call.
  4. 4 Before service, the floor manager gets a list of confirmed covers and gaps.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

No-show reminders, confirmations & waitlist project plan

Typical time to launch: about 3 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Reservation platform features, current reminders, deposit policy, waitlist and party sizes.

  2. 02

    Design

    2 to 3 days

    Message timing and wording, call-list rules, waitlist logic and pre-service list.

  3. 03

    Build

    About 1 week

    Platform connection, messages, waitlist offers, call list and log.

  4. 04

    Shadow run

    About 1 week

    Lists build for real services while messages go to a test phone.

  5. 05

    Launch

    1 to 2 days

    Switch on for dinner service first, then lunch.

  6. 06

    Support

    Ongoing

    Wording, timing and policy changes as you learn from the log.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n OpenTable, SevenRooms or Resy (integration or reports, confirmed per project) Twilio Programmable Messaging Your email provider Google Sheets or Slack for the call list

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Policy, timing, wording and list rules.

    $200 – $400

  • Build

    Messages, waitlist logic, call list and log.

    $500 – $1,300

  • Integrations

    Reservation platform, messaging and alerts.

    $150 – $400

  • Testing and shadow run

    Real services run against a test phone.

    $100 – $250

  • Launch and training

    Switch-on and host walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Messaging, n8n and reservation platform costs are billed to you directly. Deposits and card holds stay in your reservation platform.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Twilio SMS (US): About $0.0083 per message segment plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing), plus A2P 10DLC registration fees.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: A2P 10DLC registration

Application texts to US numbers from a 10-digit long code must be registered for A2P 10DLC, so registration is part of the plan.

Source: www.twilio.com

US: confirmations vs promotions

Reservation confirmations are kept free of promotions; marketing texts need prior express written consent under the TCPA rules.

Source: www.law.cornell.edu

Card data stays with the provider

Deposits and card holds are taken on the reservation or payment provider's own pages, so card numbers never pass through our workflows.

Source: www.pcisecuritystandards.org

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Restaurant no-show and waitlist questions questions, answered.

A clear confirm-or-cancel message, a personal call for large or unconfirmed parties, an easy way to cancel and a fast waitlist all help. Some venues add deposits or card holds for busy services. The workflow handles the reminders and lists; the manager sets the policy.

That is your call. If you do, publish the policy, repeat it in the booking confirmation and take the card on your reservation platform's own pages. The workflow repeats your wording; it does not charge anyone.

Most do. We build what is missing around them: large-party call lists, waitlist offers, the pre-service list and the no-show log, using the platform's own reminder where it is good enough.

Many venues confirm the day before and send a short note on the day for evening bookings. We start with your current pattern and adjust using the no-show log.

When a table is cancelled, the next guests on the waitlist get a message, and the first to reply gets the table. The host can override at any time.

No-shows and late cancellations by day and party size, tables re-filled from the waitlist and confirmations received. We log these from the first week.

Free 20-minute call

Want this for your restaurants & café?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call