← BlogInsights & Use Cases

Unanswered Calls Cost a QSR $73,000 a Year. The Winners Answer Every One

Unanswered Calls Cost a QSR $73,000 a Year. The Winners Answer Every One

On August 20 a report landed that finally puts a number on something restaurant operators have been guessing at for years. Analysts listened to 12,091 real restaurant call recordings across quick service, fast casual, full service and pizza, and scored what happened on each one. Quick-service locations answered 59.9% of their calls. The other 40.1% rang out. The study prices that at roughly $73,000 a year in lost revenue per location — $3.65 million across a 50-unit chain.

Full-service restaurants did far better on pickup rate, answering 91% of calls, but made callers wait an average of 73 seconds on hold. And the spread between brands inside the same segment was enormous: one steakhouse chain answered 99.2% of its calls, while another full-service brand managed 27.5%. Same segment, same phone, wildly different outcomes.

The phone fails at the exact hour it matters

The pattern in the data is a clock, not a staffing failure. Fast casual answered 75.3% of calls overall, but greeting consistency dropped 38 points between lunch and dinner and hold times climbed 31%. Performance falls apart precisely when the dining room fills and every pair of hands is already committed. Nobody chooses to ignore the handset at 6:40pm; the handset simply loses to the guest standing at the counter.

That is why answer rate has never been managed like a real metric. Restaurants track cover counts, ticket times and table turns to the minute, but as one operator argued in Nation’s Restaurant News earlier this year, the phone is still a black box — demand arrives, some of it converts, and nobody measures the difference. You cannot fix what never shows up on a report.

The AI numbers cut both ways, and that is the useful part

The study also benchmarked 224 AI-answered calls against 9,187 human-answered ones, and the honest read is that the technology did not decide the outcome. Weak AI deployments scored 3.30 on caller sentiment, below the 3.90 humans averaged. Well-built ones scored above 4.2, picked up in 18 to 22 seconds and greeted callers correctly on 100% of calls — better than any human-staffed segment in the sample.

Worth noting the report comes from a company that sells restaurant voice AI, so treat its enthusiasm accordingly. But the split it documents is the part that survives the bias: implementation quality, not the category, separates the 4.2 from the 3.30. A system that knows your menu, your allergen list, your hours and your booking rules, and that hands off cleanly when it should, is a different product from a bot reading a script. That distinction is the whole game in what an agent actually does for a busy restaurant.

What to check before the next dinner rush

Start by measuring. Pull the last 30 days of call logs from your phone provider and split answer rate into two buckets: 11am–2pm and 5pm–8pm. Most operators find a gap they did not know existed. Multiply the misses in that second bucket by your average check. That number is your annual leak, and for a single quick-service location the study says it is around $73,000.

Then look at what those calls actually were. The routine ones — hours, parking, “are you open Sunday,” the fifth allergen question today — should never reach a person mid-service. The valuable ones — a table for nine, a catering quote, a private dining enquiry — are worth several covers each and are the ones most likely to hit voicemail at 6:40pm. Getting every call and message answered on every channel without adding a host to the schedule is now a solved problem; the operators still deciding are the ones paying the $73,000.

Working in food & beverage? See how TalkRev works for Food & Beverage.

The TalkRev blog

One short email per new post

No ads. Unsubscribe anytime.

Start saving hours every
week with TalkRev

Reduce repetitive questions, capture more bookings, and deliver a faster customer experience — without adding headcount.

Get started
TalkRev dashboard