Reservations, takeout orders directed to your system, private-dining and large-party inquiries, hours and menu questions, allergy notes, vendor screening — handled the way a senior host would. So nobody gets hung up on during the rush.
The day your restaurant signs up, the AI already knows how a restaurant runs. It knows the difference between a two-top reservation, a six-top that wants to be near a window, a large-party inquiry that needs to go to the events coordinator, a takeout caller, a delivery question that probably belongs on your third-party platform, and the regular asking whether the kitchen is still open. It knows the words your callers actually use — corkage, family-style, prix fixe, BYOB, last seating, brunch — and how to talk back in the same register.
It captures reservations against your real availability, routes takeout to the online-ordering link or to your call-in line depending on your setup, qualifies private-dining and buyout inquiries with date, guest count, and budget range, and reads back allergy notes so the kitchen sees them. It does not promise a window table when there isn't one, does not over-book the patio when the patio is closed for weather, and does not commit to a menu item that's 86'd.
You stay in control of the specifics — your seating map and capacity, your reservation policy and hold time, your large-party threshold and deposit, your private-dining minimums, your takeout flow, your hours by day, your seasonal patio rules, the dishes you do and don't do off-menu. Your AI fills in what it already knows about how restaurants typically operate, you confirm, and it goes live.
Here is how four common ways to never miss a call compare. See the full comparison →
Give us a try. Our promise: If you don't like our service, you can cancel any time from your dedicated portal.
Connectors to the platforms restaurants most often use are rolling out. While they roll out, every reservation lands in your portal and as a text within seconds, with the party size, time, and notes — your host stand drops it into your book in one motion.
It can — but most restaurants get a cleaner ticket by texting the caller your online-ordering link and reading back the highlights. You set the rule per restaurant; if you take phone orders, the AI captures the order and reads it back before sending it to the kitchen printer or your call-in queue.
It captures date, guest count, budget range, dietary needs, and AV requirements, reads back your private-dining minimums, and routes immediately to your events coordinator. If the inquiry is outside your minimums, it captures the lead anyway so you can refer or follow up.
It captures the specific allergy on the reservation in plain language so the kitchen sees it, and reads back any standing disclaimer you've set — "our kitchen is not allergen-free, but we modify dishes when we can." It does not promise an allergen-free dish.
It handles every call in parallel. Reservations book, the waitlist queues, the special-occasion flag fires, your floor manager gets the text summaries, and nobody hangs up while the host stand is buried.
Yes — caller name, party size, original time, and what changed. It reads back your cancellation policy and any deposit-forfeiture rules so there are no surprises. The modification lands in your portal and as a text for the host stand.
Yes. You edit your hours, your seating rules, your private-dining minimums, your last-seating time, your takeout policy, your menu standing answers, and the way it greets callers — from your portal. Changes go live without re-training anything.