Channels
Each channel is switched on or off for your venue. They all read the same menu, the same hours and the same record of guests, so none of them disagrees with another. Keep what you already use; add the ones you want.
Your own website, with the menu, your hours and a book or order button, on your own domain or a free address. It is built from ready-made blocks, so you change words and pictures, not code.
Hours and the menu live in one place. Change them once and the website, the QR menu, online ordering and anything a guest’s assistant says about you all change together.
A code on each table opens the menu, with today’s specials and what has sold out. When you are ready for it, guests order and pay from the table too, and the order lands on the kitchen screen with the table number.
Start with the menu only. Switch on ordering from the table later, or never. Either way the code never goes out of date, because it reads the same menu as everything else.
Pickup and table orders from your own site: a cart, pickup times paced so the kitchen is never swamped, checkout, and payment into your own Square account. A kitchen screen shows the orders beside the dockets.
You keep your prices and your guests. Nobody sits between you and the person ordering.
Delivery from your own site. You draw the suburbs you deliver to, a courier you connect (Uber Direct or DoorDash Drive) gives a quote, and the pickup is timed so the food leaves when it is ready, not when the driver happens to arrive. The guest sees where their order is.
The courier connections are built and tested against simulated couriers only, so far. No real delivery has been dispatched through them yet.
Guests book a table for a time and a party size on your site or through their assistant. You confirm, or let bookings confirm themselves within the numbers you set. Capacity is counted in guests per time slot and per service, so there is no floor plan to draw.
The guest gets a confirmation by email or text. A booking never adds anyone to a marketing list.
Guests use assistants too. With this channel on, a guest asking ChatGPT or Claude can find your venue, read the menu and hours, book a table, and start a pickup order. The order is paid on your own order page, in your own account.
In Australia, no payment is taken inside the chat. As of October 2026, paying inside ChatGPT or Claude is not available to Australian venues, so the guest finishes paying on your page. Alcohol is never offered this way. Each assistant maker decides what appears in its own directory.
Channels are plugins, like everything else. Your assistant can switch them on and set them up for you, asking first. Or start with none of them: the record, the definitions and the guardrails around your assistant are the product, and they work with the tools you have today.