A $300 AI Host Kept a Texas Restaurant Open

Abbas Zoeb, owner of Wok & Karahi in Spring, Texas, did not post a job listing when he lost his only server. He installed an AI host named Haniya, paired her with QR-code ordering and prepayment, and kept the doors open. According to The Cool Down, the restaurant is now saving $9,650 a month. The software costs $300. That's about $10 a day.

I've written about AI receptionists for dental practices and hotel front desks and med spas. But this one stopped me, because this isn't a business that adopted AI to get ahead. It's a business that adopted AI to survive. That's a different conversation, and it deserves a different kind of attention.

What actually happened at Wok & Karahi

Wok & Karahi is a family-run Chinese, Indian, and Pakistani restaurant in Spring, Texas. When the restaurant lost its only server, owner Abbas Zoeb, a former Google software engineer, made a call that most restaurant owners wouldn't think to make. He rebuilt the service flow around an AI host instead of replacing the human.

Haniya, the AI host, handles customer interactions: greeting diners, fielding phone calls after closing, and speaking seven languages. QR-code ordering and prepayment handle the transaction side. The kitchen staff and chef now collect 100% of tips, since there's no server to split with.

Here's the math as reported by The Cool Down, citing Fox 26 Houston: $3,500 comes from cutting the server salary, and the rest of the $9,650 in monthly savings reflects efficiency gains and recaptured revenue. Zoeb's own words: "It started out of desperation. We could not keep begging one person to show up. Now nobody has to, and our guests and our team are better off for it."

I am not going to insult your intelligence with the obvious. Okay, I am in this next line, but stay with me: desperation is a faster teacher than any consultant.

The "one critical employee" problem has a name now

Every restaurant I have ever talked to has a version of this story. It's not always the server. Sometimes it's the person who opens. Sometimes it's the only one who knows the POS system. Sometimes it's the driver who does three jobs and everyone knows it and nobody wants to say it out loud. One person holds the thing together, and when they leave, you find out how fragile the whole operation actually is.

I'm going to call this the Single Thread problem. One person, one point of failure, and the whole service collapses when that thread snaps. Zoeb didn't just solve a staffing problem. He eliminated a Single Thread.

That reframe matters. If you install an AI host because you're trying to cut costs, you might talk yourself out of it. If you install one because you refuse to let one person's bad week close your dining room, you'll find the $300 in about thirty seconds.

What this means for your restaurant

Let me be direct about what this system does and doesn't do, based on what was actually reported.

It handles phone calls, including after-hours calls. It speaks seven languages. It works alongside QR-code ordering and prepayment, so the front-of-house interaction is mostly handled without a human intermediary. It does not replace a cook. It does not manage a reservation book in a fine-dining context without real care put into the prompts.

That last part comes from Professor Dietrich von Biedenfeld of the University of Houston Downtown, who told Fox 26 that this setup is "a very effective tool for a fast-food restaurant or a quick lunch spot, but for fine dining, the AI is only as good as the prompts." He's right. The tool fits the environment. A casual family restaurant running QR ordering is a very different animal than a tasting-menu room where the server is part of the experience you're selling.

So ask yourself two questions. First, is the human interaction in my restaurant a differentiator people are paying for, or is it just the mechanism by which I deliver food? Second, do I have a Single Thread right now, and what happens to my operation when that thread snaps? If your answer to the first is "mostly mechanism" and your answer to the second keeps you up at night, you're the exact customer this is built for.

If you want to see how this plays out at a different scale, a hotel in Singapore ran 3,400 bookings with no human at the desk, and the math worked out similarly. Different industry, same principle.

Under the hood, for the curious

The source doesn't name the specific software platform Haniya runs on, so I won't guess. What I can tell you is that a $300-a-month AI host at this capability level is consistent with what I've seen from vendors in this space: multilingual voice and chat agents, phone answering, and integration with QR-based ordering systems. The tech is not exotic. It's the same category of tool we've set up for restaurant and service business clients who need a front-of-house presence that doesn't call in sick.

The seven-language capability is real and worth flagging. In a diverse market like Spring, Texas, that's not a feature for a press release. That's a functional thing that determines whether a customer can order at all. Zoeb's background as a software engineer probably made him comfortable setting up the prompts and the integrations correctly, which von Biedenfeld's comment suggests is where most restaurants will need help. The tool is only as good as what you tell it to do.

The prepayment and QR-ordering piece is doing a lot of work here too. The AI host isn't replacing a server in isolation. It's the front end of a redesigned service model. You can't just drop Haniya into a traditional table-service setup and expect the same results. The whole flow was rebuilt.

What to do this week

If you run a casual restaurant, a fast-casual spot, or a family place and you're carrying a Single Thread right now, here's where I'd start.

First, write down the one or two people your operation cannot function without, and be honest about what would happen on a Tuesday if they didn't show up. If the answer is "we'd be in trouble," you have a Single Thread and it's worth pricing a solution before it snaps.

Second, look at your phone situation. Yelp is already calling your restaurant to check wait times on behalf of customers. If nobody's picking up or if after-hours calls are going to voicemail, you're losing business that an AI host would catch at $10 a day.

Third, if you're intrigued by the QR-ordering-plus-AI model, don't try to bolt it onto an existing service flow. Zoeb rebuilt the flow from scratch. That's the part that made the savings real.

You can skip this one if

You run a fine-dining room where the server-guest relationship is a genuine part of what people are paying for. The professor said it clearly and he's right. An AI host in that environment is only as good as the prompts, and prompts won't replace a sommelier who reads the table. This is a tool for a specific kind of operation, and there's no shame in knowing yours isn't it.

One thing worth sitting with

Zoeb said it started out of desperation. That's almost always how the useful innovations actually start. Not in a planning meeting. Not in a vendor demo. In a Tuesday morning panic when someone doesn't show up and you have sixty covers on the books.

The businesses I've watched do this well are not the ones who adopted AI because they read about it. They're the ones who had a problem that was costing them real money every single week, and they finally got tired of living with it.

You probably already know what your Single Thread is. The question is whether you're going to fix it before it breaks, or after.

Sources

• Texas family restaurant says $300 AI host saved them after losing their only server, The Cool Down, Ray Brennan, October 25, 2026