Can AI take restaurant reservations over the phone?

Yes. A voice agent answers the booking call, takes the date, time, party size, name and contact number, and confirms them by reading them back. If your reservation system is connected, it can check availability and create the booking; if not, it passes the request to your team to confirm. Large groups and private events should go to a manager with a summary.

Can a phone assistant answer allergy questions?

It can share general menu information, but it should never guarantee that a dish is free of an allergen. Only the kitchen can give that assurance. Allergy details are also health-related, which makes them sensitive under KVKK, Turkey’s data protection law. A good setup adds only a “team to call back” note to the booking and leaves the details to a direct conversation with your staff.

Do booking confirmation calls need İYS consent?

A call that confirms a guest’s own booking and contains no promotion can count as a service notification under Turkey’s commercial messaging rules. Adding a new menu, a special night or a discount to the same call may turn it into a promotional call, and promotional calls generally need consent recorded in İYS. Keep the script informational and ask your lawyer about edge cases.

When should the assistant hand the call to the team?

When the caller asks for a person, for large groups or full buy-outs, for complaints and billing questions, for allergy details and for anything not in the knowledge base. The handover should carry the details collected and a short summary so the guest does not have to repeat themselves. If nobody on the floor can take the call, a callback should be logged.

Blog

AI Phone Assistant for Restaurants: A Reservations Guide

A restaurant phone assistant takes, changes and confirms bookings, but never guarantees allergens or haggles on price. Call flows, setup, KVKK and İYS notes.

By SpeaklinePublished October 22, 202610 min read

A phone reservation assistant for restaurants is an AI voice agent that answers booking calls in Turkish, collects the date, time, party size and special requests, and either records the booking or passes it to the team to confirm. It answers questions about opening hours, directions, parking and the menu using information the restaurant has approved, and leaves large groups, private events and allergy details to a person. The aim is not to take your team off the phone altogether, but to make sure no booking request goes unanswered, even at the height of service.

This guide covers why the restaurant phone rings at the worst possible moment, six call flows an assistant can take on, its limits, setup steps, KVKK and İYS notes for Turkey, the metrics to track and a fictional sample call.

Why does the phone ring when service is busiest?

Most calls to a restaurant fall into a handful of groups:

Making a booking, changing its time or party size, or cancelling it
Asking “do you have a table tonight?”
Opening hours, directions, parking, high chairs and pet policy
The menu, vegetarian or gluten-free options and price range
Birthdays, business dinners or large groups that need special arrangements
Delivery or takeaway orders, if the restaurant offers them
Lost property, complaints and billing questions

These calls bunch up at predictable times: just before lunch service, at the start of dinner service and before the weekend. In the weeks before special dates such as New Year’s Eve or Valentine’s Day, booking calls rise further. That is the core problem: the phone rings most when the dining room is fullest.

Typical reasons restaurant calls get missed:

Service comes first. Whoever picks up has to keep a table waiting or let the phone ring, and usually the phone loses.
One line, one person. When two calls arrive at once, the second gets a busy tone.
Closed hours. People often plan tomorrow’s dinner late in the evening or while you are closed.
Noise. Between the kitchen and the dining room, a date or time can easily be misheard, and a wrong booking costs as much as a missed call.

For a caller who gets no answer, ringing another restaurant is usually easier than leaving a voicemail and waiting.

We explain how to measure the impact in our article on missed calls and callbacks, and you can try your own numbers in the missed call cost calculator.

Six call flows an assistant can take on

For each flow, write down four things up front: what triggers the call, what the assistant collects, how the call ends and when it goes to a person.

1. New booking

Trigger: The caller wants to reserve a table.
Details: Date, time, party size, name and contact number; any indoor or outdoor preference and a short note.
Outcome: If the reservation system is connected, availability is checked and the booking is created; if not, the request lands with the team as a single record to confirm. The assistant closes by reading back the date, time and party size.
Handover: Requests above your group limit, set menus and buy-outs.

2. Changes and cancellations

Trigger: The caller wants to change or cancel an existing booking.
Details: The name and date on the booking and the new preference.
Outcome: The change is recorded; a cancelled table reaches the team immediately so it can be offered again.
Handover: The booking cannot be found or the requested time is full.

3. Frequently asked questions

Trigger: Opening hours, directions, parking, menu options, policies on children and pets.
Details: None needed; the assistant answers from the restaurant’s approved knowledge base.
Outcome: The question is answered, and the caller can move straight to a booking in the same call.
Handover: The question is not covered in the knowledge base. The assistant does not guess; it leaves a note for the team.

4. Confirmation calls

Trigger: An outbound call you schedule before evening bookings.
Details: Whether the guest is still coming and whether the party size has changed.
Outcome: The confirmation, change or cancellation is recorded, and the team can reallocate tables of guests who will not come.
Handover: The guest raises a complaint or a special request.

5. After hours and busy lines

Trigger: A call while the restaurant is closed or every line is busy.
Details: Name, number and request.
Outcome: The assistant takes the booking request or the caller leaves a voicemail, and a callback list builds up for opening time.
Handover: The team works through the list when it opens.

6. Special occasions and groups

Trigger: Birthdays, engagements, business dinners or large groups.
Details: Date, estimated headcount, budget range if offered, and contact details.
Outcome: The assistant makes no offer; it collects the basics and passes them to the manager with a summary.
Handover: Always. The point of this flow is to get the request to the right person without losing it.

For ready-made scripts and announcements, see our restaurant and hotel call flows and greeting and after-hours announcements. For changed hours on public holidays there are holiday announcements too.

What the assistant should not do

No allergen or diet guarantees. Whether a dish contains peanuts is the kitchen’s call. The assistant can share general menu information but never confirms that a dish is allergen-free.
No haggling or special offers. Set menus, buy-outs and discounts are decided by the manager.
No guessing at capacity. Without a connected availability feed it does not say “we have a table”; it takes the request and leaves confirmation to the team.
No closing complaints on its own. It listens, summarises and passes the call on.
No payment details. If a deposit is needed, card details are never read out over the phone; the team sends a secure payment method instead.

Setup in five steps

Connect your number. You do not need to change the number guests already know. We compare call forwarding, connecting over SIP and number porting in our guide to connecting your business number.
Write the knowledge base. Opening hours, address and directions, parking, menu summaries, group policy and cancellation rules. Add special-day closures in advance.
Connect the booking flow. If your reservation system can be connected through an API or webhook, the assistant can check availability; if not, requests land on the team’s confirmation list.
Prepare announcements and the KVKK notice. If calls are recorded, the privacy notice must play before recording starts. You will find a sample notice for restaurants in our KVKK guide.
Test. Call from a noisy place, with callers of different ages, using date phrases such as “Friday evening at half past seven” or “Saturday after next”. Our test checklist was written for exactly this.

KVKK and İYS notes for Turkey

This section is general information, not legal advice. Last checked: 2026-10-22.

A booking needs very little information: name, phone number, date, time and party size. Set the assistant up so it asks for nothing more. Article 4 of Law No. 6698 on the Protection of Personal Data (in Turkish) requires personal data to be relevant, limited and proportionate to the purpose. Article 6 of the same law treats data about a person’s health as a special category of personal data. Because allergy information may fall into that category, it is better for the team to talk to the guest directly than to carry the details into call recordings and booking notes. If you record calls, inform callers before recording starts and set a retention period (KVKK and call recording).

For outbound calls the line runs like this: Article 6 of the Regulation on Commercial Communication and Commercial Electronic Messages (in Turkish) says prior consent is not required for notifications about purchases and similar matters, but that such notifications may not promote goods or services. A call confirming a guest’s own booking can be assessed in that light. Calls announcing a new menu, a special night or a discount, on the other hand, are commercial electronic messages and as a rule need the guest’s consent recorded in İYS. We cover the details in our guide to İYS consent rules.

Which metrics should you track?

Metric	How to calculate it	What it shows
Missed call rate	Inbound calls ended without a conversation ÷ all inbound calls	How often the phone goes unanswered during service
Booking conversion	Calls ending in a booking ÷ calls with booking intent	How well the assistant completes requests
Handover rate and reason	Calls passed to a person ÷ calls the assistant answered, by reason	Gaps in the knowledge base and rule settings
Confirmation reach	Guests reached ÷ guests called	Whether confirmation calls go out at the right time
No-shows	Bookings that did not turn up ÷ all bookings	The real effect of the confirmation flow

Set targets against your own baseline rather than other restaurants’ averages. The first number to measure in week one is your missed call rate.

Sample call (fictional)

Fictional example: not a real call; the restaurant and names are made up.
The call takes place in Turkish; shown here in English.

Assistant: Good evening, Liman Lokantası. I’m the restaurant’s AI assistant. How can I help?
Caller:    I’d like to book a table for four this Friday evening.
Assistant: Of course. What time would you like on Friday?
Caller:    Around half past seven. Can we sit outside?
Assistant: I’ll note your outdoor preference; the team will confirm depending on the weather. May I take your name?
Caller:    Deniz Kaya.
Assistant: Thank you. Can we reach you on the number you’re calling from?
Caller:    Yes. Also, my friend has a peanut allergy.
Assistant: Our kitchen team should talk to you about that directly, so I’m adding a “team to call” note to your booking.
           To confirm: this Friday, 7:30 pm, four people, outdoor preference. Your booking is made.
Caller:    Great, thanks.
Assistant: Thank you, have a good evening.

Restaurant calls with Speakline

We build Speakline in Turkey. For restaurants, our voice agent answers booking calls in Turkish, can reply in English to guests who speak English, and collects the date, time, party size and special requests. If your reservation system is connected through an API or webhook, it checks availability; if not, it passes the request to your team to confirm. Calls arriving at the same time are answered concurrently, up to your line capacity.

You run confirmation calls as outbound campaigns within the hours you set, and in promotional campaigns numbers are checked against İYS records. When someone from the team is needed, the call moves with a summary to a queue in our call center (warm transfer) and an operator picks it up from the browser-based desk; if nobody is free, a queue callback or voicemail takes over. Guests’ WhatsApp and SMS messages land in the same inbox. Calls can be recorded and transcribed, and if a call flow has no KVKK notice before recording, the designer warns you. To adapt it to your restaurant, get in touch.