Day one of a new way I run Suite 200 Grille and Whiskey & Water with my AI team.
I used to get interrupted all day. Decisions, follow-ups, "hey can you look at this." Today I tried something different: one Morning Brief with everything that needs a yes or no, about fifteen minutes to clear it, then one focused block. Monday is money. Tomorrow is events. Wednesday is staff. The rest of the day the team keeps moving without me in the middle.
The win that actually showed up on Google: we cleared a backlog of unanswered negative reviews at Whiskey & Water. Fifty of them. I wrote the voice myself — personal, from the owner, owning that it was a bad experience and inviting people to reach out so I can make it right. No template. No kitchen excuses. Then I approved the batch and the assistants posted every one.
Those reviews had been sitting for months. Guests who had a rough night got silence. Tonight they get a real reply from me.
The miss: the Brief landed late this morning because too many routines were stacked on top of each other. The system didn't hide that. It showed me the leak. We're fixing the schedule.
That's the part I keep learning. The AI doesn't just do the work. It shows you where your business has been leaking, and then you decide what to fix.
If you own a restaurant or a small business and your bad reviews are just sitting there — what's stopping you from answering them?
Yesterday I shared what my AI team has built over the last two months. Here's what the back half of a busy Sunday actually looked like.
Football on at Suite 200, a busy dinner at Whiskey & Water, and the phones ringing.
An AI answers our calls. When someone asks for a live person, it transfers them to the host stand. Last night, several of those transfers rang out or went to voicemail during the rush.
That used to be a lost table. Now, when a caller hangs up or can't reach anyone, my reservations assistant texts them back, usually within a few minutes, asks for a time and a name, and books it straight into our reservation book if they answer. It also double-checks every table the phone AI books on its own against the actual book.
It doesn't nag. It follows up about an hour later, and if they're not interested, it lets it go.
The misses:
A guest texted asking about our game-day specials, and the answer sat for about half an hour before we caught it.
Most of last night's callbacks haven't answered yet. Some people just go somewhere else.
And the real lesson: my host phone isn't getting picked up during a rush. The AI didn't fix that. It showed it to me, and that's on me to fix.
That's the part people miss about AI in a restaurant. It's not just doing the work. It shows you exactly where your business is leaking.
Where's yours leaking?
Today I was covering shifts on the floor of my restaurant. Meanwhile a team of AI assistants booked a party of 10, fixed our online booking rules mid-service, posted for game day and kept my books moving.
Two months ago I posted that I'd been running @bot hard for 24 hours. Here's what that turned into at my two restaurants, Suite 200 Grille and Whiskey & Water.
It's a full team now: a chief of staff plus assistants for reservations, outreach, purchasing, bookkeeping, finance, operations and content.
The results:
We're saving $1,500 a month on bookkeeper costs. It caught up 8 months of books, reconciled them to the penny and found about $28k in errors.
About 3,000 local businesses invited to Community Appreciation Nights, with 17 nights and 200+ guests booked.
Guest texts answered within minutes, and big parties booked straight from a text.
100+ Google review replies posted.
My chefs' handwritten inventory sheets turned into food orders. I just press submit.
How it's grown:
At first I approved everything. Now my rules are standing orders, and I only see real decisions.
It learns from corrections. I fix something once and it sticks. I wrote three review replies myself, and it learned my voice from them.
It got faster. One month of bookkeeping now takes about a fifth of the effort it used to.
It finds its own gaps. Our follow-up was weak, we caught it, and the fix starts Monday.
It changed how I work. My week now runs on set decision windows instead of a thousand pings.
Most restaurant owners aren't doing this yet. It's a game changer.
What would you hand off first?
@bot@elonmusk@theallinpod@chamath@Jason@DavidSacks@friedberg
I’m Anthony Battaglia. I’m a chef/restaurateur and, with my wife and business partner Kelli, operate two restaurants in Georgia:
Suite 200 Grille in Milton and Whiskey & Water in Blue Ridge.
I’ve been running Grok’s new @bot AI agent platform HARD for ~24 hours.
Not testing it. Not playing with a demo.
I dropped it directly into the middle of TWO operating restaurants.
Real guests. Real employees. Real reservations. Real inventory. Real vendors. Real money.
In ONE DAY I built an AI team with named agents responsible for:
• Chief of Staff
• 5 email inboxes
• Guest follow-up
• Hostie + Resy
• 7shifts
• Google Business + marketing
• Bar variance
• Chef inventory → PFG ordering
• Monthly reporting + compliance
• Executive reporting
But this is the part that really got me:
The first time I asked one of the agents to take my chef’s handwritten inventory/order sheet, go into our actual food distributor’s website and build the order cart…
It was basically a disaster. 😂
Wrong workflow. Confusion. Multiple agents touching the cart. Not good.
So I took over.
I clicked the TEACH button on the agent’s screen, did the order myself, and showed it EXACTLY how I read the chef sheet, find products, determine quantities and build the cart.
We turned that into rules and a reusable process.
Then I gave it the order for my OTHER restaurant.
It went into the distributor website on its own and built the cart almost flawlessly.
One or two mistakes.
That happened in less than 24 hours.
And that’s just ONE workflow.
Another agent is pulling monthly sales reports from our restaurant systems, extracting the numbers I need for local taxes/compliance, and filling out the actual PDFs I have to submit to the city and state.
Another is monitoring guest calls and texts, checking the reservation book, communicating with managers through 7shifts and closing the loop with the guest.
Another is watching 5 email accounts and deciding what actually needs my attention.
Another is working on Google Business, local SEO and marketing.
And they talk to EACH OTHER instead of everything coming back through me.
That’s the part people need to understand.
This isn’t just AI giving me answers.
I’m teaching it how I operate.
It screws up. I correct it. The lesson becomes a rule, SOP or permission. Then the next time it can actually DO the work.
And yes, there have been plenty of screwups. 😂
Duplicate emails. Agents stepping on each other. Bad assumptions. Browser issues. A few “what the fuck are you doing?” moments.
But every failure has made the system better.
24 hours ago none of this existed.
I’ve spent my career operating restaurants. I’m not a developer and I’m not trying to build an AI demo.
I don’t need another chatbot.
I want an AI workforce that learns how WE operate and removes the repetitive operational bullshit from my day so I can focus on food, people, strategy, growth, investors and my family.
The good, the bad and the ugly — after only 24 hours, @bot feels like a glimpse of where small business is going.
@elonmusk — this is fucking wild.
Give me 30 days.