Handle restaurant bookings and orders with an AI receptionist

An AI receptionist answers calls and chat messages to book tables and take delivery orders automatically.

How the work actually flows

It branches. Exactly one path is taken.

Pattern: Exclusive Choice (4) · Simple Merge (5)

flowchart TD trig>"customer calls or messages in"]:::trig s0["identify booking or order"]:::task s1[("save to Airtable")]:::store s2["notify customer"]:::svc trig --> s0 s1 --> s2 gx{"× booking or food order"}:::gate s0 --> gx p00["check table availability"]:::task gx -->|"table booking"| p00 p10["validate menu and price"]:::task gx -->|"food order"| p10 p11["check delivery area"]:::task p10 --> p11 jn{"○ confirmed request"}:::gate p00 --> jn p11 --> jn jn --> s1 out[/"confirmed booking or order saved"/]:::out pay{{"fewer missed bookings and order errors"}}:::pay s2 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepAn outside serviceA record or sheetOne path onlyPaths rejoinResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
AI Agents & Autonomous SystemsVoice & PhoneMessaging & NotificationsSpreadsheet & Database OpsScheduling & Calendar
Connects
VapiTelegramAirtableOpenAIGoogle Maps
Featured in

The problem it solves

During rush hours, phones ring off the hook while staff are busy serving tables, so bookings get missed or orders get taken down wrong. Juggling calls, messages, and a paper order pad leads to mistakes that cost you customers.

Who it fits

Small to mid-sized restaurants that take bookings and orders by phone or chat.

How it works

  1. A customer calls or messages to book a table or place an order
  2. For bookings, the assistant checks table availability for the requested time
  3. For orders, it pulls the menu, validates items, and calculates the price
  4. Delivery addresses are checked against your delivery area, with takeaway offered automatically if delivery isn't available
  5. The confirmed booking or order is saved to Airtable
What you get

Tables booked and orders taken after hours

Callers and chat messages get their table booked or their order taken right away, any time you're closed or busy.

What you get

A confirmed table booking or order saved in Airtable, with the customer notified immediately.

What you need

Airtable, an OpenAI API key, a voice calling service, and a messaging account.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook