Not an argument against hiring.
A restaurant that's short-staffed needs people — on the line, on the floor, at the register. Nothing here disputes that. What this page weighs is narrower: a real hire, compared honestly against a phone-answering system, for the one specific moment even a fully staffed shift still has — when everyone on duty is already doing something else and the phone rings anyway.
Capacity, not headcount.
It's worth being precise, because it's easy to blur this into "do I still need to hire." A hired person is a full, general-purpose addition to a shift — they answer the phone when they're free to, and they also run food, bus a table, cover the register, and do the dozen other things a restaurant job actually is. A phone-answering system does exactly one thing: it picks up a call. It doesn't cover a shift, train into a role, or do anything else a person on the floor does.
So the honest comparison isn't "hire less." It's this: even a restaurant that hires exactly the right number of people still has moments where every one of them is already occupied — mid-rush, short a person because someone called out, or just genuinely slammed — and the phone doesn't wait for a good moment to ring. That gap is what this page is about: the phone specifically, answered even when every hired hand is already full. Not a smaller staff.
Four columns, stated plainly.
Six things a person does that this doesn't
- The judgment call a script hedges on. An allergy question, an unusual substitution, a dispute over a past order — these need a situational answer, not a safe default. Dohos's own design answers an allergy question with a disclaimer and an unguaranteed transfer offer because that call needs a person.
- De-escalation. A script can apologize; it can't read a room. Guest experience is where restaurant managers say they put the most effort.
- Regulars, recognized. A familiar voice who already knows "the usual" is relationship capital a phone system has no way to have earned.
- Real negotiation. A catering order reconciles a headcount, a date, a price, and a kitchen-capacity check in one conversation — a negotiation, not an order.
- General-purpose labor. The person who answers the phone also busses a table or covers the counter. Hiring adds capacity across a whole shift.
- Experience worth keeping. The most detailed turnover-cost breakdown available found the new hire's learning-curve productivity loss the largest single cost of a departure — the mechanism is real, sourced below.
Not free, not fast
The restaurant labor market is genuinely tight: accommodation and food service posted a 4.3% quits rate in March 2026 — the highest of any industry the government tracks, nearly double the 2.2% private-sector average (BLS JOLTS).
Finding someone takes real time — 16 days to fill an hourly opening on average, 46 for a manager — and once hired, that person isn't at full value from day one: 31.8 further days to net-positive for an hourly hire, 72.2 for a manager (National Restaurant Association, April 2026). Because turnover runs high, a meaningful share of any floor, at any time, is still early in that ramp.
An ongoing structure, not a line item
Labor is already the largest or second-largest cost most restaurants carry — the staffing guide has the actual share of sales it eats, split by service style. On top of that share, real wages for real people: staff shortage carries the front- and back-of-house figures; a restaurant or food-service manager earned a median $65,310 a year (BLS OES, May 2024).
Then the ramp: 16 to 46 days to fill, a further 31.8 to 72.2 before net-positive — real time paying for a person not yet contributing at full value. A genuine cost of hiring well, not a reason to skip it.
Said early, meant fully
A restaurant with real allergy-sensitive volume, frequent complaint or refund calls, meaningful catering or large-order business, regulars worth personally recognizing — or that is short-staffed everywhere, not only on the phone — needs a person, not a phone tool.
That case is real enough to get its own full section further down this page, not one line here. A reader who finishes this page should come away thinking "Dohos and a good hire solve different problems" — never "I guess I don't need to hire."
Seven weeks. Four months.
Neither helps at 7:40 tonight.
Two timelines, not one. An hourly opening takes 16 days to fill on average, then 31.8 more before the new hire is net-positive — roughly seven weeks, start to actually paying off. A manager opening runs longer on both counts: 46 days to fill, then 72.2 more — close to four months, start to finish.
The reason any of this matters isn't abstract. Staff shortage carries the real operational toll a staffing gap takes — cut hours, postponed expansion, days closed that would ordinarily be open. A restaurant in that position needs people, generally, not a narrower fix aimed at one channel. A phone-answering system doesn't touch cut hours, a changed menu, or a closed dining room — those are staffing problems this page has no honest claim on solving.
7:40 on a Friday.
Every hand already full.
Every server is on the floor, the one line cook is deep in tickets, and the manager is running food because someone called out — a real, ordinary kind of short-handed, not a crisis. The phone rings. Nobody is free in the next several seconds.
…hello? — yeah hi, can I order for pick—
A hire adds capacity across an entire shift — something a phone tool never does. The two clocks above are honest, not damning: they just don't run at ring speed.
That's one gyro plate with extra tzatziki and a large pizza, half pepperoni, half mushroom — pickup at 8:10, under Rosa. Did I get everything?
The screen it lands on is built for the people already on shift — not instead of them.
Say it plainly — it's the
actual point of this page.
Needs a person who can weigh a specific situation — not a system that discloses and defers.
Needs someone who can de-escalate, not a flow that apologizes the same way every time.
Needs someone who can negotiate a headcount, a date, and a substitution in one conversation.
Repeat local trade needs someone who recognizes a voice and already knows the order.
On the floor, at the register, in the kitchen — not only on the phone — needs a person, full stop.
Any restaurant that recognizes itself in those five cells should hire. This page was never an argument against that. It's a description of one specific gap even a well-staffed floor still has.
So are you saying we shouldn't hire?
No — the opposite. If a restaurant is short-staffed, the honest answer is to hire; nothing on this page argues otherwise, and the section above says so directly. This page describes one specific gap — the phone, in the moment everyone hired is already busy — not a substitute for the people a restaurant actually needs.
Doesn't answering the phone automatically mean needing fewer people?
No. The number of people a restaurant needs to run a floor, a kitchen, and a register doesn't change based on who answers the phone. What changes is whether a ringing phone has to wait for one of those already-busy people to get free.
What if we can't find anyone to hire right now?
That's a real, separate problem — the labor market is genuinely tight, and this page doesn't have a fix for it. What it can do is make sure the phone still gets answered while that search is ongoing, which is a narrower promise than solving the hiring gap itself.
See it answer while your floor stays full.
Request access to see a phone-answering system running alongside your actual staff — not instead of them.