It's 21:40. Your last covers just sat down, the kitchen is finishing, and the phone rings. Someone wants a table for six on Saturday. Nobody picks up, and that booking goes to the next place on the search results.

So you start weighing the three options every owner-operator eventually weighs: a call center, voicemail, or something that answers and books. Here is how they stack up, side by side.

What each option actually does

A traditional answering service

A call center picks up on your behalf. An agent reads a script, takes the caller's name and number, and promises someone will call back. That is a message, not a table.

The details that matter to your floor - which tables fit six, how your turn times run, whether a party of twelve on a Friday needs the long table - usually aren't in the script. So the booking waits until morning. And most services bill by the minute, which means the longer a guest talks, the more the call costs you.

Voicemail

Voicemail is free, and it never says "we're closed". But a message is not a reservation. A caller who wants Friday at 20:00 hears a beep, hangs up, and dials the restaurant down the street. By the time you listen back, the table is already someone else's.

Voicemail handles one thing well: it proves you were busy. It does nothing to prove you were open.

An always-on host

An always-on host answers the phone the way you would - checks the diary, holds the table, and confirms it. I booked it for you: table 12, Friday 20:00. No callback needed, no caller left hanging.

The difference is what happens next. A host that knows your floor plan can seat the six, flag the allergy, and only ask you when it genuinely matters - a party of fourteen, a buyout, a special request. Everything else gets handled, at 23:00 or at 07:00, while you sleep. It works on email too, so the messages that land in your inbox get the same answer as the ones that ring.

Where the cost shows up

A call center's cost is on the invoice. Per-minute fees, monthly minimums, and overage charges all land in the same place, and they grow with every busy night.

Voicemail's cost is invisible until you count it. One six-top on a Saturday, lost to a missed call, can outweigh months of answering fees. Run that math across a full weekend and the "free" option is the expensive one.

An always-on host sits in a flat, predictable range, and the value is measured in tables kept, not messages logged. The number to watch is simple: bookings per week that you would otherwise have returned too late.

What to look for if you want messages answered and tables booked

Not every service answers and books. When you're comparing, ask:

• Can it take a booking, or only a message? A reservation in your diary beats a note on a pad every time.
• Does it write into the tools you already use? If you run Tableo, the booking should land there, not in a separate app you have to check.
• Does it know when to hand off? Groups, allergies, and events should reach you. Routine tables should not.
• Does it cover email, not just the phone? Guests message both.
• Can you see what it did? You should be able to read back every call and email it handled.
• What does a busy night cost? Per-minute pricing punishes you for being popular. Flat pricing doesn't.

A plain break-even

Line up the three and it comes down to one question: what is a booked table worth to you?

If a group spends, say, 400 at your restaurant, then two recovered group bookings a month tell you more than any feature list. That is the real test. Voicemail recovers almost none of them, a call center recovers some, and an always-on host recovers the ones it answers - which is all of them.

One plain promise

The point of answering isn't to log calls. It's to seat tables you would have lost. Pick the option that books directly into your diary, knows when to hand you the final say, and never sleeps through a Saturday.

You keep the room, the menu, and the last word on groups and events. Everything in between gets answered.

It's 21:40 on a Friday. Every table is seated, the pass is full, and the phone on the host stand rings. Nobody can reach it. A guest with a party of six hangs up after four rings and calls the place two streets over.

That's not a missed call. That's a booking you'll never see in your numbers.

If you run an independent restaurant or a small group of venues, you already answer guest messages yourself - usually between services, and late at night, when you should be done. The problem is the calls that land in the middle of service, the ones that come in after you've locked up, and the ones that arrive while you're carrying plates. Those are the calls that decide whether tonight's covers become tomorrow's regulars.

This is a how-to. Here's how to stop missed calls from eating into your restaurant's reservations, without hiring someone to sit by the phone.

What a missed dinner call actually costs you

A single missed call looks small. Multiplied across a week, it isn't.

Say you miss six calls on a busy Friday and Saturday. Not all of them are bookings, but a good share are - a table for two, a group of eight for a birthday, a regular checking whether you can fit them in at 20:00. If even three of those become reservations averaging four covers each, that's a dozen covers gone in one weekend. Twelve covers at your average spend, every weekend, is a serious line on your annual revenue that never appears on any report, because you can't miss what you never booked.

And it's not only the money. The guest who called at 21:40 and heard nothing doesn't blame the rush. They blame the restaurant. They book elsewhere, and they tell the rest of their party why. Missed calls cost you the table and the reputation in the same four rings.

The bookings you lose most often are the ones worth the most: group bookings and special occasions, because those guests are calling - not texting - to sort out numbers, dates and details.

Why voicemail and hold queues fail during service

The usual fixes don't fix this.

Voicemail asks a guest to leave a message and hope. They won't. A guest with a phone in their hand and three other restaurants to try will not talk to a machine. Most hang up before the beep.

A hold queue only works if someone eventually picks up. During a full service, nobody does. The guest hears ringing, then more ringing, then gives up. Between services and overnight, there's nobody on the line at all.

A generic answering service answers the phone, but it can't see your floor. It can't tell a guest that 19:30 is gone but 20:15 works, and it can't hold the table while you're mid-service. So it takes a message and hands you the work back - exactly the job you were trying to get off your plate.

The result is the same across all three: calls go unanswered when it matters most, and the bookings go to whoever answers first.

How to stop losing dinner bookings to a ringing phone

Here's a sequence you can run this week. It doesn't require new staff, and it doesn't require you to live on the phone.

1. Count the calls you're actually missing

You can't fix what you don't measure. For one week, log every call that rings during service, between services, and after close - and note how many you couldn't reach in time. Most owner-operators are surprised by the volume, and by how much of it lands when the floor is busiest.

2. Cover the hours you can't staff

Your busy hours and your phone's busy hours are the same hours. That's the gap to close first. You need something answering the phone during service, in the dead zone between lunch and dinner, and overnight - when your guests are planning tomorrow while you're asleep. Not a queue that makes them wait. An answer, immediately.

3. Answer, capture the booking, and hold the table

The call has one job: turn a ringing phone into a confirmed reservation. That means picking up on the first ring, understanding what the guest wants, checking what you actually have free, and promising the table on the spot - then telling you what it did: "I booked it for you, table 12, Friday 20:00." No message to chase. No callback to make. The booking is on your floor before you've cleared the next table.

4. Keep the final say on groups, allergies and events

Automation should never make the calls that need you. Groups, allergies and events are judgment calls - your judgment. The right setup answers and books the straightforward reservations on its own, and asks you only when it matters: the party of fourteen, the nut allergy, the private hire request. Everything else flows straight through.

That's the whole idea. Your phone gets answered around the clock, your bookings get captured, and you get asked about the few things only you should decide.

What changes when the phone always gets answered

When every call gets picked up, three things shift.

First, the late calls come back to you. The guest who plans dinner at 23:00 books with you while you're asleep, because you answered when nobody else did. Second, your group and event enquiries stop slipping away - they get captured with the details you need, waiting for your yes. Third, you stop carrying the phone around in your head. You stop apologizing to guests for a ringing line, and you stop wondering how many bookings you lost last night.

You keep the final say on the things that matter. Everything else just gets handled.

The next step

You don't need another hire or another channel to fix this. You need your phone answered during service, between services and overnight, with the booking captured and the table held.

That's what Nomi does. She answers your calls and emails around the clock, books the table, and only asks you about groups, allergies and events. Full house, phone ringing - and this time, someone picks up.

The rules exist. They just live in one head, and they get applied by whoever is nearest to that head. That works while the owner is at the pass. It stops working the first time someone else has to answer at 23:40, or on a Saturday with six calls ringing.

Writing the rules down is not paperwork. It is the step that lets you hand the inbox and the phone to someone else. Here are the five that matter most, and how to write each so nobody has to ask you.

1. The largest group you will book without asking

Every venue has a number where a booking stops being routine. For some it is six, for others ten. Above it, someone needs to look at the table plan, think about the kitchen and maybe talk about a set menu.

Pick the number and write it as one sentence: "We book up to 8 people without checking with the owner. Anything larger goes to the owner, with date, time, size and a contact."

The second half matters as much as the first. A rule that says only "no" loses the group. A rule that says what happens next keeps it.

2. The last seating, and how far ahead you book

Last seating is not the same as closing time. If the kitchen stops at 21:00 and you close at 23:00, a table booked for 21:30 is a table that arrives hungry and leaves angry.

Write the latest time a guest can sit down, per day if it differs: "Last booking 20:30 Sunday to Thursday, 21:00 Friday and Saturday." Then add the horizon: "We take bookings up to 60 days ahead." Without that second line, someone will eventually promise a table for New Year's Eve in March, and nobody will know whether you meant it.

3. Deposits: when, how much, and what happens if they cancel

Deposit rules are where staff improvise most, because the conversation feels awkward. So make it mechanical.

Say when it applies ("groups of 10 or more", or "any booking on a Saturday after 19:00"). Say how much. Say what the guest gets back and by when. A table for ten at €10 a head is a €100 deposit, and the guest should hear that number in the first reply, not in the third.

If the rule has exceptions, write them too, or write that there are none. "No exceptions without the owner" is a perfectly good rule. It just has to be on paper.

4. When the kitchen closes

This one changes with the season, so it is the rule most likely to be out of date. "Kitchen closes at 21:00 from November" is the kind of sentence that gets said once in a staff meeting and forgotten by January.

Write it with the date it starts. Write what you do after kitchen close: drinks only, a short bar menu, or nothing. A guest asking for a table at 21:15 deserves an honest answer about what they will get, not a booking that ends in an apology.

5. Whether you need a phone number before you book

Many venues quietly require a phone number and never say so. Then a host takes a booking on Instagram with a first name only, and on the night there is no way to reach the guest, confirm, or chase a no-show.

Decide it and state it: "No booking without a phone number." Or the opposite: "Email is enough for walk-in style tables." Either is fine. What causes trouble is the unwritten middle, where it depends on who is on shift.

The same goes for cancellations. Decide who may cancel and from where. A cancellation that arrives from a different number than the booking is worth a second look, so write down that it goes to a person.

Write them so a stranger could follow them

A good test: hand the page to someone who has never worked a shift in your restaurant. Could they answer "Is there a table for 12 on Saturday at 21:30?" correctly, using only what you wrote?

If the answer needs "well, it depends", find what it depends on and write that down too. Usually it is one of three things: the number of guests, the time, or the day.

Keep each rule to a sentence with a number in it. Rules with numbers get followed. Rules with adjectives ("reasonable", "usually", "if it's quiet") get argued about.

What changes once the rules are on paper

New staff stop interrupting you with the same five questions. Replies get consistent, so a guest who emails and then phones hears the same answer. And you can finally hand off the channels you do not want to watch at midnight.

It also makes an AI host workable. Nomi, for example, applies these exact rules on her own: kitchen close time, last booking time, deposit policy, the largest group she may book alone (the default is 8) and how far ahead she books. You tell her in plain sentences, such as "deposit for groups of 10+" or "kitchen closes at 21:00 from November", and they apply from the next conversation. Anything outside the rules, like a larger group, an allergy question or a complaint, goes to you instead of being guessed at.

That only works if the rules exist first. An assistant, human or not, can follow a rule. It cannot read your mind. If you have already seen how many bookings arrive when nobody is at a desk, our piece on why restaurants lose bookings after the kitchen closes shows where these rules matter most.

A ten-minute exercise

Open a note on your phone. Write five lines, one for each rule above. Put a number in every line. Then send it to your floor manager and ask what is missing.

Whatever they add is the rule you were applying without noticing. Write that down as well.

Nomi is in testing with pilot venues in Lithuania, and you can see what usage costs on the pricing page. Whether or not you ever use her, the page of rules is worth having by Friday.

For many small restaurants the owner's phone is now the front desk. It buzzes during service, at midnight, on a day off. This article is about getting that under control: a few rules, a few templates, and an honest line for when software should take over.

Why DMs feel harder than email

Email is slow by nature. A guest who emails expects an answer today. A guest who sends a DM expects an answer in minutes, because the app feels like a conversation.

That expectation is the problem. You cannot leave a DM until Monday the way you can leave an email. But you also cannot answer every one while plating food.

The cost is real if you think about one message. Take a table for four at €35 a head: that is €140 sitting in one unanswered DM. We wrote about the same arithmetic for phones in what a missed call costs a restaurant, in euros. The DM version is quieter, because nobody sees the guest leave.

Rule 1: decide when you answer, and say so

Pick fixed windows. For example: before opening, after the lunch rush, and once late in the evening. Three short sessions beat constant glancing.

Then tell guests. Set an Instagram quick reply or an away message that says when you usually answer and where to book if it is urgent. A guest who knows she will hear back by 15:00 is far more patient than one who hears nothing.

Rule 2: one person owns the inbox

If three people can reply, guests get three tones and sometimes two different answers. Name one owner for the DMs each day. Everyone else leaves the threads alone.

If you do share it, write down what a reply may promise. A manager who says "we will find you a table" without checking the plan creates a problem for Saturday.

Rule 3: move the booking out of the chat

DMs are a poor place to keep a reservation. They scroll away, and the booking exists only in someone's memory. Whatever you agree in the chat, enter it in your reservation system straight away, with the guest's phone number.

Ask for the phone number in your first reply. You need it for the booking anyway, and it gives you a way to reach her if something changes.

Rule 4: know what never gets a quick answer

Some messages should not be answered from a phone on the pass. Write the list and keep to it:

• Allergies and dietary needs.
• Complaints.
• Large groups and private events.
• Discounts, press and partnership requests.

For these, send a short holding reply and come back properly. A rushed answer about an allergy is worse than a slow one.

Templates that sound like you

Templates are not cold if they are short and specific. Keep three or four in your notes and change the details each time.

A table is free. "Hello Marta, yes, we have a table for two tomorrow at 20:00. Could you send me a phone number for the booking? We will see you then."

The time is full. "Thank you for writing. 20:00 is full tomorrow, but we have 18:30 or 21:15. Would either suit you?" Always offer two alternatives, not a flat no.

A group enquiry. "Thank you, we would be glad to host you. For groups this size I will check the table plan and reply properly by this afternoon. Which date and how many guests?"

Opening hours and menu questions. Answer in one line and give the link. Do not paste the whole menu into a DM.

Reply in the guest's language where you can. A guest who writes in Polish and gets a Polish answer remembers it.

Where the manual method breaks

These rules work until volume grows. The usual breaking points are:

• Messages arrive at 23:40 and you are asleep.
• During Friday service nobody can touch a phone.
• The same guest writes on Instagram, then emails, then calls, and nobody remembers what she asked last time.

At that point you have two choices: hire someone to sit on the inbox, or let software answer the routine messages and keep the hard ones for you. See also why restaurants lose bookings after the kitchen closes for the late-night side.

What letting software reply should look like

A generic chatbot is the wrong tool. It cannot check your tables, and it makes up answers. What you want is something that reads your live availability, books into your system, and stops when a person is needed.

That is what Nomi, our AI host, does on Instagram. She replies within about a minute, in the guest's language, signed as your restaurant. She checks live availability in Tableo, creates the booking with the guest's phone number and confirms it. She does not invent prices, dishes or free tables.

You keep the controls. Each action has its own switch, including replying on Instagram and creating bookings. You set the largest group she may book alone (the default is 8) and how far ahead she books. Allergies, complaints, private events and discounts always go to a person. If you step into a thread, she stops in that thread.

A sensible way to start is to have everything wait for your approval, read what she would send, and loosen one switch at a time. Every reply shows what it was based on, so you are not trusting a black box.

She also remembers. If a guest asked for the terrace in June and writes again in September, Nomi knows. She never stores health, diet or allergy information.

Nomi is in testing with pilot venues in Lithuania, and early access is by request. Setup takes about ten minutes. A reply costs 4 credits and a booking 6, with 1 credit at €0.10, so a reply and a booking together come to €1.00. Details are on the pricing page.

A simple starting point this week

Whether or not you use software, do these three things in the next few days. Set an away message with your answer times. Write your four templates. Write the always-ask list. That alone will cut the time you spend on DMs, and it makes any later handover to software much easier, because the rules already exist.

So the cost stays invisible. Let us make it visible with arithmetic you can redo with your own figures.

The table that never got booked

Take a table for four. Say each guest spends €35, which is a modest figure for a sit-down dinner. That table is worth 4 × €35 = €140.

Now a normal Saturday. The phone rings six times during the 19:30 rush. Four calls are people who want a table. Two go unanswered because everyone is carrying plates. If those two were tables for four, that is 2 × €140 = €280 gone in one evening.

Four Saturdays make €1,120 a month. Over 52 weeks it is €14,560. That is from one night a week, and it ignores Friday, Sunday and the weekday lunches.

Be fair to the sum. Some of those guests will call back. Some wanted a table for two, not four. Some were only asking about opening hours. Change the figures to match your room. Even if you halve the result, you are still looking at a sizeable number for something nobody noticed happening.

Where the loss happens: the service peak

The cruel part is the timing. Calls arrive in bunches, and they arrive when your people are least able to answer. Between 19:00 and 21:00 on a Friday or Saturday your host is seating guests, your manager is on the floor and the bar is two deep.

The guest on the phone is not planning a dinner for next month. Often they want a table tonight or tomorrow. They have a short list of places, and they will ring down it until someone answers. The first restaurant to pick up gets the booking. Ringing out is the same as saying no.

Hiring another person to sit by the phone for two hours rarely makes sense. You pay a wage for a job that is only busy at the moments you are already busiest, and idle the rest of the time.

Where the loss happens: after close

The second gap is the hours when nobody is at a desk at all. Picture 23:40 on a Friday. A guest sends an Instagram message: "Any table for two tomorrow at 20:00?" Nobody replies until 11:00 the next morning. The guest has booked somewhere else by 23:52, twelve minutes after asking.

That is the point about late enquiries. People decide while they are still thinking about it, usually in bed with a phone. Eleven hours later the answer is correct and useless.

The same goes for calls on a Monday morning, on a closed day, or during the quiet stretch between lunch and dinner when the team is prepping. We wrote more about this in why restaurants lose bookings after the kitchen closes.

Count your own

You do not need software to find your number. A week of honest counting will do it.

1. Look at your phone's missed-call list for the last four weeks and count the calls during service and after close.
2. Ring back a sample. Note how many were booking enquiries, and how many had already booked elsewhere.
3. Multiply the lost bookings by your usual party size and your average spend per head.

Add your Instagram and Messenger messages that waited more than a few hours. Those count too, and they are easier to measure because the timestamps are right there.

What it costs to answer instead

There are two ways to close the gap. One is people: more hours on the phone, someone checking messages at night. That works, and it is expensive. The other is to have something answer for you.

Nomi, our AI host, is built for this. She replies on email, Messenger and Instagram within about a minute, and she books straight into your reservation system after checking live availability. Phone answering on your own number is in pilot with a small group of venues in Lithuania, so we will not claim more for it than that.

The cost is something you can compare with the €140 table. A reply on email, Messenger or Instagram is 4 credits and a booking is 6. A phone call is 5 credits, plus 1 per minute after that. At €0.10 a credit, a call that ends in a booking is 5 + 6 = 11 credits, or €1.10, before any extra minutes. Questions she passes to your team are free.

She does not replace the human moments. Allergies, complaints, private events and large groups go to a person, and you decide where those limits sit. What she covers is the plain question, "is there a table for two on Friday", at the hour when nobody else is free to answer it.

The number to remember

One lost table for four is €140. One answered call costs about a euro. You do not need to be precise about how many you lose to see that the gap is worth looking at.

If you want to see how usage turns into a monthly figure for your venue, the pricing page has an estimator. And if you would rather start with the cheaper step, count your missed calls this week first. The number will tell you what to do next.

Missed restaurant calls are easy to file away as background noise. They are not noise. They are money and bookings walking out on a phone you could not reach.

This guide is about closing that gap without adding a name to the payroll. Not with a voicemail box nobody checks and not by asking your one server to juggle phones and tables at once. With a way to answer and book every call, all night, every night, while you keep the final say on the bookings that actually need you.

What a missed restaurant call actually costs you, in tables and group bookings

Start with the arithmetic, because it is what turns a small annoyance into a fixable problem.

A single missed call is rarely one table. A guest who cannot reach you on the phone does not usually leave a message. They book somewhere else. The average diner spends a set amount per head, so a missed call for a party of four is not one lost seat - it is four covers, plus whatever they would have ordered from the bar, plus the tip.

Then there is the multiplier most operators underestimate: repeat behavior. A guest who books once and has a good night comes back. A guest who could not get through never becomes a regular. You are not losing one dinner. You are losing the whole relationship that dinner would have started.

Group bookings raise the stakes again. Birthdays, work dinners, family celebrations, pre-theater tables - these calls land when you are busiest and they are worth the most. A party of ten is not ten times one guest; it is a deposit, a set menu, a wine order, and a story the guests tell. Lose enough of those and your quiet weekday income quietly drains away.

The worst part is that you never see the loss on paper. There is no line item for the bookings that never happened. That is exactly why this problem survives for years in otherwise well-run restaurants.

Where calls slip through: service hours, late nights, and the channels you already run

Most operators accept missed calls because the gaps look unavoidable. They are worth naming precisely, because that is how you close them.

The service crush. Between 19:00 and 21:30 the phone rings when every hand is on the floor. The room wins that fight every time, and it should. But the caller does not know or care that you are full. They just want an answer.

The late-night window. A guest planning tomorrow's dinner scrolls and calls at 22:30, after your last table leaves. Somebody planning a birthday calls on Sunday morning. Your phone is quiet exactly when your future bookings are being decided.

The channels you already run. Guests do not only call. They send Instagram DMs, Facebook messages, and emails, often through your Tableo profile and your contact form. Each one is a separate inbox that only you know how to check, and each one can sit unanswered for a full day while the guest moves on.

The group and event question. A party of twelve rarely books in one message. They ask about the room, the menu, allergies, the deposit, the timing. That is a real conversation, and it usually happens when you are mid-service.

Notice the pattern: the moment a guest wants an answer is almost never the moment you are free to give one. Staffing around that mismatch means hiring for the hours you cannot predict.

Setting up around-the-clock answering and booking without adding headcount

The fix is not a bigger team. It is making sure every call and message gets answered and booked, then routing only what needs your judgment back to you.

Answer every channel, not just the phone. Set up one place that handles calls, emails, Instagram and Messenger, so nothing depends on which app you happened to open. The goal is simple: no guest message expires because it landed in the wrong inbox.

Let the routine get handled and the judgment come to you. A table for two on Thursday at 19:00 is a decision nobody needs to make twice. A party of fourteen with two allergies and a surprise is your call. The system should confirm the easy ones and hand you the hard ones with the details already gathered.

Keep your rules in the loop. Your opening hours, your table limits, your group policy, your deposit terms. Answering is only useful if it answers the way you would - so it should work inside your rules, not around them.

Make the booking land in the tool you already use. The point is not another dashboard to learn. It is a booking that shows up in Tableo next to the rest, so service runs exactly as it does today.

Give yourself a written record. Every call, every message, every booking should leave a trace you can check when a guest says "I booked for Friday." That single habit ends more arguments than any policy.

This is the work I do. I answer the phone and the inboxes around the clock, I book the tables, and I ask you only when it matters - groups, allergies, events. No hiring, no new system to run, and you keep the final say on every booking that needs a human.

Start with the calls you are missing this week

You do not need a full rollout to see the size of the problem. Pick one busy night and count the calls that go unanswered, the DMs that sit until morning, the group enquiries that never get a reply. Multiply what you find by your average spend. That number is your missed-call bill, and it is the case for fixing it.

Then close the gap: every channel answered, routine tables booked, the decisions that matter routed to you. Your phone keeps ringing. The difference is what happens next.

What happens to a request at 23:40

Nothing, usually. The phone goes to voicemail, the message sits unread, and the person who would answer it is asleep. In the morning there is prep, deliveries and the lunch service, so the reply goes out at 15:00 if it goes out at all.

By then the guest has often booked somewhere else. People who write late are planning something: a birthday, a visit from parents, a Friday with friends. They write to two or three places and go with the first one that answers.

The cost in plain numbers

• A table for four at an average spend of €35 a head is €140.
• Ten such requests a week that go unanswered or answered too late are €1,400 a week.
• Over a year that is more than a host's salary, lost in silence.

Three ways restaurants deal with it

A night phone. Someone on the team takes the restaurant phone home. It works until that person wants a life.

An auto-reply. "Thanks, we will get back to you." It stops the guest booking elsewhere for about an hour.

An AI host. Software that reads the message, checks the floor plan, and books the table on the spot, in the guest's language. This is what Nomi does, and it is why she exists.

What to look for if you try one

Make sure it books into your real reservation system rather than a separate calendar, that it asks for a phone number, that it knows your rules (largest group, last booking time, deposits), and that you can see every reply it sent the next morning.

If that sounds useful, see what Nomi costs. It is less than one host shift a week.