The rebuilt snapshot is approved.
Restaurants receive the assistant Votel designed, safely: orders are priced from their own catalog and paid by link, the kitchen hears when payment clears, tables are booked with reminders, and allergy notes always reach staff.
Payments
No embedded secrets; owner-supplied restricted key; webhook confirmation.
Table booking
Booked in the conversation with confirmations and reminders.
Master generation
Exclude the leftover probe agent when generating the master.
What the final snapshot contains.
Inactive; GPT-5.4 Mini; allergy and payment rules; omnichannel.
Greeting, questions, order intake, pricing, payment link, staff fallback, reservation booking.
Stripe webhook, completed-checkout check, customer lookup, customer and kitchen notices.
Two hours after a reservation, a review text and email.
90-minute bookable with confirmations and reminders.
Order type, items, allergy notes, delivery address, party size, special requests; Menu Price Catalog plus the restaurant globals.
Text version of this diagram
A customer calls, texts or chats and is asked whether they want to order, reserve a table or ask a question. Questions are answered from the restaurant's knowledge base, never with a guarantee that a dish is allergy-safe, and the customer can move on to an order or a reservation. For an order the assistant asks pickup or delivery, takes the delivery address when needed, then the name, mobile number, items, allergy or dietary notes and an optional receipt email, all saved to the contact. An AI step prices the order only against the owner's menu price catalog. If every item matches, a Stripe payment link is created and texted and emailed to the customer, the restaurant is emailed that the order is awaiting payment, and the customer hears that the order is confirmed once paid. If an item is not on the menu or the link fails, the customer is told staff will call, the restaurant gets the order by email and a task is created. For a reservation the assistant asks party size and special requests, then books a Table Reservation; the restaurant gets an email with the time and details and the customer gets confirmations and reminders. If the booking fails, staff are asked to call.
Text version of this diagram
A Stripe webhook for completed checkouts finds or creates the customer by phone or email, emails and texts the customer that payment was received, and emails the restaurant a PAID notice with the order and any allergy notes so the kitchen can start. Other Stripe events are ignored with a note. Two hours after a Table Reservation ends, the guest gets a text and an email asking for a review at the restaurant's review link.
What was proven and what the owner proves.
No dangling links after an editor save; every branch ends.
Orders scored 90 to 96 and a booked table 98 in the simulator.
No API key, webhook URL or recipient from another business ships in the snapshot.
Run the acceptance tests in Stripe test mode, then switch to live keys.
Connect the restaurant, not the logic.
Text version of this diagram
Install the snapshot, set the restaurant globals, add the menu, hours and delivery area to the knowledge base, create Stripe prices and fill the Menu Price Catalog, paste a restricted Stripe key on the payment link step, point a Stripe webhook for completed checkouts at the Payment Confirmations URL, set up and publish Table Reservation, connect an SMS number and email sender and assign the agent to your line or chat, run the acceptance tests in Stripe test mode, then switch to live keys and activate.
Launch approved.
The rebuilt snapshot is ready for master snapshot generation and owner acceptance tests.
Open the buyer-facing guide →