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?
- Define the bookSet tables, party sizes, seating times and how long a table is held.
- Answer from factsLoad menu, hours, location and policies so the agent answers common questions.
- Check before confirmingLook up availability for the party size and time and confirm only real openings.
- Remind and thankSend a reminder before the booking and a short thank-you after.
- 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)
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?
Can it handle changes?
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
- 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.