AI Phone Agent for Fine-Dining Restaurants

At 5:40 the book is open on the stand and nobody is at the stand. Pre-service has the captain in the back with the evening's notes, the servers tasting the new amuse, and the phone ringing with a guest who wants to know whether the tasting menu can be done dairy-free for a 60th birthday, and whether there is a cake fee.

That call is worth more than any other call the restaurant takes all day, and it is the one most likely to be answered by whoever walks past.

Fine dining does not have a phone problem the way a pizzeria does. It has a book problem and a manners problem, and a voice agent now touches the manners and can fill a book of its own.

TL;DR

• A fine-dining phone carries two jobs: the book, and the questions around it. The questions are answerable today, and so is the table, if the book is the agent's own.
• The unique failure is confidence about food: an agent that improvises on a shellfish allergy risks a cover, a guest, and a liability, and no vendor should be allowed to try.
• Tone is a specification. A line that sounds like a luncheonette costs more per word than the subscription.
• Kovo books tables in its own book and only reads and texts a page for OpenTable or Resy. On allergens it repeats your words with a disclaimer and never says a dish is safe.
• Kovo is $99 a month for 750 connected minutes, roughly 300 calls, with a 14-day trial and no card.

What a fine-dining phone call is actually for

Sort the calls by what they want, not by who is calling.

• The change. A 7:30 for 4 becomes 8:00 for 5, or a guest needs the corner two-top. This is book work, and it is most of the volume.
• The confirmation. "Are we still on for Friday, and is there a dress code?" Two questions, one of which is in your FAQ and one of which is in the guest's head.
• The dietary intake. The birthday, the allergy, the vegan, the guest who does not eat offal. This is the call a captain wants to take personally, because it decides how the evening goes.
• The pre-arrival logistics. Corkage, the cake fee, parking, walk-in bar seats.
• The event. A buyout for 30, the chef's table, a private room. A person, a minimum, a signed agreement.

The second, third, and fourth are answerable, but only if the answers are written down. The first is answerable when the book is Kovo's own, and a change inside OpenTable or Resy is not. The fifth is a person, at any price. Set expectations by that line before you shop.

The failure this vertical owns: confidence about food

Every vertical has a failure it does not share. A pizzeria's is the half-and-half. A taproom's is the kicked keg. Fine dining's is the agent that answers a dietary question with a straight face.

An allergy answer is not information retrieval. It is a statement the restaurant makes about what happens in a kitchen it does not control at 8:40 on a Saturday: flour in the air, a shared fryer, a sauce finished with butter. A guest with a shellfish allergy who is told "yes, we can do that" and then has a reaction is not a support ticket. It is an incident.

So the rule is uncomfortable and simple: the agent says only what your written policy says, and transfers the rest. Kovo runs a fixed allergen script, repeating your own allergen words with a disclaimer and telling the caller to confirm with the kitchen. It never asserts that a dish is safe, and there is no ingredient database behind the sentence.

The workaround is a paragraph you write once. Something like: we modify the tasting menu with 48 hours' notice, we cannot guarantee a nut-free or gluten-free kitchen, and our pastry kitchen uses wheat flour. Put it on the site, and the phone repeats your sentence instead of inventing one. Put it nowhere, and the agent's honest move is to hand the call to a person.

Tone is a specification, not a nicety

A fine-dining guest forgives a busy signal. They do not forgive being called "buddy" by a robot.

Three things carry the tone, and none of them are the voice model:

• The pace. Turns end after 200 milliseconds of silence, so the agent does not talk over a guest who is thinking. A captain pauses. A drive-thru prompt does not.
• The vocabulary. If the room says "the tasting menu", the agent does not say "the chef's special deal". The words come from your menu and your FAQ, in your spelling.
• The exit. Upsell is a per-shop policy — which categories, a price ceiling, a minimum, and a pinned item — so what this room hears at the close is your setting rather than a vendor default. One clean close, and an offer to have someone call back when the question is not answerable.

That last point is where most demos go wrong, and you can hear it in 2 minutes. Call a vendor's demo line at 3 p.m. and ask about the corkage fee. A product built for pizza tries to sell you a side.

What the phone can take, and what it cannot

The honest table, with Kovo's column in it.

Read the second row twice. The most valuable thing a fine-dining call produces is a cover with a guest's name and dietary note on it, and Kovo can only produce one of those in its own book. In OpenTable or Resy it answers, reads the page back, and transfers. Which book you run is the whole purchase.

The arithmetic: what a missed call costs at one cover

The category numbers are useless here. Use your own cover.

Take your average cover, the one number every operator knows. Industry estimates put roughly 30% of calls unanswered during the 5 to 8 p.m. peak, and about 85% of callers do not ring back after one goes unanswered, as the missed-call arithmetic sets out. Now apply it to your worst night.

• A Friday where 2 calls go unanswered, one a party of 2 for Saturday, at $180 a cover.
• $180 × 2 covers = $360 from one call, on a night you were not full in the first place.
• Do that 3 times a month and you have $1,080, which is nearly a year of Starter at $99.

That is the whole case, and it is not a labor case. Full-service operators reported a median of 36.5% of sales on salaries and wages including benefits in 2024, per the National Restaurant Association, and the point of a phone agent in a fine-dining room is not to remove a host. It is to stop the host being the only thing between a guest and a busy signal at 5:40.

Where Kovo fits on a fine-dining line

Kovo answers the phone, takes orders, reads them back, and sends the ticket to Toast, Square, Clover, Olo, or a receipt printer. It also takes a table in its own reservation book, which changes the arithmetic in this room: the calls that used to ring out at 5:40 have somewhere to land. The ordering matters only if you sell to go: a retail loaf, a bottle, a bar menu for pickup.

What it does well for this room:

• A book that takes the cover. Availability comes from your hours and holiday exceptions, a slot is written once so two callers cannot take the same seat, the desk gets a board, and the guest gets a confirmation text. A shop on OpenTable or Resy has its page read out and texted instead, and the partner cards say pending.
• Hours that include the dark ones. The Google listing syncs, the manual grid survives switching sources, and holiday exceptions and a last-call cutoff are separate, so a caller at 11:20 p.m. gets the truth.
• One set of written answers. Your site, your menu, your FAQ. Answers are cached by content-word signature, so "Fridays" is never served for "Sundays".
• A transfer that behaves. Handoff happens when the caller presses 0 or clearly asks for a person, and only if you have set a handset number. There is no voicemail capture.
• A tested ticket path. A test connection prints one $0.00 ticket before a real order uses it.

The sushi counter guide is the closest read for a room that sells seats and food on the same line. The Toast order path covers what happens to a ticket after the call.

Who this is wrong for

If the booking has to land in OpenTable or Resy, this is the wrong product for that job, and no comparison table can fix that. Kovo reads those pages and texts them; it does not write into them. For the write, keep a person at the stand and look at a voice product that owns the platform integration. Hostie documents OpenTable, Resy, Toast, and Square and puts reservations first; Slang.ai is a reservation-and-questions product whose published pricing was $450 to $600 a month per location in October 2026, and OpenTable keeps a published list of voice AI partners worth checking before you believe any booking claim. Confirm on the vendor's own pricing page before you sign anything.

If you run 2 rooms, Kovo sells one subscription per store: a second room is a second line, a second number, a second menu, and a second subscription, nothing pooled.

And if your calls are 90 seconds of "we're fully committed, try the bar", you do not need an agent. You need the answer recorded, and a host who is not on the phone.

FAQ

Final Thoughts

The decision for a fine-dining room is which half of the phone you are buying, and whose book you keep. If the booking has to land in OpenTable or Resy, buy the platform, the person at the stand, or a reservation-first agent. If you would rather own a simple book and stop losing the calls that arrive while the host is seating, that half is answerable today, along with the questions.

Kovo answers from your own written words, takes the table in its own book or reads and texts yours, keeps the close to the policy you set, transfers what it should not touch, and takes the occasional to-go order at $99 a month. Compare the plans and the 14-day trial, and set a handset number before the first guest calls. Take a test call.