Your hostess is seating guests. Your kitchen is slammed. Your agent answers every call — reservations, takeout, hours, and everything in between.
The dinner rush (5-8 PM) is when the most people call AND when your staff is least available to answer.
Restaurants miss up to 40% of calls during peak hours. That's empty tables you could have filled.
Repeat questions (hours, parking, menu, allergies) tie up staff who should be serving guests.
Every feature below is included on every plan. No add-ons, no feature gates.
Takes reservations through natural conversation. Checks availability, handles party sizes, and confirms.
Answers questions about your menu, dietary options, allergens, and specials from your knowledge base.
Captures details for large parties and private events, then notifies your events manager.
Answers the 20 questions your staff answers 50 times a day — hours, address, parking, dress code.
Tell Allison about your restaurant — hours, menu highlights, reservation policy, dietary options. She builds your agent so it can handle 10 reservation calls simultaneously during the dinner rush.
Watchtower scores every call on resolution, accuracy, professionalism, sentiment, and escalation, and the weakest calls arrive in a Monday digest rather than as a complaint at the host stand. Read it as a general quality signal rather than an allergen safety net: the scorer works from the transcript and is deliberately lenient about reasonable general knowledge, so anything safety-critical still deserves your own spot check of the recordings.
Your agent answers in a voice and name you choose, included on every plan. Hear the voices →
Reservation booking — "Table for four, Friday at 7"
Menu and dietary questions — "Do you have gluten-free options?"
Hours and directions — "What time do you close on Sundays?"
Takeout orders — capturing order details for pickup
Large party and private event inquiries — "We need a room for 30 people"
Your knowledge base is fully customizable from the dashboard.
Yes. Your menu lives in a catalog with prices, sizes, and add-ons, and your agent builds the order conversationally: it asks what they want, captures the customizations, reads the items back with the amount due, and gives the caller a verbal order number. Your team gets an itemized email the moment the call ends and the order lands in an inbox you can work through. Three honest limits, and brief your staff on the first one: the agent says "total" when it reads the amount back, but that figure is the menu subtotal, with tax and any fees added at your register; it does not take payment over the phone; and orders do not auto-sync into Square, Toast, or Clover, though a webhook carries the full order if you want to wire that yourself.
It books into a connected Google Calendar and checks that calendar for conflicts before offering a time. Worth understanding precisely what that means: it is reading calendar availability, not a table map. It does not know your covers, table sizes, or turn times, so a room that can seat three parties at 7pm needs to be modelled as calendars you set up that way rather than as inventory the agent reasons about. Name, phone, the service or table type, and the date and time are what it captures by default; anything else, party size included, has to be asked for in your instructions. If the calendar you connect requires a customer email, the agent asks for one and takes a message rather than booking when a diner declines to give it. If you run OpenTable, Resy, or SevenRooms, a custom integration can reach them only if your plan exposes a write API, which for most single restaurants it does not.
They all get answered rather than queued behind one another. Concurrent calls are not capped on any plan, so the 7pm wave is handled the same as a quiet Tuesday. There is a platform capacity ceiling behind that, and in a rare extreme spike overflow callers are connected to the fallback number you set. That is the practical difference from a host holding one phone during service.
From what you give it, and nothing else. Menu items, prices, and descriptions come from your catalog; allergen protocols, dietary options, and prep details can live as facts, FAQs, or a document it searches during the call. It answers from your material rather than generalizing about restaurant food, and for anything you have not covered it says it will have someone follow up instead of guessing. Given the stakes on allergens, that last behavior is the one worth testing yourself before you go live.
White-glove setup
Custom API integrations, webhooks, CRM sync, escalation design — designed, wired, and tested on live calls. Included with any plan. No setup fees.
Call Allison, describe your business, and she'll build your agent. Or sign up and configure it yourself.