Every call and message becomes an order or a booking.
Busy restaurants miss orders when the phone rings during service. This snapshot takes the order, collects payment by link, books tables and answers menu questions, and tells the kitchen exactly what to make.
Paid by link
Priced from your catalog, paid through Stripe.
Tables
Booked in the conversation with reminders.
Allergies flagged
Always asked, always passed to staff, never guaranteed.
The snapshot contents.
Voice, text and chat host for orders, bookings and questions.
Orders, payment links, reservations and menu answers.
Stripe webhook that confirms paid orders to the customer and kitchen.
Text and email review ask after each reservation.
90-minute table booking with reminders.
Order details, allergy notes and party details; restaurant settings and the menu price catalog.
Three workflows, one guest journey.
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.
Nine owner steps make it yours.
- 1Set the restaurant globals
Name, timezone, team email for order notices and your review link.
- 2Add your menu
Menu, prices, hours and delivery area in the knowledge base.
- 3Create Stripe prices
One price per orderable item, then fill the Menu Price Catalog.
- 4Add a restricted Stripe key
On the payment link step, allowed to create payment links only.
- 5Connect the Stripe webhook
Completed checkouts to the Payment Confirmations URL.
- 6Set up Table Reservation
Staff, hours and capacity, then publish.
- 7Connect SMS and email
For payment links, confirmations and review requests.
- 8Assign the agent
To your phone line and website chat.
- 9Test in Stripe test mode
Then swap in live keys.
Run the acceptance tests.
Link texted and emailed; restaurant email says awaiting payment.
Customer gets payment received; restaurant gets PAID with the order and allergy notes.
Customer told staff will call; order email and task.
The address is asked once and appears on the restaurant email.
No safety guarantee; the note is on the order and PAID emails.
Confirmation text and email; restaurant reservation email; review request after the visit.
Your restaurant assistant is ready.
When the tests pass in Stripe test mode, switch to live keys and activate.
Open the setup center →