It's 10:40 on a Tuesday night. The last table left twenty minutes ago, the kitchen is dark, and you're doing the final count of the till when the phone rings. You look at it. You know exactly who it is: someone wanting to book a table for Saturday, or asking if you have gluten-free options, or checking whether you're open on a public holiday. You answer it, because you always do, and the evening that was supposed to end at 10:30 ends at 11.
Or you don't answer it, and the caller rings the restaurant two streets away, and someone there picks up.
Answering the phone after hours for restaurants is one of those problems that never makes it onto a business plan but quietly shapes your week. This article walks through what's actually happening on those calls, what the realistic options are, where each one falls short, and a practical setup that works for most independent restaurants and small chains.
Why restaurants get so many after-hours calls
Restaurants are unusual businesses. Your customers plan their evenings around you, and people plan their evenings at odd hours. Someone books a table at 9pm while watching TV. Someone else remembers at 7am on Sunday that they need a table for a family birthday that afternoon. Office managers order lunch for fifteen people the night before, once the meeting is confirmed.
The calls themselves are usually simple. In most restaurants, after-hours calls fall into a handful of buckets:
- Bookings for tonight, tomorrow or the weekend
- Opening hours questions (are you open, when does the kitchen close, are you open on holidays)
- Menu and dietary questions (allergies, vegetarian options, kids' portions)
- Takeaway or delivery orders where people prefer to call rather than use an app
- Changes and cancellations to existing reservations
- Private events and group enquiries
- Genuine problems, like a lost wallet or a complaint about tonight's meal
Notice something: most of these are routine and predictable. A few genuinely need a person. That split matters for everything that follows.
What missed after-hours calls actually cost a restaurant
There are no universal statistics here, and anyone quoting you a precise percentage of lost revenue is guessing. But you can work out your own number in about fifteen minutes, and it's worth doing.
Check your phone log for the last two weeks and count the calls that arrived after you stopped answering. Then think about what a typical call is worth to you. For most restaurants, a booking call represents a table of two to four people, and an order call represents a takeaway ticket. You know your average spend better than anyone.
The harder cost to see is habit. A caller who reaches voicemail once may try again. A caller who reaches voicemail three times in a row usually stops trying and quietly becomes someone else's regular. You'll never see that in any report, because the call simply stops coming.
Then there's the cost on the other side: answering. If you or your manager personally pick up every after-hours call, you're doing unpaid work at the exact hours you should be recovering. Restaurants already run on long days. Adding an hour of phone duty after close, every night, is how good operators burn out.
Your main options for answering the phone after hours
There's no single right answer, but there are four realistic approaches, and they can be combined.
1. Voicemail, done properly
If you're going to use voicemail at all, make it earn its keep. The greeting should state your opening hours, your address or area, and one clear instruction: what the caller should do next (leave their name, number, party size and preferred time, and you'll confirm by text or call back in the morning). Then — and this is the part most restaurants skip — actually call people back first thing, before service prep eats the morning. A callback at 9am converts far better than one at 2pm.
Voicemail's weakness is obvious: many callers won't leave a message, especially younger ones, and especially for same-evening bookings where they need an answer now.
2. Divert calls to a mobile
Simple and free: forward the restaurant line to your mobile or a manager's. The downside is just as obvious — someone has to live with that phone, answer it during family dinners, and field spam calls at 11pm. This works as a short-term fix or for a genuinely quiet period, but as a permanent arrangement it usually ends with someone resenting the phone.
3. A human answering service
Traditional answering services employ people who pick up in your restaurant's name, take messages and follow a script. They're a real step up from voicemail because a live voice keeps callers engaged. The trade-offs: quality varies a lot between providers and between individual agents, the agents rarely know your menu or your floor plan well enough to answer detailed questions, and round-the-clock human cover is priced accordingly. For some restaurants it's exactly right; for others the cost doesn't stack up against the volume of after-hours calls.
4. An AI receptionist
This is the newer option, and it's where the routine-versus-personal split from earlier really pays off. An AI receptionist answers every call immediately, any hour, speaks naturally, and can handle the predictable work: taking a booking with date, time and party size, answering opening-hours and common menu questions, recording order details, noting cancellations, and taking a clean message for anything unusual. You get a summary of each call rather than a pile of voicemails.
It suits restaurants particularly well because so much of restaurant call volume is structured. "Table for four, Saturday, seven-thirty" is a conversation with a clear shape. Ringhum for restaurants is built around exactly these calls, and it also answers on WhatsApp for the growing share of customers who'd rather message than ring.
A realistic evening, with and without after-hours answering
Here's a made-up but typical night for a neighbourhood Italian restaurant with about fifty seats.
Without any system. The kitchen closes at 10pm. Between 10pm and midnight the phone rings six times. Two are people wanting a table for tomorrow night. One is a group of eight asking about a birthday dinner in three weeks. One is a takeaway order. One asks if the restaurant is open on Monday. One is a cancellation for tonight, which is now useless anyway. Nobody answers. In the morning there's one voicemail — the birthday enquiry — because the other five callers hung up and either booked elsewhere or gave up. The morning manager spends the first twenty minutes of the day playing catch-up on a day that already started behind.
With an AI receptionist answering after hours. Same six calls. The two booking requests are taken with names, numbers, times and party sizes, and confirmed. The birthday enquiry is captured in full detail — date, size, dietary notes, contact details — so the manager can call back with a proper proposal instead of a cold "you rang us?" The takeaway order is recorded and passed on. The Monday-hours question is answered on the spot. The cancellation frees a table that the restaurant can now offer to the next caller. The manager arrives to a tidy list of six summaries instead of a blinking voicemail light.
Nothing about that second scenario is magic. It's just every call getting an answer, and every answer landing somewhere organised.
Setting it up: a practical checklist
Whichever route you choose, the setup work is similar. An hour spent here saves confusion later.
- Write down your actual opening and kitchen-closing times, including any days that differ and upcoming holiday dates. This is the single most-asked after-hours question.
- Decide your booking rules: maximum party size for an automatic booking, how far ahead bookings can be made, and whether you hold tables without a card or deposit.
- List the ten questions callers ask most — parking, allergens, kids, dogs, wheelchair access, corkage, group menus — and write one clear answer for each.
- Define your handover rule: which calls should always reach a human? (Complaints about tonight's service, suspected allergies needing detail, press enquiries, emergencies.) Make this explicit.
- Decide how you receive summaries — email, text or dashboard — and who reads them each morning.
- Record or set a greeting that sounds like your restaurant, not a call centre.
- Test it yourself. Ring your own number after close on three different nights and try to break it. Book a table, ask a weird question, cancel something. Fix what feels off.
Common mistakes to avoid
A few traps catch restaurants again and again.
Letting the greeting go stale. If your recorded message still mentions last month's holiday hours, callers lose trust in everything else it says. Review it monthly; it takes two minutes.
Taking bookings without confirmation. Whatever system you use, the caller should leave the conversation knowing the booking is real. Ambiguity produces no-shows and double-bookings.
No owner of the morning callback. If "someone" is responsible for returning after-hours enquiries, no one is. Name a person and a time.
Answering everything yourself forever. Owner-answered phones feel personal, and regulars do love it. But it doesn't scale, it doesn't survive your holiday, and it quietly caps your restaurant at the hours you're willing to be interrupted.
When a person should still take the call
Be honest with yourself here: not every call belongs with any automated system, and the good setups are explicit about it.
A guest calling to say they felt unwell after tonight's meal needs a person, quickly. So does a serious allergy conversation where the kitchen's judgement matters, a large private-hire negotiation, a journalist, or a supplier dispute. These calls are rare — a small fraction of volume — but they're the ones where tone, judgement and accountability matter most.
The right model for most restaurants is a filter, not a replacement: routine calls get answered and resolved automatically at any hour; the few sensitive calls get recognised, a detailed message is taken immediately, and you call back personally. If a caller's situation sounds urgent, your system should say so and escalate rather than improvise. You can read more about how that handover works on the Ringhum blog, and typical costs are on the pricing page.
Frequently asked questions
Is voicemail good enough for after-hours restaurant calls?
It depends on the call. For enquiries that can wait until morning — a booking for next week, an event enquiry — a clear voicemail with a promised callback time works reasonably well. For same-evening bookings and orders, callers usually need an immediate answer and will simply ring the next restaurant instead. Voicemail costs you most on the calls where timing matters.
Will an AI receptionist actually understand my customers?
Modern AI receptionists handle natural, messy speech well: accents, background noise, people changing their mind mid-sentence. They're strongest on structured conversations like bookings, hours and orders. Where they're honest about limits is unusual or emotional situations — a complaint, a complex allergy discussion — which is why a good setup always includes a clear handover to you for those calls.
What happens to bookings taken overnight?
The booking details — name, contact number, date, time, party size, any notes — are captured during the call and sent to you as a summary, typically by email or text. You arrive in the morning to a list of confirmed overnight bookings rather than a voicemail queue. You still control the diary and can adjust anything that clashes with walk-ins or large tables.
How do I stop after-hours calls interrupting my evenings?
That's largely the point of delegating them. Forward your restaurant line to an answering option after close, keep your mobile for genuine emergencies, and define what counts as one. Most owners find that once routine calls are handled elsewhere, the truly urgent after-hours calls are rare — and far easier to deal with when you're not already exhausted.
Can it answer questions about our menu and allergens?
It can answer the questions you prepare answers for: whether you have vegetarian dishes, gluten-free options, children's portions and so on. What it should never do is improvise on serious allergies. Set a firm rule that detailed allergen conversations are handed to the kitchen or manager, because the consequences of a wrong answer there are serious.
The next step
Start with the fifteen-minute exercise: count your missed after-hours calls from the last fortnight and put your own value on them. That tells you whether this is a nuisance or a leak worth fixing properly.
If it's worth fixing, choose the lightest option that actually answers the phone: a disciplined voicemail-and-callback routine costs nothing and already beats silence. If your call volume or your evenings justify more, an AI receptionist is the most practical round-the-clock option for most independent restaurants — every call answered, bookings taken, summaries waiting in the morning, and a clear rule for the calls that should reach you personally. Ringhum does exactly this: it answers your restaurant's calls around the clock, takes bookings and orders, handles common questions and messages on WhatsApp, and passes the sensitive calls to you with the details already captured. It won't replace your judgement on the calls that need it — and it isn't meant to. It just makes sure nobody rings an empty room.