He trained for six years in Osaka before he ever cut fish for money, and when he opened his own room on Coleman Boulevard in 2016 he had the phone number painted on the front window in vinyl because he could not yet afford a sign. The number is still there. For most of the last decade it was the least reliable thing in the building. The restaurant is ten seats at a counter and forty-four in the dining room.
He runs two omakase seatings, 5:30 and 8:15, six nights a week, dark on Mondays. The counter is a fixed-price menu he changes daily around whatever comes in from his purveyor, and the dining room is à la carte with a takeout window that has quietly grown into a third of the business. All of it runs through one phone line, and that line was answered by whoever happened to be closest to it. During service that is nobody.
A host mid-seating puts down a party of six to answer, or a server steps away from a table, or it rings eleven times and goes to a voicemail box that had been full since roughly 2019. He had a rough sense this was costing him. He did not know the size of it until we counted: over three weeks the restaurant took four hundred and twelve inbound calls and did not answer a hundred and forty-seven of them. Ninety-one of the missed calls landed between 6:00 and 8:30 on Friday and Saturday, which is exactly when a person calling a sushi restaurant intends to spend money that night.
The calls that were answered were not much better. Takeout orders were written on a pad by whoever picked up, in whatever shorthand they used, and the kitchen got them at the next convenient moment. Every caller was told twenty minutes. Actual pickup times ran fifteen to fifty depending on how many counter courses were firing.
The kitchen was remaking eight or nine misheard orders a week — a spicy tuna roll that was supposed to be a spicy salmon, a shellfish allergy that made it onto the pad but not onto the ticket. What we built answers on the first ring, every time, and knows the restaurant. It holds the current daily omakase menu, so when someone asks what the counter is serving tonight it says what is actually on the board rather than reading a stale website. It books both seatings against the real reservation system and understands that the counter is ten seats and cannot take a party of twelve.
It takes full takeout orders in conversational language, maps "the crunchy one with eel" onto the actual menu item, reads the order back before it commits, and pushes it straight to the kitchen printer with allergy and dietary flags on their own line. It quotes a pickup time calculated from how many tickets are open right now, not from habit. It answers the questions that made up almost half the call volume anyway — hours, parking behind the building, whether they take walk-ins at the counter, how far in advance omakase books. And it hands off to a human immediately when the caller is a purveyor, a vendor, or anyone it cannot confidently serve.
It has been live since spring. The restaurant has not missed a call since. Thirty-one percent of the reservations it books now come in outside business hours, which is a category of customer he simply never had — the person who decides at eleven at night that Saturday should be a special occasion. Kitchen remakes from bad phone orders have gone from eight or nine a week to about one.
The host stand gets roughly two hours back per shift, and those two hours go to the people standing in front of it. He was skeptical of the whole idea for a while, mostly on the grounds that his restaurant is a hospitality business and a machine answering the phone is the opposite of hospitality. What changed his mind was not the technology. It was the hundred and forty-seven.