This is the delivery page rather than the research page. Three real restaurant situations the agent has to handle, the four-phase timeline from kickoff to live traffic, and the three numbers we commit to: 10 use cases mapped, $800–$3,200/mo savings range and 21-day implementation.
Three situations this has to handle
The Friday dinner rush — Friday at 6:45pm. Your dining room is at 90% capacity. Your host is at the door seating walk-ins. The phone rings 18 times in the next hour. In the old workflow, your host either ignores the phone (losing reservations) or runs back and forth (slowing seating). With the agent, every call is answered by Resy-integrated voice AI: 6 reservation requests get booked, 8 hours-and-parking questions get answered, 3 catering inquiries get logged for Monday callback, and 1 allergy question gets routed to the chef. Your host never leaves the door. Your manager is on the line, not on the phone.
The catering pipeline — Your restaurant does catering as a side line. Phone inquiries used to bounce when the manager was on the floor — maybe one in three converted. With the agent, every catering inquiry gets a structured qualifying conversation (date, headcount, food preferences, budget, location), gets the menu PDF, and gets the manager a callback slot. Inquiry-to-quote conversion roughly doubles. Over a year, catering becomes a meaningful incremental revenue stream you weren't capturing.
The no-show reduction — Your restaurant takes 50 reservations a night. In the old workflow, no-show rate hovers around 12–15%, costing you covers and prep waste. With the agent's two-way SMS + voice reminder flow (24 hours out, 2 hours out, with easy reschedule), no-show rate drops materially. Even a few percentage points across 50 covers a night, 365 days a year, translates to a meaningful revenue lift — pure margin, since the kitchen was already staffed.
The four phases
Week 1 — Discovery + scope. Map your POS, reservation system, catering menu, brand voice, and integrations.
Weeks 2–3 — Build voice agent for reservations + FAQ. Wire catering intake. Pilot internally; GM and host roleplay 30+ inquiries.
Week 4 — Live pilot during dinner service overflow. GM listens to recordings daily, tunes brand voice. Onboard reminders and review automation.
"Hi, I'd like to make a reservation for 6 people on Saturday at 7pm." That is the first line, and it is deliberately a question rather than a greeting — the fastest way to find out whether this is an emergency or a price enquiry is to ask.
The three KPIs we commit to
10 use cases mapped
$800–$3,200/mo savings range
21-day implementation
Related trades we build for
Operators in med spa, fitness and auto repair run a similar build, because the failure pattern is the same even when the vocabulary is not.