Three calls you never hear about
7:42 PM, Friday. Every table is full and the host is seating a six-top. The phone rings out. The caller wanted a table for four tomorrow and books the place down the street instead.
3:15 PM, Tuesday. Someone on your website fills out a contact form asking about Saturday. Nobody sees it until after service. By then they've booked somewhere that confirmed on the spot.
11:30 PM, Saturday. A couple decides on brunch plans after a show. You're closed, the call goes to voicemail, and they don't leave a message.
None of these show up in your reservation book, your POS or your end-of-night report. That's exactly why most owners underestimate them. The good news: you can measure it.
How to count your missed reservations
You don't need special software for this. Your phone provider already keeps the data.
1. Pull your call log for a busy weekend
Log in to your phone provider's portal (Bell, Rogers, Telus, your VoIP company) and export the call history for one Friday and one Saturday. Most portals show every incoming call with a time and whether it was answered.
2. Count the unanswered calls
Split them into two groups: calls missed during service, and calls that came in while you were closed. Ignore obvious spam and repeat dials from the same number within a few minutes.
3. Estimate how many were bookings
Look at the calls you did answer that weekend. If roughly half were reservation requests, assume about half of the missed ones were too. Be conservative; the point is a realistic floor, not a scary number.
4. Put a dollar figure on it
Multiply the missed bookings by your average party size and your average spend per guest. Then multiply by the number of weekends in a year.
A worked example
Here's how the math looks for a made-up 70-seat restaurant. Swap in your own numbers.
- Missed calls on Friday and Saturday combined: 16
- Share that were likely bookings: half, so 8
- Average party size: 3
- Average spend per guest: $40
That's 8 × 3 × $40 = $960 in one weekend, or roughly $50,000 a year if the pattern holds. Even if only a third of those callers would have actually come in, it's still far more than any reservation system costs.
Don't forget the bookings that never became a call
The call log only catches people who dialled. It misses the guest who filled out your website contact form and never heard back, the one who messaged you on Instagram during service, and the one who looked for an online booking button, didn't find one and moved on. Those are harder to count, but worth a quick check: open your contact form inbox and your social messages from last weekend and see how many reservation requests are sitting there without a reply.
Once you have a number, write it down and check it again in a month. The goal isn't a perfect figure. It's knowing whether the leak is a few tables a month or a few tables a night, because that tells you how much it's worth spending to fix it.
Three takeaways
- Your book only shows the bookings that got through. Missed calls are invisible until you go looking for them.
- The busiest hours are the leakiest. The phone rings most when your team has the least time to answer it.
- After-hours calls count too. Guests make plans in the evening, long after your host has gone home.
How Reserve A Table closes the gap
Reserve A Table puts every way a guest tries to book into one live book. An AI agent answers the phone on the first ring, real-time booking on your website confirms instantly, and website chat takes bookings around the clock. Every booking, call recording and transcript lands in one dashboard, so you can see exactly what came in and when.
It's flat monthly pricing in Canadian dollars with no per-cover fees, built and supported in London, Ontario. If you're paying per cover today, see how we compare as an OpenTable alternative, or read what to do when the phone rings during the rush.
Want to see it on your own restaurant? Call 519-614-4143 or book a demo.