Common Bots (Step by Step)
Build the most requested restaurant bots in minutes using Nuxa Flow.
Use these recipes to ship high-value restaurant bots fast. Each one lists the blocks/tools, a short prompt, guardrails, and the guest benefit.
Prereqs: Knowledge Base filled with menu, hours, delivery zones, and policies; Twilio Voice/SMS connected.
1) Phone Ordering Bot
Goal: Answer calls, take orders, and text confirmations.
Blocks/Tools: Start → Agent → Guardrails → Response → Twilio SMS.
“You are a restaurant assistant. Take phone orders using the menu, fees, and hours provided. Confirm items, modifiers, order type (pickup/delivery), fees, and ready/ETA. Be concise and ask to send an SMS confirmation.”
{ items: [{ name, quantity, modifiers }], order_type, pickup_time, delivery_address?, contact }
Block orders outside hours; enforce delivery zones/fees; require phone for all orders.
Read back the order and total; send SMS summary with pickup/delivery time; post a staff summary.
Benefit: Fewer missed calls, clean orders, happier guests.
2) Reservation & Waitlist Bot
Goal: Book tables within your rules and send SMS confirmations.
Blocks/Tools: Start → Agent → Condition → Response → Twilio SMS.
“Capture party_size, date, time, name, phone, and notes. Follow party-size limits, deposit rules, and blackout dates. Offer nearest available times if full.”
{ party_size, date, time, name, phone, notes, status }
Cap party size; require phone; enforce deposit/cancellation windows; propose alternates if full.
SMS confirmation with details; notify host channel; add a reminder if desired.
Benefit: Consistent bookings and fewer back-and-forth calls.
3) After-Hours Catcher
Goal: Convert closed-hour calls into next-day actions.
Blocks/Tools: Start → Condition (hours) → Agent → Twilio SMS → Email/Slack.
If outside hours, skip ordering; go to after-hours path.
“We’re closed. Collect name, phone, and request (order/reservation/catering). Promise a callback when we open. Offer tomorrow’s hours.”
SMS guest: when you reopen + menu link; email/Slack summary to morning staff.
Benefit: No intent lost overnight; clear expectations for guests.
4) Delivery/Pickup Status Bot
Goal: Proactive SMS updates when timing changes.
Blocks/Tools: Start/API Trigger → Agent → Twilio SMS.
{ order_id, customer_phone, status, eta, pickup_or_delivery }
“Send a concise status update under 320 chars. Include order type, ETA, and next step. If delayed, apologize and give the new ETA.”
Deliver the update; optional follow-up if delayed again.
Benefit: Fewer “where is my order?” calls; happier guests.
5) Catering Intake Bot
Goal: Capture large orders and route to a manager.
Blocks/Tools: Start → Agent → Guardrails → Response → Email/SMS.
“Collect headcount, date/time, budget, dietary needs, contact, and notes. Enforce lead time and minimum spend. Offer alternatives if too soon.”
{ headcount, date, time, budget, dietary, contact, notes }
Email/Slack the request to manager; SMS guest with acknowledgement and next steps.
Benefit: Structured catering leads without long phone calls.
Next: If you need more bots, fork these patterns and reuse the Knowledge Base, guardrails, and SMS confirmations to stay consistent.