A 5-minute read explaining the purpose of the operator OS, the five agents behind it, how Josh's content + catering pipeline + restaurant ops connect through one system, and what it takes to ship it without changing a single tool you already use.
A creator-led restaurant has two sets of demand happening at the same time. Local customers want lunch by 12:15. National Sknny Chef followers want a reply by tomorrow. Catering inquiries come through 5 different channels. Nobody can be everywhere — but everything below is doable by a small fleet of agents that report to you.
Every agent reports to Josh through a single Monday queue. None of them sends anything to a customer or follower without his approval. This isn't autonomous; it's deferential.
Answers the phone in 2 rings, bilingual ES + EN, takes orders straight into Toast, books catering inquiries to Josh.
Reads every Sknny Chef comment + DM across 4 channels. Triages into qualified leads, replies on-brand, surfaces the 12 things only Josh can answer.
Owns the catering pipeline — ezCater, phone, web, IG DMs. Qualifies, drafts quotes, books on the kitchen calendar.
Watches every Google + Yelp + Tripadvisor review, drafts brand-voice replies in the original language, pushes happy customers to leave more.
Clips Sknny content from kitchen cameras, drafts captions in Josh's voice, sequences posts across YouTube, TikTok, IG, FB.
Josh's only weekly time commitment to the system. Tuesday through Sunday the agents work; Monday Josh reviews + approves what they queued for him.
One link · phone. All 5 agents' queues sorted by priority. Coffee in hand.
3 weekend catering inquiries. Read the auto-drafted quotes. Approve, edit, or send to Jesse.
El Vocero filtered 600 comments down to 12 that need Josh's voice. Reply with one click each.
El Productor cut 5 clips from last week's kitchen footage. Approve the 3 best for posting Tue-Thu.
Reviews, lapsed-guest texts, phone-order AI all running automatically. Josh's done.
The system doesn't replace anyone. It picks up the work nobody currently has time to do — and hands the rest back to the team that's already great at it.
| The work | Josh + Jesse + team | The Operator OS |
|---|---|---|
| Reading 500+ Sknny comments/day | (Nobody has time) | Triages, replies, escalates 12 things to Josh |
| Answering the 12-1pm lunch rush phone | Counter staff when they can | Picks up calls counter can't, takes orders in ES + EN |
| Decide which customers get a personal Josh reply | Josh — Monday review | Surfaces the 12 that matter. Doesn't pick. |
| Cook the food + run the line | Jesse + kitchen team — same as today | (Stays out of the kitchen) |
| Quote a 60-person school fundraiser | Josh — 5 min on the phone | Drafts the quote with availability check + menu + pricing |
| Reply to a 5-star Spanish-language Yelp review | Was: nobody. Now: 30-second approve. | Drafts in matching language + tone |
| Take an Inner Circle Zoom call | Josh — Wednesday 2pm | (Stays out of the Zoom) |
| Catch missing items in takeout bags | Counter staff during rush | QA vision check at the expo station before bag leaves |
Everything attaches to Toast + Instagram + ezCater + YouTube via existing APIs. The team keeps using exactly what they're using today.
Toast API key + Sknny Chef social handle access + ezCater export + Roxanne's web inquiry form route. Read-only at first.
El Vocero reads 30 days of past Sknny comments + replies. Tunes to Josh's voice. Josh reviews 20 sample drafts, marks the bad ones.
El Concierge handles next 10 catering inquiries with Josh approving every quote. Calibrates pricing + availability + menu by close.
First Monday review queue lands in Josh's inbox. Phone-Order AI goes live during lunch rush. Content engine starts clipping kitchen footage.
We map your existing stack (Toast, Sknny channels, ezCater, kitchen cameras), agree on which 3 agents ship first, and lock the 30-day Foundation tier build. Production tier kicks in month 3.
Schedule the build ← Back to dashboard