Restaurant phone systems and the dinner rush

Every restaurant has the same twenty minutes. Six-forty on a Friday: the first tables are seating, the pass is filling up, and the phone starts. Someone picks it up, holds it against a shoulder, and tries to find Thursday in the book while a couple waits to be seated.

Half the time nobody gets to it at all.

The problem is when, not how many

Restaurants do not take a huge number of calls. They take them in a narrow window, and the window is the worst possible one.

Pull a week of call data and the shape is almost always the same: a modest spike late morning, then a sharp peak from about an hour before service through the first hour of it, then a long quiet tail. The peak is where the missed calls live.

This matters because it changes what a solution has to do. You do not need more capacity in general. You need calls answered during a ninety-minute window when nobody has a free hand — and a new phone system, however good, does not create hands.

What the calls actually are

Broadly four kinds, and they need very different handling:

1. Reservations. Booking, changing, cancelling. The highest-value calls, and the ones most likely to be lost during the peak.
2. Questions. Opening hours, parking, whether you take dogs, whether the terrace is covered, is there a set menu tonight. Repetitive and easily answered from fixed information.
3. Large parties and private hire. Low volume, high value, and worth a human every time.
4. Allergen and dietary questions. Rare, and a safety matter — never to be answered by anything working from stale information.

Groups 1 and 2 are most of the volume. Group 2 in particular is pure interruption: the answer never changes, and it never needs judgement.

What a phone system fixes, and what it doesn't

A modern cloud phone system will give you call routing, an auto-attendant, hold music, voicemail-to-email, and call reporting. That reporting is genuinely useful — most restaurants have never actually looked at when their missed calls happen, and the data usually changes the conversation.

What it does not do is answer. An auto-attendant that offers four options to someone trying to book a table for Friday mostly teaches them to hang up and use the booking site, which — to be fair — is not the worst outcome.

That points at the honest first move for a lot of restaurants:

Covering the calls that remain

Once reservations are deflected online, what is left is questions, large parties, and the callers who will only ever use a phone. Three options:

Take a message and call back. Fine for private hire, useless for a table tonight.

A human answering service. Reliable, priced per minute or per call with a monthly minimum, and worth considering if your call volume genuinely justifies it. Most independents find the minimum hard to justify for a ninety-minute daily peak.

An AI receptionist. Answers every call during the peak, handles the repetitive questions from your own information, and passes anything needing a person — private hire, allergens, complaints — straight through. Because it is billed per minute of answered time, a slow Tuesday costs almost nothing, which suits the spiky pattern well.

The same caution applies as anywhere else: it should only claim to have made a reservation if it is writing to your actual booking system. A "reservation" that sits in an email for someone to key in later is a message, and at volume it is how double-bookings happen.

Setting it up so it doesn't embarrass you

1. 1

   Lead with the booking link

   Whatever answers, the first thing a caller hears should be the fastest route to what they want. For most restaurants at most hours, that is booking online.

2. 2

   Write down the repetitive answers properly

   Hours, parking, dogs, terrace, corkage, set menu nights, accessibility, whether you split bills. These are the interruptions worth eliminating, and vague answers sound like evasion.

3. 3

   Route allergens and private hire to a human, always

   Allergen questions are a safety matter and menus change. Private hire is high-value and needs a conversation. Neither should be automated, regardless of what a demo shows.

4. 4

   Check it during service, not at 3pm

   Test it in the peak, when the dining room is loud and the system is busy. That is the only test that reflects reality.

Where to start

Look at your missed calls by hour first. It costs nothing and it usually reframes the problem — most owners discover the losses are concentrated in a window they could describe from memory but had never quantified.

If those calls are mostly reservations, fix the deflection before you buy anything. If they are mostly questions, something that answers consistently during service will pay for itself quickly.

Dial Milo handles the second case: it answers during the rush from information you provide, captures reservation requests with the details you need, and hands private hire, allergen questions, and complaints straight to a person. The broader comparison of cover options is in after-hours answering services.