Back to all workAcademy prototype

Voice AI restaurant ordering prototype

A caller phones a fictional Nigerian restaurant and speaks to an AI assistant. The assistant takes the order, confirms the details back, and the workflow routes the fields into the right sheet. Orders, reservations and escalations each go to their own tab.

Vapi · n8n · Google Sheets

Watch a test call, 3 minutesOpens on Loom

Google Sheet of captured order rows, one row per call, with columns for the caller, the items ordered and the routing decision — The sheet the assistant writes to. Each row is one call, split into order, reservation and escalation tabs.

What the tests showed

A test call reached the n8n webhook and wrote order and reservation fields into Google Sheets in under two seconds. Where the assistant transcribed a caller name incorrectly, the record was routed to an escalation sheet instead of being confirmed.

n8n workflow canvas for the restaurant assistant, showing the webhook node branching into separate Google Sheets nodes for orders, reservations and escalations — The workflow behind the call. The webhook receives the fields, then routing sends each type of request to its own tab.

The transcript panel from one call. The assistant reads the order back and the caller confirms it.

What is not proven

This was built as a graded academy project around a fictional restaurant. It has run on test calls and sample data only. It has not handled a noisy line, an interrupted caller, or a real kitchen during service.

What I would do next

Add field level confirmation before an order is accepted, then test against noisy calls and incomplete orders before proposing any live pilot.