Start with the door that already loses the phone, not the newest lease

Dev owns three studios in one metro and he can already tell you which door still loses the phone. Ash Street is the flagship: colour that cannot overlap, Vietnamese and English on the line, Kira at the desk, full most Saturdays. Riverside is more walk-in cuts, Spanish and English, Tomas on the door, open an hour later. Elm already answers, including after close, and the book is quiet enough that a person can still pick up. The jobs he wants are the same at every address. The calendars are not the same. A hole at Riverside is not a chair at Ash unless he writes that rule down.

The rollout is a sequence, not a group toggle. You pilot one door, copy the job rather than the hours, rebind the book, and train the person who still owns that desk. Watch week one for the loud failures, then week four for the quiet ones. The operating model those jobs sit on is Four doors, four calendars. One shared inbox is where it breaks.. This page is the order of work: which door first, what you copy, what you leave, and what Kira has to be able to do on a Thursday before you touch Riverside.

Start on the door that already loses the line

Pick the loudest book that still drops rings, not the newest lease and not the door with the cleanest Square setup. For Dev that is Ash. The floor is in colour, Kira is greeting a walk-in, and the second line is already a voicemail. Elm does not need coverage. Riverside can wait a week. Fit is per book, not per brand. If you go live on three doors because the workspace has a location dropdown, you will spend the first Saturday arguing about which waitlist just got texted.

Listen on that door only, for a week you actually work.

1. Write the hours you answer, including the real close, not the hours on the door sign.
2. Write the languages that already happen on the line, with an example thread for each.
3. Write the menu the agent is allowed to sell, with duration, and the things it must never promise.
4. Name the stop person. At Ash that is Kira. Write the VIP list she already keeps in her head.
5. Write whether anyone is allowed to travel to a sister door. If the answer is no, write no.
6. Staff front desk only, with tools on who is open, duration, and the calendar you already run, on the number and the web form you already publish.
7. Watch a real Saturday on that book before you copy anything.

Tuesday will lie to you, because the floor has air and a transcript looks fine when nothing collided. Saturday at Ash is Mina in a colour, a walk-in who will not hold, and a Vietnamese text for a combo while Kira is at the door. If the agent cannot book the person who is actually free, or if it talks past a handoff Kira was supposed to take, it is not live. The Saturday watch itself is Tuesday will lie to you about whether the agent actually works. An Ash combo landed on a Riverside chair is a bind failure, not a staffing mood.

Do not staff recovery, rebooking, reputation, and floor on day one, and do not staff them on three doors because front desk looked fine in a screenshot. Five agents on three books is how a group stops watching.

Copy the job and rebind the book

Once Ash is holding, copy the job description, rebind every argument to the next calendar, and leave the local facts alone.

What you copy is the work. Front desk answers voice, SMS, and web, and books the person who is actually free. Recovery, when you add it, texts that door's waitlist once. Rebooking puts the next visit with the same provider on that door's cadence. Reputation asks once, in their language, on that door's Google listing. Floor shows who is open on that floor. Those sentences travel from Ash to Riverside to Elm.

What you rebind is the tool layer. When Riverside's number rings, `who_is_open` reads Riverside, `book_visit` writes Riverside, and floor is Riverside's chairs. Ash does not appear in that run. The job description is identical. The arguments are not.

What you leave alone is almost everything operators try to clone because it would be faster. Ash closes at seven, Riverside runs until nine, and Elm is already dark on Monday, so after-hours voice on Ash's number books Ash's next open slot instead of hunting Riverside because the lights are on two miles away. Ash sells colour that cannot overlap a cut; Riverside sells walk-in cuts and a short list. Mina sits Ash, Riverside has a different bench, and a tech who works Ash in the morning and Riverside at four is a schedule in the POS, not a merge. A hole at Riverside is Riverside's duration, chair, and list. Kira names Ash holds. Tomas names Riverside's. Google wants one profile per address, so the review ask follows that listing. Keep a number per door unless you already publish one, because a mashed number sends Riverside walk-ins into Ash colour.

Sharing is a decision you write in the listen week: a membership allowed to travel, a client who asked for any door, a dining group that would rather seat a four-top somewhere than lose it. OpenTable for Groups will show sister availability when one room is full. That is a choice a GM can want. It is not a reason for recovery at Riverside to text Ash, and it is not a default the copy should invent because the owner view looks cleaner with one list.

Train the person who still owns the desk

This is the step groups skip because the agent is on the phone and the desk looks quieter. Kira still owns Ash. She greets, she checks in, she knows which hold she will never put through a model, and she takes the dispute. The agent covers the second line, lunch, a full book, and after close. That is overflow. It is not a replacement, and the longer version of that decision is Does an AI receptionist replace the front desk.

Sit with her for an hour before go-live and show her the actual inbox, not a slide. She needs to see what the agent is allowed to finish without her. A Saturday at 2 with Mina, combo or single service, booked on chair 3, is finished work, and she should not reopen that thread and book it again. She also needs to see a handoff: the Okonkwo hold, a bill fight, a custom duration Ash does not sell. The run should say handed off, with her name on it. If she cannot find that thread in the same inbox as the texts, she will miss it.

She needs a way to mark a slot as human, because recovery, when you add it, does not fill a chair she was saving. If that control is missing, she will hide holes in the POS so the agent cannot see them. She also needs to know not to race the waitlist. If recovery is already texting the 3:30, she does not also call the list from her pocket.

Tomas gets the same hour before Riverside goes live. Do not assume he will pick it up from Kira's Slack. The stop list is different, the language mix is different, and the walk-in rule at Riverside would wreck Ash colour if he imported it the other way. A desk person who was not trained will treat the inbox as the computer's job, ignore handoffs, and then tell you the agent is talking to VIPs. They are right. You skipped the person.

Keep languages on the door that heard them

Ash already runs Vietnamese and English. Riverside already runs Spanish and English. Elm is English. That mix is a fact of the line, not a brand voice you pick in a settings page. When An texts Ash in Vietnamese, the thread stays in Vietnamese through the confirmation. When Rafa calls Riverside in Spanish, the reply is Spanish. The review ask later uses the same language against that door's listing. You do not pick one brand language and hope the other door catches up.

The failure mode in week one is obvious: an English script on a Vietnamese Ash text. Pull the job. The failure mode in week four is quieter. Testers were English. Kira started answering English on threads that began in Vietnamese because it was faster. Riverside's Spanish volume dipped and nobody noticed the agent had drifted. Language is not a toggle you set once for the group. It is a property of the thread, on the door that heard it.

If you already publish one number for three doors, the language problem gets worse, because the door check has to happen before the language check. Keep the published line per door unless you have a reason not to, and train Kira and Tomas that they do not switch a thread to English to make the inbox easier to skim. After close follows the same rule. Ash's number at 7:40 is still Ash, in the language the caller used, booking Ash's next open hour, which is the extra constraint on After-hours AI receptionist that books. The night line does not get to discover a sister door that is still open.

What to watch in week one

Week one is isolation. You are looking for the copy to lie. A cancel at Riverside must not fill a chair at Ash. After close at Ash must not walk a caller to Riverside. A Vietnamese thread at Ash must not come back in English. A tool call must carry a door. The Okonkwo hold must land on Kira, not on Dev, and not on Tomas. Floor at Ash must not show a Riverside name. If Mina is mid-colour, Riverside must not see her as open. If Kira is racing the waitlist, the desk training did not take.

Watch a Saturday, not a Tuesday. Sit Kira at Ash. Dev watches from the owner view, filtering by door. If the workspace looks like one inbox, or if Dev starts taking desk threads because the screen looks central, isolation already failed, and you have not earned door two.

When a row fails, pull the job and fix the bind. Do not add recovery to paper over a bad copy. Recovery on a shared list will hide the isolation failure by filling chairs faster, which is the opposite of a fix. Week one is the live version of What to test on an AI receptionist demo, with last week's holes replayed.

Only after week one is boring do you bind Riverside: same job, new book, Tomas trained, Spanish on the line, different hours, menu, waitlist, listing, and number. Watch Riverside's Saturday before you touch Elm. Elm may never need the layer. If it already answers, leave it. Dev still sees the doors that are live. He does not pretend the quiet door needs coverage so the workspace looks even.

What to watch in week four

Week four is drift. The loud failures are gone, or you already pulled the job. What shows up now is slower, and it usually comes from people, not from the bind.

Language drifts to English because the last dozen testers were English and nobody sampled a real Ash thread. Kira has stopped opening handoffs because she assumed the computer would finish them. Tomas never got the hour Kira got, so Riverside's VIP list is still in his notes app. Dev has started answering from the owner view because it is one screen. That is how an owner becomes the fourth desk.

Hours change and nobody rebinds them. Riverside went to summer hours, and after-hours voice is still quoting the listen-week clock. Someone toggled a shared waitlist because a hole at Ash looked lonely, recovery inherited that toggle, and you are now filling Ash colour from Riverside's walk-in list, which is the problem you staffed this layer to avoid.

The desk test at week four is whether Kira still owns Ash. She should be faster at taking a handoff than she was in week one, not slower, and Tomas should be able to do the same at Riverside without calling her to ask what the inbox means. If either desk person is fighting the agent, you have a training problem, not a model problem. Sit the hour again. Do not turn on reputation to distract from it.

LLDTEK staffs this as listen, then bind, then watch. You do not prompt the agents, and you do not get a year-long rollout plan. The work takes days on the books you actually run. Add recovery when the holes are the pain and the lists are still local. Rebooking, reputation, and floor follow the same copy-and-rebind, never a dump of five tools onto three doors because the first screenshot looked clean.

Three doors is the proof size: enough that isolation can fail in public, small enough that Dev can still name Kira and Tomas. Ten doors is the same shape with a longer listen, and no right to go live on ten because three worked. Thirty doors is a call center. A booth renter sharing a room is not a second door. Two chairs in one shop are one book.

Does a hole at the second door fill the first

No, not unless you wrote that rule in the listen week. Recovery texts the waitlist for the door that lost the visit. Sharing is a decision, not a convenience the owner view should invent.

What if two doors run different POS tools

Keep both. Ash can stay on Vagaro, Riverside on Square, Elm on Booksy. Checkout stays with the processor you already use. Flattening three tills into one platform is how the stop gets lost.

Who sees runs across all three

Dev sees runs, holes, and handoffs, filtered by door. Kira sees Ash. Tomas sees Riverside. If the owner starts taking desk threads because the inbox looks central, isolation already failed.

When should a door stay off the agents

When it already answers every ring, including after close, when the book is broken, or when nobody will watch a Saturday. Kira's Ash can go live while Elm waits. Dev does not staff a quiet door so the rollout looks complete.