Answer every call on the first ring.
Leads call after 5 PM and hit voicemail.
Est. deploy 2–3 weeksSee the walkthrough
Intake & Scheduling · Restaurants
Capture reservation requests without losing details.
Large-party requests arrive in several channels.
For: Host managers and the team responsible for intake & scheduling in restaurants.
01 · The outcome
What good looks like.
The team has a host-approved reservation proposal, with source evidence and an explicit approval before any external action. Track reservation requests with complete information against a baseline; do not assume automation improves it.
A connected workflow that uses party size, requested time, accessibility requests, and approved booking rules to collect missing administrative details and check available capacity without promising a table. It produces a host-approved reservation proposal.
Where AI helps, and where a person decides.
AI can collect missing administrative details and check available capacity without promising a table. It drafts and organizes; it does not authorize spending, commitments, clinical decisions or customer communication. The host manager verifies the source facts and approves the final action.
Host manager is accountable. People approve customer-facing, sensitive, financial, and legally binding actions.
- Host manager: Capture the source and scope
- Host manager: Review the proposed outcome
- Host manager: Release only the approved version
- Host manager: Check the result and exceptions
A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
02 · The handoffs
How the work moves.
Every handoff has an owner. Select a step to open or close its detail.
Start when: A group reservation request arrives. Connect only party size, requested time, accessibility requests, and approved booking rules. The host manager confirms the request is authorized and in scope.
Ready when: The source reference, permissions and accountable owner are recorded.
Use the authorized records to collect missing administrative details and check available capacity without promising a table. Preserve the original language alongside the draft and label uncertain fields.
Ready when: Each proposed fact links back to a source, and missing information is visible.
Check a host-approved reservation proposal against the original records and current policy. Correct errors and escalate exceptions to the qualified specialist; do not auto-approve.
Ready when: Host manager has recorded approval or a reason to hold the item.
After explicit approval, save a host-approved reservation proposal in the system of record. Send only approved messages to verified recipients. Record the version and prevent duplicate delivery.
Ready when: The approved record is saved; any delivery is confirmed or placed in the retry queue.
Review reservation requests with complete information each week, sample completed records for quality, and resolve held items. Change the rules only after reviewing actual errors and staff feedback.
Ready when: Exceptions have owners, the metric has a baseline, and corrective actions are assigned.
Sample record.
$ david run --workflow=restaurant-reservation-intake
ILLUSTRATIVE RECORD / NOT LIVE CUSTOMER DATA
- Example
- Illustrative only — not a real client record
- Reference
- RESTAURANT-RESERVATION-I-DEMO-001
- Trigger
- A group reservation request arrives.
- Owner
- Host manager
- Prepared output
- a host-approved reservation proposal
- Review status
- Awaiting human approval — no external action taken
- Missing information
- Owner to verify source completeness
- Measure
- Reservation requests with complete information
Start with your tools.
Connect POS, Google Business Profile, Google Workspace through approved APIs or controlled exports. Map record identifiers first; test permissions and field updates in a sandbox. Vendor names describe possible connections, not a guarantee of an available integration or license.
When things go wrong.
- A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
- Use only authorized sources and role-based access. Keep an audit trail of source records, drafts, approvals and delivery status; deduplicate retries.
- If an integration fails, a source is missing or confidence is low, pause the action and assign the original request to the accountable owner.
Try this week / no DAVID required
A useful first step.
This week, have your host manager time five examples of this work. Use redacted copies of party size, requested time, accessibility requests, and approved booking rules to make a host-approved reservation proposal manually, then list which fields required judgment.
What to measure.
- Reservation requests with complete information
- Minutes of human handling per completed item
- Drafts needing substantive correction
- Exceptions unresolved beyond the agreed review window
Estimate your time back.
20.8
$11,232
03 · More workflows to consider
Related workflows.
Route every inquiry, 24/7.
Email, calls and webforms produce disconnected intake trails.
Est. deploy 3–5 weeksSee the walkthrough
Prepare every treatment start before arrival.
Missing forms delay the first treatment visit.
Est. deploy 4–6 weeksSee the walkthrough
Want this running in your business in 2–4 weeks?
Free 30-minute call. We'll tell you honestly whether AI fits, and where.