Restaurant dining room set for service

Custom AI receptionists for restaurants

Start free pilotFree pilot. About 14 days to a working line, no call limit.

Why a restaurant needs a custom AI receptionist

Your phone rings hardest in the middle of service, and most of those calls are not reservations. AnswerAI answers the hours-and-parking questions, takes the booking against your real availability, and knows the short list of calls that belong to a person.

A restaurant's phone rings hardest in the middle of service, which is the one hour nobody can leave the floor to answer it. Most of those calls are not reservations (hours, parking, a party that grew by two, whether the table is still being held) and every one of them has a fixed answer that costs a host thirty seconds and a section. AnswerAI answers them in your wording and takes the booking against the availability your host is looking at. It matters more than it did: per-capita spending at Canadian full-service restaurants is still below where it sat in 2019, so the covers you don't take are not made up later in the week.

What do people actually phone a restaurant about?

Mostly not reservations, and almost all of it during service. Hours, parking, a party that changed size, a table being held: factual questions with fixed answers, arriving in the ninety minutes when nobody can pick up.

  • “Table for six at seven - actually, can we do a high chair, and is there parking?”

    A reservation with three complications attached, arriving in the middle of the dinner rush. Answer it and it is a booking; miss it and it is nothing.

  • “We're eight now, not six. Can you still do it, or should we split?”

    The change that decides whether the 7:30 seating works. It has to be answered against the floor plan, and it has to be answered tonight.

  • “We're running twenty minutes late, do we still have the table?”

    Nobody can answer this from the pass, and the alternative to answering it is a no-show that was not one.

  • “Are you open on Monday? Google says one thing and your site says another.”

    High volume, zero judgement required, and it arrives at 6:40pm because that is when the caller thought of it.

Won't it hand out a table we don't have?

Not if it books the way your host books. The line works from the availability already in your reservation system, with your rules attached: party size, turn times, which tables combine, how many covers the kitchen will take in one seating. Where your platform will not let an outside system write, the call arrives as a structured request your host confirms, and we tell you which of the two you are getting before you commit.

This is the fear worth taking seriously in a restaurant, and it is not the one about sounding like a machine. It is that something answers the phone and commits the floor. A book is not a list of open slots; it is covers paced against what one kitchen can send in fifteen minutes, tables that combine and tables that do not, and a 7:30 that is genuinely free unless you have already promised the 7:15 and the 7:45. A system that reads availability as capacity will sell the same window four times, and the people who pay for it are on the line at eight.

So the booking behaviour is built against your floor, not a generic calendar. OpenTable, Resy, SevenRooms and Tock cover most independents and they differ in what an outside system may write; that is a real constraint and we would rather name it than let you discover it in week three. Either your line books directly into the book, or it captures the reservation as a structured request your host accepts in one tap. Both beat a voicemail nobody clears until eleven.

The larger part of the problem is not the booking at all; it is everything else the phone brings during service, and the reason it is expensive is that answering it costs a person on the floor. Hours, parking, the patio, a party that changed size, a table being held. Each has one correct answer that does not change between calls, and none of them needs the judgement of the one host who could be seating table nine. The running-late call is the one with money attached: a table held is a table turned, and a party that could not get through is written up as a no-show it never was.

There is a short list the line does not answer, and it is short on purpose. Anything with a contract behind it, a complaint, and any allergy question that goes past what your menu states; the line reports what a dish contains as written and hands the rest to a person, with the allergy noted on the booking so the kitchen sees it either way. Those calls do not need speed, they need somebody who can walk into the kitchen.

The economics behind all of it are worth stating plainly. Per-capita spending at full-service restaurants is still under its 2019 level, 75% of Canadians say they are eating out less, and independents hold 63.55% of a $124B market, competing for those outings against chains with call centres. That is a margin argument, not a growth one, which is also why you will not find a missed-call percentage on this page. The honest number is the one in your own phone records, and the pilot will show it to you.

What a well-built service-hour call sounds like

A six-top that does not fit at the hour it was asked for, a birthday, a parking question and a warning about traffic, all handled in one call at ten past seven, with no host leaving the floor.

Example call: composite, not a recording

Built from typical service-hour call patterns. No real caller, no real restaurant. Friday, 7:10pm, mid-service, every host on the floor.

  1. Caller

    Hi, do you have anything for six tonight? Around seven-thirty?

    7:10pm on a Friday. This is the busiest phone hour of the week and the one hour nobody is free to answer it.
  2. Agent

    Let me check. Six at 7:30 I can't do as one table - I have 8:15 as a six, or 7:30 across two tables side by side. Which would you rather?

    Real availability read against the floor plan, and the two options a host would actually offer. A line that only checks whether 7:30 is free says no here and loses the booking.
  3. Caller

    8:15 as one table, please. It's my dad's birthday.

  4. Agent

    Done, six at 8:15 under your name, and I've noted the birthday so the floor knows before you sit down. Anything else on it? High chair, anything you'd like on the table?

    The birthday is on the booking hours before the party arrives, which is the difference between a candle in the dessert and an apology at the end of the night.
  5. Caller

    No high chair. Is there parking near you? We're coming from the south.

  6. Agent

    There's the lot behind the building, and street parking on the block north of us. The lot is the easier one at that hour.

    Thirty seconds a host would have spent at the podium during service. Most of the volume is exactly this: a real question with a fixed answer that never changes between callers.
  7. Caller

    Great. We might be fifteen minutes late though - traffic.

  8. Agent

    Noted on the booking. We hold a table fifteen minutes; if it looks longer than that, call this same number and I'll tell the host rather than releasing it. Same line, and it gets answered.

    The hold policy stated at the point of booking, plus a working route for the late call. That is what turns a party stuck in traffic into a table that still turns.

A six-top booked at the size the floor can actually seat, a birthday on the ticket, a parking question answered, and a hold policy stated with a route to use it, from a call that rang at ten past seven, when every host was carrying plates.

A no-show and a party running twenty minutes late are the same empty table - the only difference is whether anybody was free to pick up the phone when they called.

Nick Lovett, Founder, AnswerAI

The quickest way to know is to call it at seven on a Friday, ask for a table for six, and then call back to say you're running late.

Start free pilot

Questions operators ask

That is exactly the window it is for. The busiest phone hour and the least answerable hour are the same hour, which is not a coincidence and is not fixable by hiring. It books against the availability your host is looking at, with your pacing and table rules on it, and it takes the second and third call arriving in the same minute.

It is the main reason to bother. Hours, parking, the patio, a party that changed size, whether the table is still held: all factual, all arriving during service, none of them needing a host to leave the floor.

Those three plus Tock cover most independents, and they differ in what an outside system may write. We will tell you specifically what we can book directly and what arrives as a structured request your host confirms, before you commit.

A line that answers a “we're running late” call converts a no-show into a held table. It can also state your hold policy at the point of booking and confirm ahead of service, if that is how you run.

It will tell a caller what a dish contains as your menu describes it. It will not tell anyone a dish is safe, will not speculate about cross-contamination, and will not reassure. Those go to a person who can check the kitchen, with the allergy flagged on the booking either way.

Nobody credible has published that number. The figures circulating (40%, 43%, 85%) are three different numbers from three vendor blogs with no methodology behind any of them, so we do not use them. Your own phone records are the only honest source, and the pilot will show you.

Let's build one for your restaurant and find out.

We build a working line on your menu, your hours, your floor plan and your reservation rules, and you call it yourself at seven on a Friday. About 14 days. No call limit during the pilot.

Start free pilot