AITableFlow ยท for restaurants

Customer Journey, End to End

From "sees the website" to "launched, filling tables, and monitored" โ€” with no human in the loop. Every step after signup runs itself, and we build the whole thing for you.

$999/mo First 30 days free ยท first bill day 30 ๐Ÿค– We build it โ€” no human in the loop
Customer does it Automated โ€” no human Conversion / outcome
Day 0
๐Ÿ”Ž
1
Customer

Discover

Lands on the site

A restaurant owner sees the full page, talks to the live AI chat, clicks through the in-product demo, sees the transparent price. No sales call needed โ€” the page sells itself.

System
aitableflow.com
Outcome
Understands it. Ready to start.
๐Ÿ’ณ
2
Customer

Sign up

Clicks "Start free"

Stripe Checkout โ€” 30-day free trial, card on file. $0 charged today; the first $999 runs on day 30. Cancel anytime before then.

System
Stripe Checkout (trial)
Outcome
Customer created ยท bill scheduled day 30
๐Ÿ“จ
3
Automated

Launch form sent

Trigger: payment confirmed

The system emails them the intake form โ€” "everything we need to launch your account" โ€” with a unique link. Sent only to people who put a card down.

System
Stripe webhook โ†’ email + form
Outcome
Customer has the form
๐Ÿ“
4
Customer

Completes the form

~10 minutes, once

Restaurant name, menu, hours, brand, phone, offers, team, and which integrations to connect (their existing booking tool stays in place). The only thing only they know.

System
launch-hub form โ†’ KV store
Outcome
All launch data captured
๐Ÿฝ๏ธ
5
Customer

Reservation system routed

Onboarding: "What reservation system do you use?"

Your AI doesn't just take the reservation โ€” it books the table, and it can never double-book you. Works with whatever you use today โ€” OpenTable, Resy, resOS, Square, Toast, or nothing at all โ€” and adds a "Reserve a table" button to your Google listing. Their answer routes a safe lane โ€” be the book, sync to yours, or capture-and-confirm for OpenTable/Resy โ€” so the AI books (or captures) off one source of truth and two reservations can't collide.

How it routes
Books real tables by phone, chat, and Google โ€” automatically, even when no one can pick up ยท Never double-books โ€” there's always one booking list, so two reservations can't collide ยท Keep your current system, or let us be it โ€” your choice ยท New bookings from Google, where most guests find you ยท No per-cover fees like OpenTable โ€” it's part of your flat price
System
launch-hub form โ†’ booking lane
Outcome
One source of truth ยท never double-books
๐Ÿฅก
6
Customer

To-go & pickup, always on

Anytime โ€” even before you open

Takes to-go & pickup orders too โ€” anytime, even before you open โ€” priced from your menu and sent to your team, so you keep the sale you'd otherwise lose. It's a standing feature and the fallback when a table won't fit: if the AI can't seat them, it offers a pickup order instead of letting the guest hang up.

How it works
Always on โ€” a standing feature, and the fallback when no table fits ยท Prices come only from your menu, never invented ยท The order is a request your team confirms โ€” no automated texts ยท Pay at pickup โ€” no card taken ยท Allergies are flagged to your staff
System
Conversation AI โ†’ menu โ†’ team confirm
Outcome
Sale kept ยท order sent to the team
โš™๏ธ
7
Automated

We build the account

Trigger: form submitted

The system clones the template and builds their GHL sub-account from the form data โ€” custom fields, tags, pipeline, workflows, calendars, custom values, logins. Zero humans. Their AI is configured to answer calls and capture reservation requests for the team to confirm.

System
provision_subaccount.py + GHL API
Outcome
Live, configured account
๐Ÿš€
8
Automated

Launch + handbook

Trigger: build complete

"You're live!" goes out with their login(s), their Daily Handbook link (how to use it every day), and their first two steps โ€” plus an AI welcome call from the same agent now answering their phones and taking reservation requests.

System
email/SMS + Conversation AI
Outcome
Customer can start day one
Day 0โ€“30
๐Ÿ”
9
Automated

30-day nudge engine

Every ~3 days

Email and AI phone calls, personalized to their real progress: praise what they've done, point at the one next step. Tracks an activation checklist (team added, Google reviews connected, calls forwarding, win-back campaign live). The nudge calls double as a live demo of the AI that answers their phones, captures reservation requests, and fills slow nights by winning back past guests.

System
GHL ops workflows + AI calls + monitor
Outcome
Customer gets fully activated & sees value
Day 28
๐Ÿงพ
10
Automated

Billing heads-up

2 days before first charge

A transparent note: "your free month ends in 2 days, first bill on [date]," plus a 30-day scorecard of calls answered, reservation requests captured, and guests won back. No surprises โ€” kills disputes, builds trust.

System
GHL workflow + account stats
Outcome
Trust ยท no chargebacks
Day 30
โœ…
11
Conversion

Convert & run

First $999 charge

The card on file is charged automatically โ€” no second ask. They're a full customer, the AI keeps answering calls and capturing reservation requests on autopilot, and light ongoing monitoring + nudges keep them healthy.

System
Stripe + GHL (steady state)
Outcome
Retained, paying, hands-free