The Phone Rings at 22:40: How an AI Agent Takes Reservations After Hours
An AI phone agent takes reservations after hours: it checks real availability, counts the party, gets seating wishes right and hands off to a human when needed.
It is 22:40. The last table is on dessert, the kitchen is being wiped down, and the host stand has been empty for an hour. The phone rings. Somebody wants a table for Saturday. Nobody hears it, and by Saturday the question has been answered by whoever picked up somewhere else.
Booking calls have a shape that order calls do not. They are short — under two minutes, usually. They are worth more than a single order, because a table for six on Saturday is six covers plus drinks. And they arrive at the worst possible times: late evening, Sunday afternoon, the half-hour before opening, the middle of the Friday rush. The overlap between "when people phone to book" and "when somebody can answer" is smaller than most owners think.
What Actually Happens on the Call
An AI phone agent picks up on the first ring, every time, in any of those hours. What follows is worth walking through in detail, because "AI takes bookings" is a sentence that hides all the parts that decide whether it works.
The call opens with the standard greeting: the agent says the caller is speaking to the venue's virtual assistant and that the call may be recorded. A venue can rewrite that opening and can reword or remove the recording sentence; our advice is to keep both. Then it greets the caller by name if it recognises the number, because a guest who has eaten with you before should not be treated as a stranger.
It checks availability against the real book
When the guest names a day and a time, the agent does not guess and does not promise. It checks the actual reservation book for that slot, and for the half-hours around it, so that a full 20:00 comes back as "20:00 is taken — I can do 19:30 or 20:30" instead of a flat no. If the venue is genuinely full, the caller is told so, and offered whatever else exists.
The clock this runs on is your clock. This sounds like a triviality and is not. An agent that resolves "in about an hour" against the wrong timezone will check a slot that has already passed, find it empty, and cheerfully offer a table in the past. The agent reads the time in your venue's own timezone, and refuses any slot that has already gone by — on your wall clock, not a server's.
It counts everybody who needs a chair
Party size is where booking systems quietly go wrong. A guest says "nine of us, four of them children" — that is nine. Another says "two adults and three kids" — that is five. Both phrasings are common, they mean different totals, and getting it backwards means laying a table for two when five people walk in.
The rule is simple and worth stating to your staff as well as expecting from software: a child occupies a chair and needs a place setting, so the party size is everybody. Where a venue tracks children separately — for a kids' menu, a policy, a high chair count — the number of children is recorded as a breakdown of the total, never subtracted from it.
If your venue has a rule about larger groups of children — a limit, a set menu, a surcharge — the agent should only read it out when the rule is actually triggered. A policy recited to a family of three is noise; the same policy withheld from a party of eight is a problem at the door.
It understands where the guest wants to sit
Guests almost never name your zones. They say "somewhere quieter", "outside if it's warm", "near the children's corner", "away from the door". Your seating areas are called "Main Room" and "Garden", and no amount of cleverness gets from one to the other on its own.
So the venue teaches it, in the venue's own words: a short list per area of how guests actually describe it. Main Room — children's corner, with kids, air conditioning. Garden — outside, in the open, smoking. Once that list exists, a guest who says "next to the children's corner" has answered the seating question, and the agent confirms the real area back to them rather than asking "indoor or garden?" as if it had not been listening. That one exchange is the difference between a call that feels handled and a call that feels like a form.
It saves the booking under a name you can actually find
Every booking is saved under a first name and a family name. On a full Saturday, "Maria" is not a booking — it is a guess. If the caller's full name is already on file, the agent asks nothing and uses it. If only a first name is known, it asks for the family name and nothing else. And a guest who plainly does not want to give it is asked once and then left alone: no booking is worth losing over a formality.
What It Deliberately Will Not Do
This part matters more than the feature list, because an operator who is told only the upside stops believing the rest of it.
- •By default it will not change an existing booking. Moving a time, resizing a party or switching an area is handed to a person, because those are the calls where a misunderstanding costs you a table you had already sold. A venue can switch on changes by phone; even then the agent acts only on a phone call, only on a booking under the caller's own number, reads the changed booking back and needs a yes before it moves anything.
- •It will not offer a seating area you do not have. Areas come from your actual floor plan; a wording that points at an area that has been renamed or removed is simply ignored rather than improvised around.
- •It will not book a slot in the past, and it will not book absurdly far ahead — there is a hard limit on how distant a date it will accept.
- •It will not pretend to be a person. With the standard greeting, the assistant disclosure and the recording notice come at the top of every call, in every language, and when asked, it says it is the venue's virtual assistant.
- •When a caller needs a person, it transfers them — to a mobile, or to an extension on your own phone system. Where a transfer is not possible, it takes a number and files a callback instead of quietly dropping the call.
Where the Booking Ends Up
The reservation lands in the same book as one typed in by hand — same floor plan, same day view, same print sheet. Nobody has to check a second screen or a voicemail box. The call itself is stored beside it with a full transcript, so a disputed booking is a thirty-second read rather than a disagreement.
Because the call and the ordering side live on the same platform, one call can do both: a guest who books a table for Saturday and then asks to pre-order the set menu is not two separate systems and two separate confirmations.
How to Introduce It Without Betting the Phone Line
The mistake is handing over your main number on day one. Do not. Start where the loss is provable and the risk is nil.
- •Start after hours only. Forward the line when you are closed. Every one of those calls is currently lost, so there is no downside to compare against.
- •Then add the overflow: staff answer first, and only the calls nobody picks up in a set number of rings reach the agent. Your number and your habits do not change at all.
- •Read the first week of transcripts. Not the summaries — the transcripts. You will find out what your guests actually ask for, which is useful whether or not you keep the agent.
- •Fix what the transcripts expose. Almost always it is the venue's own data: a seating area nobody described, an opening hour that is wrong in the system, a policy that was never written down.
- •Only then consider daytime hours, and only for the periods your missed-call log says you are losing.
Every plan includes a small monthly allowance of calls, which is enough to hear the agent handle your own menu and your own floor plan before deciding anything. Phone your own restaurant after close and try to book a table for six with two children by the children's corner. You will know within one call whether it belongs on your line.
The Honest Summary
An AI agent is not better than your host at the host stand. It is better than the phone ringing out at 22:40, which is what it is actually competing with. Judge it against the calls you are losing today, not against your best server on a quiet Tuesday — and start with the hours where the comparison is not even close.
The AI Voice Ordering feature page covers what the agent can and cannot do and how to hear it on your own venue. If missed calls in general are the problem rather than bookings specifically, our guide on how to stop losing phone orders lays out the cheaper rungs first.
Frequently asked questions
Can an AI phone agent take restaurant reservations?
Yes. It answers the call, checks your real reservation book for the requested slot and the half-hours around it, collects the party size and seating preference, saves the booking under a first and family name, and confirms it back to the caller. The reservation appears in the same book as one typed in by hand, with the full call transcript stored beside it.
What happens if the restaurant is fully booked at the requested time?
The agent checks the surrounding half-hour slots and offers the nearest alternatives — "20:00 is taken, I can do 19:30 or 20:30" — instead of a flat refusal. If nothing is available at all, the caller is told plainly rather than being given a booking that does not exist.
Does the AI count children in the party size?
Yes. Party size is everybody who needs a chair, children included, because a child occupies a seat and a place setting. Where a venue tracks children separately for a kids' menu or a policy, the number of children is recorded as a breakdown of the total, never subtracted from it.
Can an AI agent change or cancel an existing reservation?
By default, changing a booking (the time, the party size or the seating area) is handed to a person, because a misunderstanding there costs a table you had already sold. A venue can switch on changes by phone: the agent then changes only a booking under the number the call comes from, reads it back as it will be and waits for a yes. Cancellation is handled only for a caller whose phone number matches the booking on file.
Do guests know they are speaking to an AI?
With the standard greeting, yes. It opens every call by saying the caller is speaking to the venue's virtual assistant and that the call may be recorded, and the agent says the same if asked. A venue can rewrite its opening line and reword or remove the recording sentence; our advice is to keep both, because the EU AI Act and GDPR expect callers to be told.
Try Ordering.Tools for Free
Set up your digital menu in under 2 minutes. No credit card required.