A hole at the wine bar is not a table at the noodle shop

A guest calls the number printed on the website at 19:08 and asks for a table tonight, any of your places. You have three restaurants. The wine bar is full until 21:30. The cafe has already turned the brunch line off. The noodle shop has a two-top at 20:15 and a forty-five-minute turn that does not match what this guest wanted. If the person on the phone treats those three books as one calendar, you will seat a wine-bar party in a room that is plating ramen.

An AI receptionist for a multi-location restaurant group has to keep each door's book, hours, menu, and wait local. A hole at location two is not a table at location one. Whether you publish one main line or a number per store is a routing choice. It is not a reason to flatten the floorplans.

The host at each door still owns the room. The line is overflow: lunch, the 8pm wave, after close, the second call while someone is walking a four-top. A single restaurant that already answers every ring does not need this. A team shopping for a new POS does not need this either.

Three doors are three books

Helen owns three restaurants that share a logo and almost nothing else.

The noodle shop opens at 11:30. Lunch is a forty-five-minute turn. Tomas runs the book on OpenTable. The line is English and Japanese. A six at 12:30 is what that door sells, not a 90-minute wine-bar seating.

The wine bar opens at 16:00. Two-tops at 19:30 are the product. Isabel hosts, and the line is English and Spanish. Deposits live in OpenTable for parties of six and up. The dining room does not serve lunch, does not serve ramen, and does not take a brunch party at 10:30.

The cafe opens at 08:00. Brunch until 14:30, a short dinner until 21:00, then dark. Nate's book is Square for the till and a reservation list that only exists after 17:00. The line is English and Vietnamese. The wine bar does not take brunch.

Hours, menus, and turn time do not match across the three doors. Wait at the noodle shop at 12:15 is a high-top problem. Wait at the wine bar at 19:10 is a dining two-top problem. If you copy one script across three doors, guests hear three companies, or worse, one company that keeps seating them in the wrong room.

The National Restaurant Association's 2026 State of the Restaurant Industry report put U.S. sales at a projected $1.55 trillion, with more than nine in ten operators still naming labor as a significant challenge. Last year, 42 percent of operators said the restaurant was not profitable. That is not a reason to fire the host at each door. It is a reason not to add a fourth job to three stands at once.

Peak call times sit on peak service. QSR Magazine's 2026 industry estimate treated missed calls as a structural leak, not a staffing mood. Across three doors the leak compounds. One door invents a script. The second lets voicemail die. The third quotes a wait from memory.

A hole at location two is not a table at location one

This is the rule that has to be true before anyone answers the phone.

When a four-top cancels at 19:00 at the noodle shop, that hole belongs to Tomas's book. It is a forty-five or sixty-minute turn, a section he can actually run, a waitlist of people who wanted noodles tonight. It is not a four at Isabel's wine bar. It is not a brunch four at Nate's cafe tomorrow. Filling it from the wrong list is how you get a dressed-up two-top in a steam-filled dining room, or a family of four at a bar that does not have high chairs.

The same rule runs in the other direction. Isabel is full. A guest on the main line says, "put us at the other location." If Helen has not written that as a yes, it is a person. Cross-booking sounds helpful on a spreadsheet and brutal on a Saturday. The wine-bar guest wanted a 90-minute two-top with a list. The noodle shop can give them a counter seat in twenty minutes. Those are not the same product.

Write the isolation in plain language and hang it where the stand can see it.

• Each door's OpenTable, Resy, or Square book is the only book that door sells.
• A cancel, a no-show, and a waitlist live on that door.
• A guest who asks for "any table tonight" is offered only the doors Helen allowed, in the order she wrote, and only if that book can take the party size and the turn.
• A dark room is not a yes. The cafe after 21:00 does not get a 21:15 seating because the wine bar is slammed.

Filling a cancel on one book is its own sequence. Who you text, how long you wait, patio versus private dining, all of that sits in OpenTable texts the guest. It never texts about the cancelled table.. The waitlist itself, quoted wait versus actual wait, is A 25-minute quote that turns into 40 is how you lose the table. Do not let the front-desk agent pretend it is also those jobs.

Store number versus the main line

Operators buy two phone setups and then mix them in the guest's ear. Pick one on purpose.

A number per store is the honest default. The guest who called the wine bar wanted the wine bar. The agent, or the host, reads Isabel's book, Isabel's hours, Isabel's menu, Isabel's wait. If that door is full, the true answer is full, not "we have a sister restaurant." You can offer the noodle shop only if the guest asks, and only if Tomas's book can take them.

A main line is a routing problem. Someone, or something, has to ask which location, then bind the rest of the thread to that book. "Any of your places tonight" is the dangerous case. Check the books Helen allowed, in the order she wrote. Offer the one that can take this party size at a time the guest will actually sit. Do not offer a 21:00 cafe two-top to a guest who wanted 19:30 at the wine bar and call it helpful.

Do not assume a shared number just because you have three doors. Some groups keep a number per store and the same agent job on each. Some publish one number and route. The constraint is the book, not the DID. Flattening three kitchens into one calendar fails before the first Saturday.

Putting the same agents on three doors without mixing hours is its own walk-through: Start with the door that already loses the phone, not the newest lease. The wider stack, if you ever staff more than the line, is Four doors, four calendars. One shared inbox is where it breaks.. Front desk is still the first hire, because the unanswered ring is the constraint you can name at 19:08.

Hours, menu, and wait do not travel

Guests will ask for brunch at the wine bar. They will ask for the tasting menu at the cafe. They will ask if the wait at location one is shorter. The true answers are local.

Hours stay on the door that published them. The wine bar is closed at 10:30. The cafe is dark after 21:00. The noodle shop does not take a 21:30 four on a Tuesday if Tomas has already turned the fryer down. After-hours voice still has to land on a table that will exist tomorrow, on that door, not on a hope.

A dish this door does not serve is a stop. The agent does not sell ramen at the wine bar because the guest is hungry and the wine bar picked up. Off-menu at one location is not a transfer to another location unless Helen wrote that rule.

Quoted wait at the noodle shop is a different number from quoted wait at the wine bar. Party size is local. High-tops at Tomas's counter are not Isabel's banquettes. If you quote the wine-bar wait to a guest who called the noodle shop, you have already lied.

Language is local too. Japanese and English on Tomas's line. Spanish on Isabel's. Vietnamese on Nate's. The guest is answered in the language they already used, on the door they called. An English-only main line dumped onto three bilingual stands is how Saturday sounds like a call center.

Large parties stop at the threshold you named per door. Eight or more at the wine bar is a deposit and a person. Six at the noodle shop may be a table Tomas can take on a 45-minute turn. Do not copy the wine-bar policy onto the noodle shop because it felt consistent.

OpenTable's diner help, updated in 2026, is clear that each restaurant sets its own cancellation and no-show policy. The POS is the policy layer. The agent is not. If a guest wants to fight a deposit at Isabel's, the thread stops. OpenTable still owns that fight.

What the agent is allowed to finish

LLDTEK is an agent platform. For a group, the first job is front desk: answer the line, read the local book, book the table that is actually free on the door that owns it, stop when a person is required. It sits beside OpenTable, Square, or the book each door already runs. It does not replace the host. It does not replace checkout. It does not replace a deposit policy.

Restaurant Business reported in 2026, citing the National Restaurant Association, that 74 percent of operators say technology will augment people, not replace them. That is the correct shape. A firing plan for three hosts is the wrong product.

You do not start with five agents on three doors. You start with the line. Recovery, which fills a cancel from that door's waitlist, is a different job. Rebooking, reputation, and floor can wait. Mix them on day one and a guest who called for Saturday brunch gets a review ask while table 12 at the wine bar sits empty.

Watch the run from one inbox, with three calendars. Helen does not sit the pass at three addresses. She should see live runs, the threads that need a person, and whether the agent called Tomas's book or talked past a handoff. If it books the wine bar for a ramen request, it is not live. If it talks past a VIP Isabel named, it is not live. If it answers Nate's cafe in the wrong language, it is not live.

Staff the doors that miss the line. Leave a quiet cafe alone if Nate already picks up every ring, including after close. Multi-location is not a package you have to put on every storefront.

If one of the three books is actually broken, double seats, no floorplan, no hours anyone trusts, fix that book. Switching POS to get a smarter phone line is the wrong trade. Payments stay with the processor you already use.

The demo is thirty minutes against the three books you actually run. What that call has to prove is in What to test on an AI receptionist demo.

How big the group has to be

Size is a constraint, not a package.

One door that already answers every ring can skip this. A person who is free at the stand does not need an agent on the overflow.

Two or three doors where the host cannot leave the pass is the brief. Separate books. One owner view. One standard on the line, local hours and menus underneath.

Five to eight doors with the same constraint is still the same agents on separate books. Do not assume a shared number. Do not assume a shared menu. Design it door by door.

A twelve-door group with a central reservations office is a different design. If people already sit a phone bank and can see every book, the gap may be smaller. If that office still misses the 8pm wave, look at overflow. Do not sell a surprise bundle.