How to count your restaurant's missed calls in 15 minutes

To count your restaurant's missed calls, 15 minutes is enough to get started: open the call log on your business phone service or the restaurant's cell phone, tape a tally sheet next to the phone, then keep it for one week, two minutes every night at closing. After seven days you have your real number, and working out what it costs takes five more minutes.

We found no reliable, industry-wide missed-call rate for restaurants, so the only number worth having is yours. Here's where to find it, what each call log leaves out, how to count without inflating the total, and what to do with the result.

Where do you find your restaurant's call log?

If your line runs on a business VoIP service, start with its online account: that's where the call log lives, with filters and dates. A few examples:

Three things to know before you count:

• Billing records miss the calls you care about. Comcast Business's guide to VoiceEdge call detail records (2016) says they don't include local calls, inbound or outbound [3]. A customer calling from down the street is a local call. Use the call log, not the bill.
• Some systems will email the log to you. In RingCentral, you can schedule the call log by email, daily, weekly or monthly, under Reports, then Call Log, then Delivery Settings [1].
• Provider not listed here? Search its help center for “call history” or “call log,” and check how far back it goes before you start counting.

How do you check missed calls on the restaurant's cell phone?

If the restaurant's number rings on a cell phone, its call list is your second source. It takes a few taps.

On an iPhone

Open the Phone app and tap Calls (Unified layout, iOS 26 and later) or Recents (Classic layout). Tap Filter in the upper-right corner, then Missed: audio calls that weren't answered [4]. The Unknown Callers filter groups missed calls and voicemails from unknown numbers [4], which covers new customers and spam alike.

On an Android phone

In the Phone by Google app, the Home tab shows an icon next to each call: missed (incoming), answered (incoming) or made (outgoing) [5].

Neither Apple nor Google says on these pages how many calls the list keeps. So take a screenshot at closing every night of your counting week, and the question stops mattering.

How do you count missed calls over one week?

The call log tells you how many calls rang out. The tally sheet tells you when, and it never gets erased. Keep both for seven days you're open, not one evening.

Why a full week? Because calls don't arrive evenly. In Maple's data (1.2 million calls to US restaurants and local businesses using its voice AI service, December 2023 to November 2025), Friday brings 18% of the week's calls and Monday 11% [6]. And 68% of calls come in during the lunch rush (11 am to 2 pm) and the dinner rush (5 pm to 9 pm) [6]. Count one Friday and multiply by 30, and you'll overestimate; count a Monday, and you'll underestimate.

The first 15 minutes

1. 5 minutes: the log. Open your phone service's call log or the cell phone's list (see above). Note how far back it goes.
2. 5 minutes: the sheet. One sheet per day, taped next to the phone, with one row per time slot. For example: opening to 11:30 am, 11:30 am to 2 pm, 2 to 5 pm, 5 to 9 pm, 9 pm to closing. Adjust to your hours.
3. 5 minutes: the first pass. Copy the missed calls the log already holds, with their times. That's your starting point.

For the next seven days

• One tick mark for every call that rings out, in the right time slot. Whoever walks past the phone makes the mark, even mid-rush.
• If you want your miss rate, add a dot for every call someone answers. You'll see what share of calls you miss, slot by slot.
• Every night at closing, two minutes: compare the sheet with the log, fill in what's missing, and take a screenshot of the log.

Missed call, callback or repeat caller: what should you count?

A raw call log counts rings, not customers. Before you total the week, apply these rules:

• One number, one customer. Someone who calls three times in ten minutes is one missed customer, not three. Group by number within the same meal period.
• A customer who calls back and gets through isn't lost. Cross out their mark, but log them separately as a “callback that got through.” That's your own measure of how many customers try again.
• Your own callbacks go in a separate column. For each one, note whether the customer picked up and whether they ordered. Callbacks recover less than you'd think: see why calling back a customer who hung up rarely works.
• Short rings count. A customer who hangs up after a few rings is still a missed call. Revmo, a voice AI vendor that analyzed 12,091 recorded restaurant calls, puts the abandonment threshold at 5.5 rings [7].
• Blocked numbers count one by one, since you can't group them. That may inflate the total a little, so keep them in their own column.
• Spam comes out. On Android, the Lookup button searches an unknown number in your default search engine [5], which quickly flags a call center.
• After-hours calls get their own column. They don't need the same fix as rush-hour calls.

At the end of the week you have three numbers: missed customers (unique numbers), how many of them came during the rush, and callbacks that got through. Divide the first by the days you were open: that's your average number of missed calls per day.

What do your missed calls cost you?

With your daily average, the math is ready. You need two more inputs and one number from your register: the share of callers who wanted to order, the share who don't call back, and your average ticket. The formula and a calculator are in what a missed call really costs a restaurant: swap its example inputs for yours.

Your week already gives you one of them. For example, to replace with your own: of 20 missed customers, 4 called back and got through. The share who don't call back is 16 out of 20, or 80%. That beats any national average, because it's yours.

Then look at the time slots. If nearly every miss falls between 7 and 9 pm on Fridays and Saturdays, one more person on the phone those nights may be enough: compare their hourly cost with the loss, and with the staff hours your phone already eats during the rush. If misses are spread across the day, call forwarding or an AI voice agent is a better fit. An agent like Soleir answers when your team can't, takes the order from your menu, reads it back, and the ticket prints in your kitchen.

Whatever you choose, run the same week of counting a month later, with the same sheet. If the number of missed customers hasn't dropped, the fix isn't working.