← Back to library

Confirm tables on WhatsApp against a live book

u/begylewis built a WhatsApp booking agent for a neighborhood restaurant: guests message normally, and the agent checks availability, answers questions, confirms the table and later sends a reminder and a thank-you. Staff manage bookings on a table layout in a companion web app. He landed one paying restaurant by cold email but not a second after a thousand more.

  • OutcomeGuests book a table by chatting on WhatsApp, staff see bookings on a table plan, and reminders go out automatically.
  • SetupAn afternoon+
  • LevelIntermediate
  • Creditu/begylewis on r/micro_saas
View original
Works with
Custom agentChatGPTn8n

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • Your restaurant already takes bookings over WhatsApp by hand
  • Staff miss messages during service
  • You want reminders to cut no-shows

Not for: Restaurants without an accurate record of table availability; Promotional messaging to people who haven't booked

What do you need, and what do you get?

You need

  • WhatsApp Business API access
  • A reservation book with tables, covers and opening hours
  • Restaurant details for common questions

You get

  • Confirmed bookings from chat
  • A staff view of reservations by table
  • Pre-visit reminders and post-visit thanks

How does it work, step by step?

  1. Define the bookSet tables, party sizes, seating times and how long a table is held.
  2. Answer from factsLoad menu, hours, location and policies so the agent answers common questions.
  3. Check before confirmingLook up availability for the party size and time and confirm only real openings.
  4. Remind and thankSend a reminder before the booking and a short thank-you after.
  5. Give staff the planShow bookings on a table layout so the floor team can adjust.

The prompt

Our own prompt, inspired by u/begylewis on r/micro_saas and written to work in Custom agent, ChatGPT and n8n. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt4 variables
You take reservations on WhatsApp for {restaurant}. Facts: {facts} (hours, address, menu notes, policies). Availability tool result: {availability}.
Ask for date, time, party size and name. Offer only times that are open for that party size; confirm the booking back with all details. For parties over {max_party}, allergies or special events, say a team member will reply and collect contact details. Never invent opening hours, dishes or availability.

Inspired by u/begylewis on r/micro_saas: Created an AI agent through WhatsApp that manages reservations for a local restaurant. I have one paying customer but can't find more.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Walk-ins and phone bookings must go into the same book or the agent will double-book.
  • Large groups and special requests are better passed to staff.

Our take

For restaurants that already live on WhatsApp, meeting guests in that channel is smarter than pushing them to a booking site. The make-or-break detail is that every booking, whether from chat, phone or walk-in, lands in the same reservation book, otherwise the agent will confidently give away a table that's taken. The staff table view in his product addresses that, and it's the piece to build first if you do this yourself. Keep the agent's answers tied to a short fact sheet about hours, menu and policies, and send large parties, allergies and complaints to a person. Reminders are low-risk and usually reduce no-shows. His sales struggle is also instructive for anyone building for restaurants: owners are busy and wary of new software, so a pilot with one place you know personally may teach more than another thousand cold emails. If you're a restaurant owner, ask any vendor how walk-ins are recorded before signing up.

Where the time goes back: Staff stop answering booking messages during service, and reminders go out without anyone remembering to send them.

FAQ

Is this a product?
Yes, the author sells it and was asking for advice on finding more restaurant customers.
Can it handle changes?
The post covers bookings, reminders and questions; we'd send changes to staff unless the book supports them reliably.

Source and credit

Inspired by u/begylewis on r/micro_saas. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Created an AI agent through WhatsApp that manages reservations for a local restaurant. I have one paying customer but can't find more.
Creator
u/begylewis on r/micro_saas
Published on
Reddit
Original date
Oct 23, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
ChatGPT
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Log every agent action as ok, failed or unknown

Give each write an agent makes one structured log line with its attempt ID, request key, an outcome of ok, failed or unknown, and what the agent did next, then keep one saved query for the combination that should never happen, an unknown outcome the agent confirmed to the customer, so a repeat of the incident shows up in minutes.

Credit: ccch713

Under an hour
Operations & AdminWorkflow✓ AI dry run

Pin your agent's write path with one contract test

Build a single fast test workflow that sends the same request key to your agent's booking or order write twice against a stand-in backend, then confirms from an append-only log that exactly one write happened, that the repeat ends as a deliberate skip, and that a forced timeout still lands as unknown and reaches a person, so refactors cannot quietly bring back duplicate writes.

Credit: ccch713

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Catch the emails your AI inbox assistant never processed

Run your AI email triage workflow as usual, label every message it handles, and add a second, independent workflow that once a day searches the inbox for recent mail without that label and sends you the list, alongside retries on the model steps and a production-status sign-in so the trigger does not silently expire.

Credit: Huzaifa_Aamish

Under an hour
Operations & AdminSkill✓ AI dry run

Write an NCR that scopes and locates every suspect part

Use the ncr-writeup skill from Anthropic's Claude for Manufacturing plugin to turn an inspector's finding or a customer complaint into a nonconformance report that records the measured condition, cites the exact requirement at the revision the part was built to, works out how many parts are suspect and why, checks all five places they could be, searches earlier reports for the same problem and drafts a customer notice when bad parts may have shipped.

Credit: anthropics

Under an hour
Operations & AdminSkill✓ AI dry run

Rewrite dense text in plain language without losing facts

Turn a policy, benefits notice or technical announcement into something your actual readers understand, with a check that every number, condition and caveat survived.

Credit: mohitagw15856

Minutes