Kitchen Pass · Proposed AI workflow
Why is Table 7 still waiting?
During lunch service, Table 7 asks for an update while its two bowls are still on the kitchen board.
Try the Kitchen Pass demo →Application screenshots · Sample data
How Kitchen Pass works today
Search for Table 7 · Two bowls. Move the ticket from Received to Cooking, then to Ready when both bowls reach the pass. Mark it Served after handoff.
Simulation · Fictional records
Walk through the chat
Follow the scripted conversation and review the proposed action. Choices affect this walkthrough only.
Requester
Why is Table 7 still waiting?
Proposed agent workflow
-
Read
When the server asks, match Table 7 in the Kitchen Pass board and check the ticket stage. Return Cooking and the two-bowl order.
-
Check
For the Cooking ticket, compare both items in the proposed pass log. Identify the second bowl as outstanding and request a fresh estimate from the pass.
-
Draft
When the pass responds, check that the four-minute estimate is current and refers to the second bowl. Draft a guest update for the server.
-
Approve and record
When the server approves, check for a newer pass update and put the approved wording in the server’s handoff queue. Kitchen staff still record Ready and Served as those events occur.
Result after approval
Table 7 update approved and queued for the server. Ticket remains Cooking.
Exception path
If the pass cannot give a reliable ETA, the assistant tells the server that the second bowl is still cooking and that an estimate was requested. The guest message stays pending until the pass lead confirms timing.
What to measure in a pilot
-
Response time
Timestamp the server’s question and first usable update for each sampled ticket.
-
Estimate accuracy
Compare quoted wait times with the actual time the ticket reaches Ready.