How an AI host takes reservations
Evoriqa Team · June 22, 2026 · 6 min read

During a busy service, nobody has a free hand to answer the phone, and that's exactly when guests are trying to book a table, ask about a dish, or plan a large order. But not every question a restaurant gets is a good fit for automation on day one. Some are safe and repetitive enough to hand over straight away. Others need a person every time. Getting that split right is what separates a useful AI host from one that gives a guest the wrong answer at the wrong moment.
This is a guide to the order you automate in: which questions to give an AI host first, which to hold back, and where the allergen question in particular needs a firm boundary. For the wider picture of what an AI host does across a restaurant, see the restaurant support solution.
Rank your questions by two things
Before you automate anything, list the questions your team answers in a week. The list is usually short: opening hours, location and parking, whether you take walk-ins, table availability and reservations, menu and price questions, dietary and allergen queries, private hire, and catering or large orders.
Score each one on two axes. How repetitive is it? Do you answer it several times a day, or once a month? And how safe is an automated answer? If the agent gets it slightly wrong, is that a mild inconvenience or a real problem for the guest? The questions to automate first are the ones that are both highly repetitive and low-stakes. The ones to hold back are low-volume, high-stakes, or both.
| Question type | How repetitive | Safe to automate? | Who handles it |
|---|---|---|---|
| Hours, location, parking | Very high | Yes, automate first | AI host |
| Table availability and reservations | Very high | Yes, through your booking tool | AI host, human for exceptions |
| Menu items and prices | High | Yes, from your own menu | AI host |
| Dietary options (vegetarian, vegan) | High | Yes, with careful wording | AI host |
| Allergen safety for a specific guest | Medium | No, needs care | Human every time |
| Private hire and large parties | Medium | Capture, don't close | Human, after the AI logs the lead |
| Catering orders | Medium | Capture, don't close | Human, after the AI logs the lead |
| Complaints and refunds | Low | No | Human every time |
The top rows are plain facts that don't change during service: your hours, where to park, what's on the menu, what a dish costs. An AI host answers them from your own content, so the reply matches what you've actually published rather than a guess. Grounding every answer in your own knowledge is what keeps those replies accurate, and it means the agent updates the moment you change a price or pull a dish.
The dinner-rush hour is where this pays off
The dinner rush is the sharpest test. The phone rings while every table needs attention, and DMs on Instagram and WhatsApp pile up unread. It's the worst possible time to lose a booking and the best possible time to have already automated the questions at the top of that list. An AI host picks those up the moment they arrive — on your website, on WhatsApp, on Instagram, and by phone through an AI voice agent — so your team can stay on the floor.
By the tenth "are you open tonight?" of the evening, the host stand is better spent seating the party at the door than repeating a fact the AI host already reads off your published hours. Those repeat, low-stakes questions are exactly the top band you scored to automate first; a genuinely unusual request still reaches a person. Start with that band, watch how the agent handles it for a week or two, then widen the set once you trust it. Resist widening it all at once. Each new question type you hand over is one more place a wrong answer can reach a guest before you catch it.
Where to draw the line on allergens
Allergen questions are common enough that you'll want to automate them, but they carry real risk, so they need a firm boundary. The trick is to split the question in two.
There's the factual part: what a dish contains, and what your published allergen information says. An AI host can answer that from your own menu and allergen matrix, the same way it answers a price. If that information isn't in your content, a well-built agent says it doesn't know rather than inventing an answer, which is exactly the behavior you want here. A confident guess about allergens is worse than no answer at all.
Then there's the assurance part: "I have a severe nut allergy, is this dish safe for me?" That is not a factual lookup. It depends on how the dish is prepared that night, on shared fryers and surfaces, and on a kitchen's judgment about cross-contamination. No automated answer should promise a dish is safe for a specific guest. Set the agent to give the published facts and then hand the conversation to a human, with the full thread attached, so a member of staff makes the call. The guest still gets an instant, accurate first reply; the promise still comes from a person who can check the kitchen.
Reservations: automate the ask, confirm through your booking tool
Reservations usually sit near the top of the list on both axes, but a booking is an action, not just an answer. An AI host takes the request across your website and DMs and passes it to your booking tool, so availability and confirmation come from the system that actually holds your tables rather than from the agent's own guess.
The exceptions are where a person steps in: a party larger than your online limit, a specific room, a set menu, a date you keep closed. The agent should route those to staff instead of trying to confirm them itself. That way the routine bookings clear on their own and your team only touches the ones that genuinely need a decision.
Catering and private hire: capture, don't close
Catering, large parties, and private hire are leads, not FAQs, so handle them differently. These enquiries are worth real money and usually need a conversation about dates, headcount, and menu. Don't ask an AI host to close them. Ask it to capture the lead — name, date, party size, what they're after — the moment it lands, including from an Instagram DM at eleven at night, and route it to whoever owns events.
The job of automation here is narrow on purpose: make sure the enquiry is recorded and reaches a person quickly, so it never sits unread in a DM folder over a weekend. Closing the booking stays with your team.
Put it in order
To recap the order of play: automate the repetitive, low-stakes questions first: hours, parking, menu, availability. Automate allergen facts, but hand the safety assurance to a person every time. Capture catering and private-hire leads, and let staff close them. Keep complaints and refunds with a human. Start narrow, watch what the agent handles well, and widen from there.
That order keeps your team on the floor during service, gives guests an accurate reply wherever they message, and draws a clear line around the questions that need a person. Create your workspace free and have an AI host answering from your own menu, handing the tricky questions to your team.