The AI Knows When to Stop — and Who to Call
The AI handles the routine calls. What it does with the ones it should not finish is the important part. Here is exactly how escalation works.
The question most restaurant owners ask before a demo is some version of this: what happens when the AI cannot handle a call? The answer is not a fallback to voicemail. It is a structured escalation system — designed so the team is alerted before the caller even notices something is wrong.
When the AI hands off
There are two categories of handoff. The first is automatic: if the AI's speech recognition confidence drops below 70%, or if the caller explicitly asks to speak to a manager, the AI alerts the front-of-house team immediately — via phone ring or dashboard notification. If no staff member is available to take the call live, the system logs a callback ticket so the team can follow up.
The second category is configured per-restaurant. During setup, the AI is briefed on which request types belong to a person and which it should handle itself. This is where a live deployment differs from a generic bot.
What gets routed to a person by default
From the live DineCall deployments, the requests that consistently go to a person:
Private rooms and large banquets — at Yuan's Garden in Richmond, a caller asking about a private dining room or a banquet for a large group is routed to the team. The AI either hands the call over live or captures the details and flags them for the team.
Allergy flags — a caller who mentions a food allergy is routed to a person. The AI does not take the risk on a dietary restriction; it captures the details and flags them for the team.
Golf bay bookings and private events — at Dimsum Caddy in Richmond, a caller who wants to book a golf simulator bay or inquire about a private event is routed directly to the team. The AI knows what it is and passes the request without guessing.
What happens to the booking request
For table reservations, restaurants choose between auto-confirm and staff approval. Standard booking requests — a party of four on a Tuesday evening — can be confirmed instantly without staff involvement. Unusual requests — a private room, a same-day large party, a booking outside normal hours — can be held. Every booking, confirmed or pending, lands on the live reservation board. The team sees the full picture from the first notification.
What the caller experiences
When the AI routes a call to the team, the caller is not dropped into a voicemail. The AI tells the caller a team member will be with them shortly, or — if no one is available to pick up — captures the reason for the call. The callback ticket means the team follows up with the right context, rather than cold-calling and asking what the original request was.
This is different from an answering machine in every way that matters. An answering machine records a message and hopes someone checks it. A callback ticket is attached to a specific caller, a specific reason, and a time. It is a task, not a recording.
Configured to the restaurant, not generic
The escalation routing is configured during the 2–3 day setup process, based on how the restaurant actually operates. A small counter-service restaurant routes differently than a full-service dining room with private rooms. The AI is briefed on what the team wants to handle and what it should handle itself.
FAQ
Q: What triggers an automatic handoff? A: Two things. First: speech recognition confidence dropping below 70%. Second: the caller explicitly asks to speak to a manager. In both cases the team is alerted immediately — via a phone ring and a dashboard notification.
Q: What if no one is available to take the call? A: The system logs a callback ticket — with the caller's phone number, the reason for the call, and the time. The team follows up with context rather than calling blind.
Q: Can we choose which requests go to a person? A: Yes. The routing is configured during setup. Private rooms, large banquets, catering inquiries, allergy flags — whatever the team wants to handle personally is set that way. Lao Cai routes requests the AI shouldn't settle alone straight to the team. Dimsum Caddy routes bay bookings and private events to the team.
Q: Does the AI take bookings that need staff approval? A: The AI captures the full booking details and holds them for manual approval. Every pending booking lands on the reservation board so the team can confirm or adjust before the caller expects a reply.
Q: How is this different from an answering machine? A: An answering machine records a message. The AI creates a callback ticket with a specific caller, a specific reason, and a time. The team follows up with context. An answering machine is a recording; a callback ticket is a task.