Use a chat readback before sending a staff request

The decision this workflow supports

Typed conversations can change direction as the visitor adds dates or corrects a party size. Before the assistant submits a staff request, a compact readback gives the visitor a chance to catch errors and confirm what they want sent.

Put the review process in place

Show the requested action, relevant date and contact preference in one review message. Invite corrections to individual details. Submit only after the visitor indicates that the summary reflects their request, and retain the pending status after submission.

Worked example for your team

A fictional visitor begins with Friday as the event date, then corrects it to Saturday before submitting. The readback should show Saturday and ask the visitor to review the final request. If the visitor chooses not to send it, the interface should not display a received or confirmed status. After a submission, compare the readback with the staff note. The event date, requested action and contact preference should agree. This test checks the whole transition from draft conversation to staff task rather than only whether the chatbot understood the correction.

Sample wording to approve

“Here is the request I would send: [summary]. Staff still need to confirm any arrangement. Would you like to correct a detail before I pass this to the team?” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need request summary, corrected details, visitor submission choice, destination owner, and pending status. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

A correction replaces the relevant detail. Abandoning the draft does not appear as a confirmed request. The submitted readback matches what staff receive. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides