It's a quarter past seven on a Saturday. Every table is full, two tickets are waiting at the pass, and the host is walking a party of six to their seats. Then the phone rings. Someone wants a table for tomorrow, someone else wants to know if you do gluten-free pasta, and a third caller wants to order a takeaway. Nobody has a free hand. This is the problem an answering service for restaurants exists to solve: the phone keeps ringing at exactly the moments your team can't pick it up.
A good answering service takes those calls so they don't go to voicemail or ring out. It books tables into your system, takes orders, answers the questions you hear every day, and passes anything unusual to a person with a clear message. It doesn't replace your front-of-house team. It protects their attention for the guests already in the room.
This guide covers what the service should handle, what to check before you choose one, what to avoid, and which calls should always reach a human.
Why the phone is the hardest job in a busy restaurant
In most businesses, the phone is busiest when staff have the most time. In a restaurant, it's the other way round. People call to book and order around mealtimes, which is when everyone on shift is already stretched.
That leaves you with a few bad options:
- Answer anyway. A server leaves a table mid-order, or the host takes a booking while guests wait at the door. Both guests lose.
- Let it ring. The caller often just tries the next place on their list. You never learn the booking or order existed.
- Send it to voicemail. Messages pile up, get checked late, and callers who wanted a table tonight have already gone elsewhere.
There is also the phone outside service: early morning before anyone arrives, the afternoon gap between lunch and dinner, and late at night. Callers plan their evenings at all of those times.
What a restaurant answering service should actually handle
Not every call is the same. Sort them into groups and decide how each should be handled.
Reservations
This is the core job. The service should check availability, take the name, party size, date, time and phone number, note special requests like a high chair or a birthday, and confirm the booking back to the caller. Ideally it writes straight into the booking system you already use, so there is no second list to reconcile. It should also handle changes and cancellations, which free up tables you can resell.
Takeaway and delivery orders
If you take phone orders, the service needs your current menu, including prices, sizes, add-ons and anything that has sold out. It should read the order back, confirm a pickup or delivery time you can actually meet, and send the ticket where your kitchen will see it.
The questions you hear every day
Opening hours, parking, whether you take walk-ins, whether dogs are allowed on the terrace, whether there is a vegetarian menu, how to get there. These calls are short, repetitive and easy to answer well, and they add up to a lot of interruptions over a week.
Messages that need a human
Complaints, supplier calls, job applicants, press, large events and anything the service isn't sure about should become a clear message: who called, their number, what they want, and how urgent it is. Messaging is also worth considering here, since many guests would rather confirm a booking by text or WhatsApp than call back.
A Friday service, with the phone covered
Picture a small neighbourhood bistro with one host and a busy kitchen.
- 9:40 am. Nobody is in yet. A caller asks about booking for eight people next Thursday. The service checks the book, finds a slot at 7:30 pm and confirms it. The booking is waiting when the manager arrives.
- 11:50 am. Prep is in full swing. Someone asks whether the restaurant is open for lunch on the upcoming public holiday. The answer is in the information the owner provided, so the caller gets it immediately.
- 3:15 pm. Between services, a regular calls to move tonight's table from 8 pm to 8:30 pm. The change is made and confirmed.
- 6:55 pm. The first rush. Three calls arrive within a few minutes: a takeaway order, a request for a table for two at 7:30 pm, and a question about gluten-free options. The order goes to the kitchen screen, the table is booked, and the dietary question is answered from the approved menu notes, with an offer to pass the caller to staff if they have a serious allergy.
- 8:20 pm. A caller is unhappy about last week's meal. The service doesn't argue or promise refunds. It takes the details and flags the message for the manager.
- 11:30 pm. After close, someone asks about a private dinner for thirty in December. The enquiry is captured with contact details for the owner to handle personally the next morning.
Nothing dramatic happened. That's the point. Every call got an answer and no one on the floor was pulled away from a guest.
Choosing an answering service for restaurants: a checklist
Before you sign up for anything, work through these steps.
- List your call types. Spend a week noting what people actually call about. It shows you what the service must handle well.
- Check it connects to your booking system. If it can't see real availability, you'll get double bookings or a separate list someone must copy across.
- Test menu and order handling. Place a complicated order yourself, with swaps and extras, and see whether it comes out right in the kitchen.
- Decide your handover rules. Which calls transfer to a person during service, which become messages, and who receives them.
- Check the languages. If your guests call in more than one language, confirm the service handles them naturally.
- Listen to how it sounds. Call it as a guest would. It should sound like your restaurant: warm, quick and clear.
- Understand the costs. Compare how each option charges, whether per call, per minute or a flat plan, and what happens in your busiest weeks. Ringhum publishes its plans on its pricing page.
- Know how to update it. Menus change, dishes sell out and hours shift for holidays. Updating should take minutes, not a support ticket.
What to avoid
- Out-of-date information. A service that tells callers you serve brunch after you've dropped it creates angry guests. Make updating part of your routine.
- Overpromising. Don't let any service confirm things only the kitchen or manager can promise, such as allergen guarantees, custom dishes or refunds.
- Dead ends. Callers should always have a way to reach a person or leave a message that someone will actually read.
- Messages that sit unread. Decide who checks them and when. A captured enquiry is only valuable if someone follows it up.
- Ignoring local rules. Recording calls, storing customer details and handling allergen information are regulated differently by country. Check what applies to you.
When a person should take the call
An automated or remote service is good at the routine. Some calls deserve a human, and it's worth being honest about which:
- Serious allergies. Give approved menu information, but anyone with a severe allergy should speak with someone who knows the kitchen that day.
- Complaints. An upset guest wants to be heard by someone who can put things right.
- Large events and private hire. These involve negotiation, deposits and menu planning. Capture the enquiry, then let the owner or manager call back.
- Anything urgent or unusual. A lost item, a delivery that never arrived, a supplier problem. Route these straight to staff.
The best setups treat the service as a first line that handles the everyday and passes on the rest cleanly.
Frequently asked questions
Will guests know they aren't talking to my staff?
Some will, some won't. What matters more is whether the call goes well. Guests mostly want a quick, accurate answer and a confirmed booking. If the service is honest about what it can do, speaks clearly and passes tricky calls to a person, most callers are simply glad someone picked up rather than being left to ring out or sent to voicemail.
Can an answering service take takeaway orders correctly?
Yes, if it has an accurate, current menu with prices, options and sold-out items. Test it with complex orders before going live, and make sure orders arrive where your kitchen already looks, such as a printer or screen. Keep the menu updated whenever dishes change, because most wrong orders come from old information rather than misheard calls.
What happens when we're fully booked?
The service should tell the caller honestly, offer the nearest available times or another date, and, if you use one, add them to a waiting list. It can also mention walk-in policy if you keep tables free. That is far better than a caller hearing nothing and assuming you never answer the phone.
Is it only useful during service?
No. Many calls come in before opening, between lunch and dinner, and after closing. Covering those hours catches bookings and enquiries you would otherwise find as a pile of voicemails the next morning, often too late to be useful. Round-the-clock answering means the phone is covered whenever guests happen to plan their meal.
The practical next step
Start this week by keeping a simple tally of every call: what it was about, when it came in, and whether someone answered. Within a few days you'll see which calls interrupt service, which get missed, and which need a human. That list is your brief for any answering service you consider.
Ringhum is an AI phone receptionist that answers your restaurant's calls around the clock, books tables, takes orders, answers routine questions and sends you clear messages for anything that needs a person, including on WhatsApp. It works best for the everyday calls described here, not for complaints or complex events. You can see how it works for restaurants on our restaurants page, and setup questions are covered in the help center.
