Adel AtyaAn AI phone agent can take pickup orders during the Friday rush because it answers every call the moment it rings, and it can hold many calls at the same time. Your staff stop being the phone line, and the order arrives as a ticket instead of a napkin note.
It works for simple orders from a menu you give it. It should not handle allergy questions, complaints or complicated custom orders, and a good setup hands those to a person.
How many restaurant calls go unanswered at peak?
One vendor's data says about a third. Maple, a restaurant phone AI company, analysed 1.2 million calls from 1,000+ locations. It reports that restaurants miss 33% of calls at peak service hours, and that Friday carries the largest share of the week's calls at 18%.
Read that number with care. Maple says the 33% comes from merchants' own estimates before they signed up, and that its sample may not match all U.S. restaurants. It is a seller's figure, not an independent study.
Your own number matters more. Pull your phone provider's call log for the last four Fridays and count the calls that rang out between 5pm and 9pm. That count is what you are actually trying to fix.
What does a missed call cost on a Friday night?
Here is an illustration, not a statistic. Say your average pickup order is $35 and four calls ring out during the 6pm to 8pm peak. That is $140 gone in two hours, on one night.
A ringing phone in a busy kitchen is not a staffing failure. Nobody can stir a pan, plate a table and take a 12-item order at once.
The real choice is between a ringing phone and a second person on the phone. That person costs $2,800 to $4,500 a month on the pricing page's comparison and goes home at close.
Why does an AI agent cope with a rush better than a person?
A person can only be on one call. A phone line can be busy, and a caller gets a busy tone or voicemail.
An AI agent is software, so it can run many calls at once. That is a real limit worth checking, though.
On Retell, concurrency limits apply per workspace, and a pay-as-you-go workspace gets 20 concurrent calls by default. Past the limit, an inbound call waits about 40 seconds, then goes to a fallback number if you set one. Without a fallback it ends.
For most single restaurants, 20 calls at the same time is far more than a Friday rush produces. But ask your builder to set the fallback number to your host stand, so the rare overflow call reaches a person.
My agents answer in about 1 second, so the caller is not left listening to a ring.
What does the agent do on an order call?
Following my restaurant page, here is the flow:
- It reads the menu you gave it and takes the order.
- It repeats the order back before confirming.
- It confirms the pickup time against your real prep window.
- It sends the ticket to a tablet, a printer, an email, or straight into your system if that has an API.
Each step can fail, so the setup matters. On Retell, a custom function calls your URL while the caller waits. The timeout defaults to 120 seconds and retries are off. Two minutes of silence on a phone call is far too long.
A sensible build sets a short timeout and says something to the caller. It must not blindly retry an order, because a retry could send the kitchen the same order twice.
My Blue Ridge recovery demo uses a related rule: the agent must call a log_outcome function before it hangs up, so a call can never end without a record. The same idea fits orders. No ticket, no goodbye.
What should it never decide on its own?
Write these rules before launch:
- Allergies. The agent can record what the guest says and flag it on the ticket. It must never tell a guest a dish is safe. The FDA lists nine major food allergens, and its own advice for someone with a sesame allergy is to ask restaurant staff about the ingredients. A person in your kitchen has to answer.
- Substitutions it isn't sure about. "No onions" is easy. "Make it like the one you did last month" is not.
- Items that sold out. Someone has to tell the agent when a dish comes off the menu, or it will keep offering it.
- Complaints and refunds. These go to a person, fast.
- Anything not in its data. It says it doesn't know and offers a callback. I cover that in what an AI receptionist does when it doesn't know the answer.
A wrong answer about the menu on a busy night costs more than a missed call. Test it before the real rush. My suite runs 38 simulated callers and 114 calls per run for about $0.25, and I describe it in how I test AI phone agents. For a restaurant you can do a small version yourself: call ten times with awkward orders and read the tickets.
What does it cost?
The voice agent is a $900 build and $450 a month with 500 minutes included, then 15 cents a minute. The first three clients get the build at $600. On the pricing page, 250 calls a month is about 500 minutes and stays at $450. At 500 calls a month you pass the included minutes and pay $525.
Compare that against your own missed-call count, not a vendor's.
When is an AI phone agent not worth it?
- You rarely miss calls. If most orders come through an app or your counter, calls are a small share and the phone is not your problem.
- Your orders are complex. Catering, large parties and heavy customisation need a person.
- Your menu changes daily and nobody will update it. The agent only knows what it was given.
- Your guests expect a human. Some will hang up on a machine. The agent should offer a person the moment someone asks.
- No one will check tickets. If the order lands on a tablet nobody watches, you have built a faster way to lose orders.
Checklist before the next Friday
- Count the calls that rang out in the last four Fridays, 5pm to 9pm.
- List the order types the agent may take, and the ones that go to a person.
- Ask where tickets go and who watches that screen.
- Ask what happens on a timeout, and that retries cannot double an order.
- Set a fallback number for overflow calls.
- Call the agent ten times with awkward orders before it goes live.
To hear one first, call the restaurant demo and try to confuse it.