Missed calls are the most expensive line item that never shows up on a P&L. There's no invoice, no alert, no red number at the end of the month. The revenue just never arrives — and because it never arrives, most operators never count it.
I run Subway stores in San Diego with my brother Rohit, and for years we assumed the number was small. It wasn't. Once we actually measured it, the weekly figure was large enough to change how we thought about the phone entirely. Here's the math we use — plug in your own numbers as you read.
Step 1: What is a single call actually worth?
Not every call is equal, so don't average them into one blurry number. At a quick-service or fast-casual store, inbound calls fall into two buckets that are worth wildly different amounts:
- A regular order — a pickup or a couple of sandwiches. Call it $15–25. Use $18 if you don't know.
- A catering inquiry — a tray order, an office lunch, a party platter. In our stores these average north of $500, and they repeat.
The catering call is the one that hurts. A missed $18 sandwich stings for a minute. A missed catering inquiry is a $500 order and a customer who now has a relationship with whoever did pick up. You didn't lose one sale — you lost the account.
Step 2: How many are you actually missing?
Most operators badly underestimate this because the misses are invisible by definition — you can't see a call nobody answered. Pull your phone records for one week: total inbound calls versus calls answered. The gap is your miss rate.
When we did this, roughly 30% of our inbound calls were going unanswered — almost all of them clustered during the lunch and dinner rush, which is exactly when catering customers call to plan the next day. That's not a slacking-staff problem. It's structural: the phone rings hardest at the precise moment your team physically cannot pick it up.
Step 3: The weekly-leak formula
Here's the whole thing on one line. Run it per store, then multiply by your store count.
Weekly leak = (calls/day × miss rate × days open) × recovery factor × blended call value
Recovery factor = the share of missed calls that were real, winnable business (not spam, wrong numbers, or people who call back). We use a conservative 60%.
A worked example for one store, deliberately conservative:
- 50 calls/day × 30% miss rate × 6 days = 90 missed calls/week
- × 60% recovery factor = 54 winnable calls lost
- Say 1 in 10 was catering: ~5 catering (× $500) + ~49 orders (× $18)
- = $2,500 + $882 = ~$3,380 per store, per week
Across five stores, that conservative number is over $17,000 a week — roughly $880,000 a year — walking out the door with no record that it ever knocked.
Change the inputs to match your reality. Even if you think our miss rate is high, halve it: you're still looking at real six-figure annual leakage per store cluster. The point isn't the exact dollar — it's that the number is never as small as it feels.
Why the usual fixes don't recover it
We tried all of them before we built anything. None gave the money back:
- Voicemail — a hungry customer at noon does not leave a voicemail. They hang up and call the next place. Voicemail is where revenue goes to be ignored.
- Call routing / phone trees — menus add friction at the exact moment the caller has the least patience. Press-1-for-catering doesn't help if nobody's on the other end of option 1.
- Hiring for phone coverage — expensive, and it fails when you need it most. Everyone is slammed during the rush; nobody's free to answer.
We wrote up that whole journey — from "just hire more people" to actually solving it — in why 30% of our calls went unanswered and what we did about it. The short version: the only fix that recovers the leak is answering every call, instantly, without adding headcount.
What full capture is actually worth
Flip the formula around. The weekly leak isn't a sunk cost — it's the upside sitting on the table. Recovering even most of it is the single highest-ROI operational change available to a multi-unit operator, because it requires no new locations, no menu changes, and no marketing spend. It's revenue you're already generating demand for and simply failing to catch.
That's why we built Maya — an AI voice agent that picks up on the first ring at every store, takes the order, captures the catering lead, and warm-transfers to a human when it should. Our own capture went from ~70% to 100%. When we priced it for other operators, we set it against exactly this math: if Maya costs a fraction of what one store leaks in a week, the decision makes itself.
Run the formula on your own numbers first. If the leak surprises you, that's the whole point — it's been there the entire time.