A restaurant phone has a different failure mode from a salon's. The salon misses calls because one person is busy for forty minutes at a time. The restaurant misses them because for two hours nobody can reach a handset at all, and those two hours are when most of the calls arrive.
An AI receptionist for a restaurant is judged on the rush. Everything else is secondary.
What it has to survive
Several calls at once. This is the specific thing human coverage cannot do during service, and it is the main reason to have one. Three simultaneous callers at seven on a Friday is not a staffing problem you can solve by hiring one more host.
Noise on both ends. A dining room behind the handset, a street behind the caller.
Party size, which changes everything. "Four" and "fourteen" are different products. Fourteen is a large-party conversation with different rules, often a different room, sometimes a deposit.
Turn times that are not a fixed grid. A two-top at six and a six-top at eight occupy the floor differently. A system offering slots from a generic calendar will overbook you in a way that only becomes visible at the door.
What it should handle without anyone touching it
Reservations, changes and cancellations. The core. A cancellation captured at nine on Saturday is a table you resell; one sitting in voicemail until Monday is a table you did not.
The hours question. Are you open, are you serving, are you open on the holiday. Enormous volume, no judgement, and it consumes more host attention than anything else on the list.
The where-are-you question. Parking, the entrance, which side of the street.
What it must refuse, every time
Anything about allergens. This is not a place for a confident guess, and a system that reassures a caller about nuts or shellfish is a genuine liability rather than a support inconvenience. The correct behaviour is to say plainly that a person will call back, and then make sure that happens.
We treat this as the single most important test of any restaurant system, and it is one of the five in five calls to make before you trust an AI receptionist. Ask the vendor's demo line whether a dish can be made without nuts. If it answers, walk away.
A complaint. Someone ringing about last night's meal needs a person, immediately, and should not be asked to describe the problem to a machine first.
A large party with conditions. Fourteen people, a set menu, a specific room, a time you would normally refuse. That is a conversation with a manager.
The part that decides whether it works
It has to read your real floor, not a slot grid. If it books a six-top into a window that only holds four, you have moved the problem to the door, where it is worse — a guest standing in front of you with a confirmation for a table that does not exist.
This is the question to press hardest on with any vendor. Ask specifically: does it know my table configuration and my turn times, or is it offering slots from a calendar? The answers diverge quickly.
What it is worth
Do this with your own numbers rather than an example.
Count the calls you miss during service for one week — your phone system or carrier can usually tell you. Take the share that were reservations, which for most restaurants is the majority. Multiply by your average cover value, then by party size.
Say you miss twelve calls a week during service, seven were reservations, average party of three, average spend of forty-five a head. That is roughly nine hundred and forty-five dollars a week of covers that rang and got nothing. Whether covering that is worth paying for becomes an easy question, and you answered it without trusting anyone's marketing.
The number people forget is the second visit. A first-time guest who could not get through never becomes a regular, and they never appear in the count at all.
Being straight about the limits
It speaks English today. Ours does. Ask directly rather than accepting a roadmap date.
It will mishear things. Every system does, and a dining room is a hard listening environment. What matters is whether a mishearing becomes a question — "was that four or fourteen?" — or a confident booking.
It does not replace a host. A host reads a room, manages a queue, handles a walk-in, recognises a regular. What this removes is the interruption during service, not the role.
Starting on one service
You do not need to hand over the line. Conditional call forwarding passes only the calls nobody picks up, so during a rush the overflow goes somewhere that can take a reservation while your handsets keep working exactly as they do now. The codes by carrier are in the call forwarding guide.
Run it through one Friday and one Saturday, then count the reservations that came back from calls that would previously have rung out. That is the only test worth running.