Calling back a customer who hung up: why it rarely works

Calling back a customer who hung up rarely works, because most people no longer answer numbers they don't recognize. In Hiya's State of the Call 2026 survey of more than 12,000 consumers in six countries, including the US, 86% didn't choose “answer immediately” as their usual reaction to an unknown number [1]. And by the time your callback gets through, dinner may already be ordered somewhere else.

Callbacks are still worth making, as long as you make them fast and don't count on them. Here's what the data shows, what callers do between the missed call and your callback, how to call back, and the only fix that doesn't depend on the customer: answering the first time.

Why don't customers pick up when you call back?

Because an unknown number looks like spam until proven otherwise. People have learned to screen their calls.

• Most people screen. Hiya, a voice security and caller ID company, had Censuswide survey more than 12,000 consumers in the US, Canada, the UK, France, Germany and Spain. Asked what they usually do when a number they don't recognize calls, 86% didn't choose “answer immediately” [1].
• The top reflex is to let it ring. Waiting to see whether the caller leaves a voicemail was the most common answer [1].

One caution on that 86%. Hiya's website turns it into “86% of unknown calls go unanswered” [2], but the survey didn't count calls. It measured what people say they usually do. It's still a strong sign that a callback from an unsaved number has a good chance of being ignored.

And screening keeps growing. In France, where the telecom regulator tracks it, the share of phone users who say they rarely or never answer a number they don't recognize rose from 57% in 2021 to 65% in 2023 [3].

One nuance: the customer dialed your number, so they may recognize it. But unless they saved it, your callback shows up as just another number. Call from a personal cell or a blocked number, and you're a complete stranger.

What do callers do when a restaurant doesn't answer?

They don't wait for your callback. They move on.

• They hang up fast. Revmo, a voice AI vendor that analyzed 12,091 recorded restaurant calls, puts the “abandonment threshold” at 5.5 rings (2026) [4].
• They go elsewhere. In a 2025 Harris Poll survey of 2,065 US adults for Hostie, 69% said they're likely to give up on going to a restaurant if no one answers the phone [5]. That's stated intention, not measured behavior.
• It happens often. In the same survey, 1 in 5 Americans (20%) said their calls to restaurants are always or often ignored [5].

A food order is more urgent than a customer service question: people are hungry now. If they can't reach you, they call the place down the street or open a delivery app. By the time your callback comes, their dinner may be on its way from someone else.

How many orders does calling back recover?

Nobody has measured it, and every restaurant is different. But a quick example shows why the number is small. The inputs are assumptions, to replace with your own:

1. 10 missed calls during a Friday dinner rush.
2. 4 customers pick up when you call back an hour later. That's an assumption in line with the screening data above.
3. 2 still want to order. The other two have already eaten or ordered somewhere else.

Result: 2 orders recovered out of 10 missed calls, for about ten calls made after service. The other 8 are gone. To put a dollar figure on them, run your own numbers in what a missed call really costs a restaurant.

To find your real rate, keep a simple log for one week. For each callback, write down the time, whether the customer picked up and whether they ordered. Seven days of notes will tell you what callbacks are actually worth to you.

How should you call back a missed caller?

If you do call back, give yourself the best odds:

1. Call back fast. Within minutes, not the next day. The longer you wait, the more time the customer has had to find another option.
2. Use the restaurant's number. The one they dialed, the one on your Google Business Profile. Never a personal cell, never a blocked number.
3. Leave a short voicemail. Waiting to see whether the caller leaves a message is the most common reaction to an unknown number [1], so that's where your callback lands. For example: “Hi, this is [restaurant name], you tried to reach us around 7 pm. Call us back at [number] and we'll take your order.”
4. Send a text if your line allows it. A text from the restaurant can be read without picking up.

And decide who calls back. During the rush, nobody has time; after service, it's often too late for dinner.

How do you stop needing callbacks?

Answer the first time. It's the only fix that doesn't depend on the customer picking up. Choose based on how many calls you miss and when:

• Someone on the phone during the rush. The most reliable fix for busy nights, but it costs staff hours: see how many staff hours your phone eats during the rush.
• Call forwarding. After a few rings, the call rolls to a second phone. Useful only if someone there is free to answer.
• A clear voicemail greeting. Your hours and your online ordering link. Helpful, but voicemail doesn't take orders.
• An AI voice agent. It answers when your team can't, says it's an AI in its first sentence, takes the order from your menu, reads it back and gives the pickup time you set. The ticket prints in your kitchen, with a text and email alert. When you're closed, it says so and gives your hours. That's what Soleir does: try the live demo to hear it pick up.

A customer who reaches someone, or an agent that takes their order, doesn't need a callback. Callbacks go back to being what they should be: the exception.