When we had one store, the phone was a people problem. Whoever was closest to the counter picked it up, and most of the time that worked. When we had four, it turned into a systems problem, and for a long time we kept trying to solve it with people anyway.
This is what we learned running phones across our own four stores in San Diego, and what we would tell any multi-unit operator who is about to add a location and is wondering who is going to answer its line.
The per-store coverage problem
Every location has its own phone, its own rush and its own short-staffed Tuesday. The trouble is that the rushes line up. Lunch peaks at roughly the same hour at every store, which means the moment the phone matters most is the moment every store is buried at once. Roughly 30% of restaurant calls go unanswered, and in our case it was not one weak store dragging the average down. It was every store, at the same time of day.
What made it hard to fix was that we could not see it. A missed call does not leave a ticket on the rail. Each store had a phone bill and a voicemail box nobody checked, and the only signal we got was a manager telling us it had been a crazy shift. Multiply that by four and you are running a portfolio where you do not know how many customers tried to reach you last week.
The missed calls are not all the same size, either. Most are someone asking about hours or ordering a sandwich. Some are an office manager trying to feed forty people, and the average catering order is $500+. When that call rings out at noon, the office manager does not leave a voicemail. They call the next place on their list.
The two usual fixes, and where each one breaks
Most operators try one of two things. We looked hard at both.
Staff the phone at each store. Make answering the phone part of someone's job at every location. This is the obvious move, and it fails in a predictable way: the person covering the phone is front-of-house, and front-of-house is the first role pulled onto the line when the rush hits. You end up paying for coverage at every store and still losing calls at the peak, because the peak is exactly when that person is needed somewhere else. Then add sick days, turnover, and training every new hire on the menu, the pricing and the catering lead times, once per store.
Centralize the line. Forward every store's number to one person or an outside answering service. That fixes the pulled-onto-the-line problem and creates new ones. A person can take one call at a time, and since every store's rush happens together, the queue forms exactly when it hurts most. The person on the central line also does not know that one store closes an hour early on Sundays, or that another has a different catering minimum. The caller gets an answer, but often the wrong one for their store.
| Staff at each store | One central line | One AI agent across stores | |
|---|---|---|---|
| Lunch rush at every store at once | Phone loses to the line | Queue forms, calls wait or drop | Every call answered on the first ring |
| Knows each store's menu and hours | Yes, once trained | Rarely, without a lot of notes | Yes, configured per store |
| Adding a new location | Another person to hire and train | More volume on the same line | Forward the line, set up the store |
| Can you see what was missed | No | Partly | Every call has a transcript and recording |
One agent across every store
What we built for our own stores is Maya, and the reason it works across locations is that she does not get busy. She answers every store's line after one ring, and she answers them at the same time, so noon at four stores is just a set of calls, not a pile-up. Each store gets its own setup: its own voice, hours, menu and pricing. The Sunday early close and the different catering minimum are right on every call, because she is answering for that store, not for the company in general. She speaks English and Spanish and switches mid-call when the caller does.
She also knows when a call should not be hers. When a customer asks for a person, a complaint comes up, or a big catering lead wants to talk to someone, she warm-transfers to that store's manager and introduces the situation before bridging the call. When someone places an order, she takes it down and texts it to the store so the team only has to make it. To be plain about one thing operators always ask: she does not inject the order into your POS. Your staff still ring it in. What changes is that the order arrived at all.
Adding a store does not mean adding a person. Each location keeps its existing phone number and forwards the line, which takes about two minutes per store, and then that store's menu and hours are set up once. One four-store operator went live end-to-end in about 25 minutes. The cost is a flat per-store monthly plan, and the pricing page lays out what each tier includes.
Reporting: seeing every phone at once
The part we did not expect to value as much as we do is the reporting. For the first time we can see the phones across the portfolio instead of guessing. Every call has a full transcript and recording. The dashboard shows each store's calls, and the multi-store view puts the stores side by side, so you notice when one location's calls look different from the rest. On the POS systems we integrate with, orders Maya books are matched to a register transaction, so the revenue number comes from the register rather than an estimate.
As of October 2026, Maya has answered 5,200 real customer calls at our own stores. Reading through even a slice of those transcripts told us things no manager had: which questions repeat, which store gets calls well before it opens, and how many people call simply to ask whether we cater. Those are operating decisions, and we were making them blind before.
My routine now is simple. Once a week I look at each store's calls, read the transfers and the catering calls, and check whether any location is getting questions the others are not. It takes a few minutes per store. Before, the equivalent was asking four managers how the phones were and getting four versions of "busy."
What it means for your staff
The title says without adding staff, and that is the honest version. Nobody's job is "answer the phone during the rush" anymore, because that job never worked. Your team makes food and serves the people standing in front of them. Your managers get rung for the calls that actually need a manager, which is a lot fewer than every call.
In our own stores, sales are up about 40% on this model. That is our result in our stores, not a promise for yours, and it came from a lot of things working together, not the phone alone. But the phone was where the leak was easiest to see once we could finally see it.
If you run two or more stores, do a quick count before your next opening. How many lines do you have, how many hours of overlapping rush, and who is actually picking up during them. If the answer is "whoever is closest," you already know how this goes at five stores. It is worth fixing before the next one, not after.