Your Phone Rings Hardest at the Hour Nobody Can Answer It
Most advice about missed calls assumes nobody was there.
In a restaurant the opposite is true. At seven on a Friday every single person you employ is present, moving, and already holding something. The phone isn't ringing into an empty room — it's ringing into the busiest room it will be in all week, and that's precisely why it doesn't get answered.
That's a different problem from the one the answering-service industry describes, and it needs a different fix.
The shape of it
Think about when your phone actually rings.
Someone wants a table for tonight. Someone's checking whether you can do a nut allergy. Someone's twenty minutes late for a booking and calling to say so. Someone wants to know if the kitchen is still open. A supplier. A large party trying to book for next Saturday.
Almost all of that lands between six and eight. So does everything else in your night.
The host is seating. The manager is fixing a table that was double-booked. Whoever's nearest the phone is carrying three plates. The call rings out, or it gets picked up on the seventh ring by someone who can't hear, can't check the book, and can't talk for more than nine seconds.
The industry number for how often a small business answers live is 37.8% — that's from a 2024 study by 411 Locals across 85 businesses and 58 industries, and it's the figure I trust most, because it counted rather than estimated. You'll see much bigger and much scarier numbers than that from companies selling phone systems. I've written before about why I don't use them and I'm not going to start now.
You don't need my number anyway. You have yours. Look at your own missed-call log for last Friday between six and nine.
What each of those calls was worth
This is the part restaurants underestimate, because a missed call doesn't feel like a lost sale — it feels like nothing at all.
- A two-top that didn't book: your average cover, twice.
- A twelve-person party that called three places and booked the second one: a whole section of a Saturday.
- The allergy question nobody answered: that person didn't risk it. You'll never know they existed.
- The regular who couldn't get through to say they were running late: their table sat empty for twenty minutes and then they arrived annoyed.
The large-party call is the one worth stopping on. Those come in during service, they're worth ten or twenty times a normal booking, and they're the most likely to be abandoned, because a group organiser has a list of restaurants and is working down it. They aren't waiting for you to call back tomorrow. They're already on the phone to the next place.
What an AI receptionist does about it
Plainly, because this is the part people picture wrong.
An AI answers your phone on the first or second ring, in your restaurant's name, while your host keeps seating. It's not a menu tree and you don't press one for anything — the caller talks normally and it answers.
For a restaurant that means it can:
- Take the booking, straight into your reservation system, including the party size and the date
- Answer what you told it — your hours, whether the kitchen's still on, whether you do gluten-free, where to park, whether you take walk-ins
- Take the running-late message and text it to the host stand, so the table gets held instead of turned
- Pass the big one through. A twelve-person enquiry or a private-hire question can be routed to a person, or captured in full detail and sent to the manager's phone with the number to call back
And the constraint that matters more than any feature: it says it's an AI if the caller asks, and it hands off rather than improvising when the question is outside what you gave it. A system that guesses at your allergen information is worse than a phone that rings out. Much worse.
I've written the honest version of whether customers actually mind talking to one, including the cases where they do.
What I would not let it do
Post 8 covers this principle in full — automate the wait, not the relationship — but restaurants have two specific ones.
Allergies. An AI can say the kitchen can usually accommodate that and the manager will confirm on arrival. It should not be the last word on whether your kitchen can guarantee no cross-contamination. That answer comes from a chef, every time.
Complaints. If someone's calling because last night went badly, that call goes to a person, and quickly. Nothing makes a bad night worse than being triaged by software.
The version I'd build for a Philadelphia restaurant
The companies selling this sell a subscription. You sign up, you fill in a form describing your business, and you configure it yourself between shifts — which, if you run a restaurant, means it stays half-configured for eight months.
That's the actual failure. Not the technology, which works. The setup.
What I do instead is put it in already working: your hours, your menu, your allergen policy, your parking, your BYOB situation, your reservation system, and the handful of questions you personally get asked forty times a week and are sick of answering. Then it goes on your site and your Google listing, and I stay on the hook when the menu changes in October.
The uncomfortable part
An AI answering your phone is worse than a good host answering your phone. That's true and I'm not going to pretend otherwise.
If you have someone on the stand from five until close who knows your regulars by name, you already have the better thing, and you should keep it. This isn't for you.
It's for the two hours a night when that person is physically unable to pick up, and for Monday when you're closed and someone's trying to book Saturday. The comparison isn't AI against your host. It's AI against the seventh ring and nobody there. That comparison is the only one that decides whether this is worth money to you.
A ten-minute check
Tonight, during service:
- Have someone call your own number at 7:15. Let it ring. Count the rings. Note who answers and what they can hear.
- Pull last week's missed calls on your mobile or your phone system, and count only Friday and Saturday between six and nine.
- Multiply that count by your average cover. Halve it, because some of them called back or walked in anyway.
That last number is what this decision is actually about, and it's yours rather than a vendor's.
Want to know what your Friday night is costing? Send me your number and your average cover. I'll call it during service like a customer would, tell you what happened, and give you the arithmetic — free, and if it turns out your host is handling it fine, I'll tell you that instead. Start a conversation →