Build a practical test set for the restaurant assistant

The decision this workflow supports

A successful demonstration of one easy question does not show how the assistant handles mixed requests or uncertainty. Build a small set of fictional scenarios that reflect the restaurant’s actual scope and its important boundaries.

Put the review process in place

Include hours, catering, table requests, an unknown question and an attempted order. Add one correction and one request to speak with staff. Assign the expected outcome before running each scenario so reviewers judge behavior against a clear requirement rather than a pleasant voice.

Worked example for your team

Build a fictional test sheet with an ordinary hours question, a catering inquiry, a corrected date, an attempted order and an unknown venue question. Before running it, write the expected staff handoff or information answer for each. A reviewer should be able to mark a failure even when the assistant sounds natural. For example, a confident invented availability answer fails; an honest staff referral may pass. Keep the scenarios stable when comparing revisions so a seemingly improved result is not merely the effect of asking an easier question.

Sample wording to approve

“Test instruction: act as a fictional organizer asking about a thirty-person lunch, then change the date. The expected result is a corrected inquiry awaiting staff confirmation, with no order or availability promise.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need scenario name, fictional input, expected outcome, observed result, and issue owner. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

An attempted order is redirected. A corrected date appears in the summary. The test record distinguishes a pass from an unresolved defect. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides