Restaurant Missed Calls: The Booking You Never Knew You Lost

2026-08-17 · Guides

Saturday, seven in the evening, full house. The phone rings, but the waitress is carrying plates and the bar is three deep. The guest hangs up after five rings and calls the restaurant two streets away. You never see that missed call. It just quietly disappears — no note, no message, no trace of the four people who were about to spend an evening with you.

Nobody counts what you lost. At the end of the month you can open a report and see covers, average spend, table turns, cancellations, food cost, labour hours. A restaurant can measure almost everything it does. What it cannot measure is the guest who gave up on the fifth ring. That person leaves no row in any table. There is no line called "revenue we did not get", and that is exactly why the problem survives for years without anyone deciding to fix it.

The calls arrive at the worst possible moment, and that is not a coincidence. Nobody rings a restaurant at half past two on a Tuesday to book Saturday dinner — most people decide where to eat a few hours before they eat, which means the phone gets busy on Friday and Saturday between roughly five and eight in the evening. That is the same window in which your dining room is full, the pass is backed up and every pair of hands is holding something. Peak demand and peak workload are the same hour. It is not a discipline problem or a staffing failure. It is how the problem is built.

An online booking at least leaves a trace. When a guest books through your website, the reservation lands in the system whether anyone was watching or not. Even when there is nothing free, the guest sees it, picks another time or another day, and the restaurant has effectively had a conversation with them without anyone being present. A phone call does the opposite: if nobody answers, nothing at all happened. Not a request, not a rejection, not a name. Silence looks identical to a night when nobody called.

So go and look at last Saturday. This is the one part of this article you can act on today without buying anything. If reservations come to a mobile, the phone itself keeps a list of missed calls — scroll back to last Friday and Saturday and count the ones between five and nine in the evening. If you use a landline or a virtual exchange, most Czech operators and VoIP providers show unanswered calls in the self-service portal or in the call log; the numbers are usually there, they are just never opened. Count them. That figure is yours, from your restaurant, and it beats any number an article could give you.

Then be honest about the count. Not every missed call was a table. Some are suppliers, some are wrong numbers, some are people asking whether you are open on Monday, and some guests do try again ten minutes later. Nobody can tell you what share of those calls would have become a booking, and anyone who quotes you a precise percentage made it up. But the honest answer is not zero either — and on a busy Saturday, one party of six is not a rounding error.

Voicemail is the answer that everyone tries first. It sounds sensible until you listen to the mailbox and find out how few messages are actually in there. Someone who wants a table for four tonight is not going to record a message and then wait to hear whether it worked. They will hang up and dial the next place on the list. Voicemail catches the patient guest, and the guest deciding where to have dinner in the next thirty minutes is not patient.

Calling back later has the same flaw, one step further along. In practice, "later" means after service — half past ten, when the kitchen is closed and you finally sit down. By then the guest has been sitting somewhere else for two hours. Calling back works for next weekend's booking and for the group enquiry, which is genuinely worth doing. It does not work for tonight, and tonight is where most of the loss is.

Hiring someone to answer works, and that is the problem with it. A person on the phone handles the awkward cases, hears the tone of voice, knows that the corner table is worth offering. It is also the most expensive option available, and the shape of the demand makes it worse: you need that person for a handful of hours on Friday and Saturday evening, not for a shift. Very few independent restaurants can justify paying for a phone that only rings hard for six hours a week.

And then there is the language. A German family in Prague, an Italian couple in Český Krumlov, an Austrian group in the border regions — they ring, someone picks up mid-service, and the conversation is short, polite and produces no booking. Nobody did anything wrong. The waiter was busy and the guest did not speak Czech. That call is a lost booking in exactly the same way as the unanswered one, except it hurts more, because someone actually answered it.

This is why we are building an AI receptionist into Stolio. The idea is deliberately unambitious in one respect: your number does not change. Guests keep dialling the number that is on your door, on Google and on every menu you ever printed. When nobody picks up after a few rings, the call goes to the AI instead of into nothing. It answers in the name of your restaurant and has a normal conversation about a table.

To be clear, we are not the only ones doing this. AI phone answering for restaurants exists elsewhere — Slang.ai, Loman and Newo do versions of it, and OpenTable and SevenRooms have their own. The difference we care about is what the AI is connected to. Ours talks directly to the reservation system, so it is not taking a message for someone to process later: it looks at real table availability for that date and time, offers what is actually free, creates the reservation, and the guest gets an SMS confirmation before they hang up. It is also built for the Czech market, which sounds like a smaller claim than it is — until you have tried explaining Czech street names to a system designed for New York.

When it is not sure, it hands over. A group of eighteen, a question about allergens, a complaint, a request that does not fit any rule — the AI is not supposed to improvise its way through those. It passes the call to a human, or takes the contact details and flags it so somebody calls back knowing exactly what the guest wanted. A receptionist that confidently invents an answer is worse than a phone that rings out.

It speaks the guest's language — Czech, English, German and Italian — which is the part that matters most in Prague and in the border regions. One note so there is no confusion: this is about the phone conversation with your guest. The Stolio dashboard and our support are currently in Czech and English only.

The second use is the day before. The same system can call your bookings the day before to confirm — a simple question, yes or no, and a table released back into the system when the answer is no. This is worth saying carefully: deposits do reduce no-shows, that is not in dispute. The catch is that they also cost you bookings, because a share of guests abandon the booking flow the moment they are asked for card details. A short confirmation call the day before does not scare anybody off, and it turns a table that would have sat empty into one you can still sell.

The Stolio AI receptionist does this today. Get in touch and we will set it up for your restaurant — and give you a number to call first, so you hear exactly what your guests will hear.

Everything else in a restaurant gets counted. Waste gets counted, labour gets counted, covers get counted. The guest who hung up on the fifth ring does not, and that is the whole reason the problem is comfortable to ignore. You do not need us to do the first step: open last Saturday's call log and look at the number. Whatever it is, it is bigger than the zero you have been working with. If you want the reservations you do catch handled properly in the meantime, Stolio starts at 499 CZK a month with no commission per booking, and you can try it free for 14 days.