Pizzerias & restaurants

On the phone

• Missed-call redirect — keep the shop's number; *71 rolls the calls the counter can't grab to the AI order line. Friday night stops leaking ~$30 tickets.
• The order line — the flow takes items, sizes, changes, collection or delivery + address, repeats the order back, pushes it to the POS or `/crm/ingest`, and texts the confirmation. Wait times come from a knowledge step someone updates once a night.
• Friday-rush overflow — a second line rings the AI when the counter can't; the priority queue keeps regulars first; "kitchen question" transfers inside.
• Reservations on the call — party size, time, name, number → the board. Large parties route to their own flow that captures the event brief and tickets the manager.
• The allergy guardrail — never confirms an allergen from memory; takes a number, tickets the kitchen.
• After-hours — 42% of restaurant calls arrive outside hours; the AI books tomorrow's tables while the kitchen sleeps.

Workflows

• Missed call → "text us your order" — the SMS agent takes it conversationally.
• "Where's my order" chat flow with a knowledge step.
• Late order → ticket — never a promised refund; a human decides.
• Reservation confirmations + reminders on column moves; no-show recovery (polite SMS + rebook link, DND respected).

Social front desk

Messenger and Instagram orders run the same order flow as chat; "do you have space tonight" DMs get live availability wording and the booking link. The menu is one knowledge step shared by every door — update it once a night.

Keep & grow

The "slow Tuesday" SMS campaign to an "ordered before, nothing in 30 days" audience; event-diners ("large party, last 12 months") get the private-dining promo; regulars column → birthday cadence. STOP stops everything; quiet hours hold the 2am blast nobody meant to send.